LAN network config problems

i’ve a linux server which have the IP 192.168.0.1 .

my QNX Box is configure as 192.168.0.2 (en0 … configure as … Realtek ?
NE2000 ? … but configured :slight_smile:

(i don’t have the nettrap binary for testing as it said on FAQ’s … :frowning:

these computers are in the same LAN network …

when i try to ping the server (192.168.0.1) that tells me “no route to host”
or “host down” …

can anyone tell me what command lines to launch (io-net etc …) for the
network card and protocols (TCP/IP) become active ??? (maybe the problem is
there … but i don’t know …)

please help me :frowning:

Mike

Mike <mluneau@fr-logic.com> wrote:

i’ve a linux server which have the IP 192.168.0.1 .

my QNX Box is configure as 192.168.0.2 (en0 … configure as … Realtek ?
NE2000 ? … but configured > :slight_smile:

(i don’t have the nettrap binary for testing as it said on FAQ’s … > :frowning:

these computers are in the same LAN network …

when i try to ping the server (192.168.0.1) that tells me “no route to host”
or “host down” …

You want to post “netstat -ni”, “netstat -nr”, “nicinfo” output before/after
your “ping”

-xtang

can anyone tell me what command lines to launch (io-net etc …) for the
network card and protocols (TCP/IP) become active ??? (maybe the problem is
there … but i don’t know …)

please help me > :frowning:

Mike

i’ve verified all that commands and all parameters seems to be correct …
all stacks are loaded etc … that is a space OS :wink: all OS works fine with
my network hardware :slight_smile:

but i’ll post what you want :slight_smile:

Mike


“Xiaodan Tang” <xtang@qnx.com> a écrit dans le message news:
9isb2o$d8l$1@nntp.qnx.com

Mike <> mluneau@fr-logic.com> > wrote:
i’ve a linux server which have the IP 192.168.0.1 .

my QNX Box is configure as 192.168.0.2 (en0 … configure as …
Realtek ?
NE2000 ? … but configured > :slight_smile:

(i don’t have the nettrap binary for testing as it said on FAQ’s … > :frowning:

these computers are in the same LAN network …

when i try to ping the server (192.168.0.1) that tells me “no route to
host”
or “host down” …

You want to post “netstat -ni”, “netstat -nr”, “nicinfo” output
before/after
your “ping”

-xtang

can anyone tell me what command lines to launch (io-net etc …) for the
network card and protocols (TCP/IP) become active ??? (maybe the problem
is
there … but i don’t know …)

please help me > :frowning:

Mike

Hi,

it seems I have the same problem - although I’m trying to connect to the
internet by adsl, actually …

I installed QNX-RTD 6.1 using the latest image (downloaded about 1 week
ago).
But it didn’t recognize my network-card at all (some kind of DEC 21143
compatible chip by Davicom: DM9102AF), even if i tried to tell io-net to
explicitly load devn-tulip.so But ok - it might be not supported.
I changed the card to some Realtek NE2000: one PCI and 2 ISA (one after the
other …): they were recognized :slight_smile:))
After that the photon-dialer / phlip finally knew about the crad (en0).
Trying the photon-dialer, I found it starting pppoe, conecting server,
conecting server, conecting server, conecting server, and so on
So, I had a closer look at the card and configuration. I think, the cards (I
tried them on 2 different machines with qnx) were recognized well, but there
went something wrong with their initialization: Using other os, the
corresponding “link-leds” on my hub use to turn to green somewhere within
the boot-phases. Unsing QNX, instead, the link-leds keep dark. Since I can
see the the cards’ “TX-led” start blinking after a ping to 192.168.0.2
while the hub’s leds keep dark and TxD bad counter rises, I suppose the
cards initialization failed (still using bnc ??). Especially, because I
tried to change some card settings as the “connector” (all my cards have bnc
as well as twisted pair), duplex and “mtu”. But nicinfo always tells me the
same settings.

I hope someone can tell me how to set up a qnxrtp-network using tcpip and
dsl correctly.

Ingolf

this is what the info-tools tell before a “ping” :


Just after startup, nicinfo says:

NE2000 Ethernet Controller
Physical Node ID … 004005 64B560
Current Physical Node ID … 004005 64B560
Media Rate … 10.00 Mb/s half-duplex UTP
MTU … 1514
Lan … 0
I/O Port Range … 0xEC00 → 0xEC1E
Hardware Interrupt … 0xB
Promiscuous … Disabled
Multicast … Enabled

Total Packets Txd OK … 0
Total Packets Txd Bad … 0
Total Packets Rxd OK … 0
Total Rx Errors … 0

Total Bytes Txd … 0
Total Bytes Rxd … 0

Tx Collision Errors … 0
Tx Collisions Errors (aborted) … 0
Carrier Sense Lost on Tx … 0
FIFO Underruns During Tx … 0
Tx deferred … 0
Out of Window Collisions … 0
FIFO Overruns During Rx … 0
Alignment errors … 0
CRC errors … 0

netstat -ni says:

lo0: flags=8009<UP,LOOPBACK,MULTICAST> mtu 32976
inet 127.0.0.1 netmask 0xff000000
en0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
address: 00:40:05:64:b5:60
inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255

and netstat -nr says:

Name Mtu Network Address Ipkts Ierrs Opkts Oerrs
Coll
lo0 32976 0 0 0 0
0
lo0 32976 127 127.0.0.1 0 0 0 0
0
en0 1500 00:40:05:64:b5:60 0 0 2 0
0
en0 1500 192.168 192.168.0.1 0 0 2 0
0
Routing tables

Internet:
Destination Gateway Flags Refs Use Mtu
Interface
127.0.0.1 127.0.0.1 UH 0 0 - lo0
192.168 192.168.0.1 U 0 0 - en0
192.168.0.1 192.168.0.1 UH 0 0 - lo0


And after a “ping” to 192.168.0.0.2


nicinfo:

NE2000 Ethernet Controller
Physical Node ID … 004005 64B560
Current Physical Node ID … 004005 64B560
Media Rate … 10.00 Mb/s half-duplex UTP
MTU … 1514
Lan … 0
I/O Port Range … 0xEC00 → 0xEC1E
Hardware Interrupt … 0xB
Promiscuous … Disabled
Multicast … Enabled

Total Packets Txd OK … 0
Total Packets Txd Bad … 141
Total Packets Rxd OK … 0
Total Rx Errors … 0

Total Bytes Txd … 300
Total Bytes Rxd … 0

Tx Collision Errors … 141
Tx Collisions Errors (aborted) … 141
Carrier Sense Lost on Tx … 141
FIFO Underruns During Tx … 0
Tx deferred … 0
Out of Window Collisions … 0
FIFO Overruns During Rx … 0
Alignment errors … 0
CRC errors … 0


netstat -ni:

Name Mtu Network Address Ipkts Ierrs Opkts Oerrs
Coll
lo0 32976 0 0 0 0
0
lo0 32976 127 127.0.0.1 0 0 0 0
0
en0 1500 00:40:05:64:b5:60 0 0 7 0
0
en0 1500 192.168 192.168.0.1 0 0 7 0
0
Routing tables


and netstat -nr:

Internet:
Destination Gateway Flags Refs Use Mtu
Interface
127.0.0.1 127.0.0.1 UH 0 0 - lo0
192.168 192.168.0.1 U 0 9 - en0
192.168.0.1 192.168.0.1 UH 0 0 - lo0
lo0: flags=8009<UP,LOOPBACK,MULTICAST> mtu 32976
inet 127.0.0.1 netmask 0xff000000
en0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
address: 00:40:05:64:b5:60
inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255


----- Original Message -----
From: “Xiaodan Tang” <xtang@qnx.com>
Newsgroups: qdn.public.qnxrtp.installation
Sent: Sunday, July 15, 2001 4:58 PM
Subject: Re: LAN network config problems


Mike <> mluneau@fr-logic.com> > wrote:
i’ve a linux server which have the IP 192.168.0.1 .

my QNX Box is configure as 192.168.0.2 (en0 … configure as …
Realtek ?
NE2000 ? … but configured > :slight_smile:

(i don’t have the nettrap binary for testing as it said on FAQ’s … > :frowning:

these computers are in the same LAN network …

when i try to ping the server (192.168.0.1) that tells me “no route to
host”
or “host down” …

You want to post “netstat -ni”, “netstat -nr”, “nicinfo” output
before/after
your “ping”

-xtang

can anyone tell me what command lines to launch (io-net etc …) for the
network card and protocols (TCP/IP) become active ??? (maybe the problem
is
there … but i don’t know …)

please help me > :frowning:

Mike