Well unfortunately these computers are over an hour’s drive away from me so
I can’t disconnect the one network. Here is the netstar -rn info
The output for ifconfig is what your would expect.
UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST
inet 192.168.4.239 netmask ffffff00 broadcast 192.168.4.255
Here is the netstat info you wanted. There is a sl0 slip interface in there
too, but I tried my setup without the complication of the sliplogin and it
still didn’t work. I also tried starting Socket use en1 ( random guessing )
and that worked no better than on en2.
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs
Coll
en2 1500 0.1.2.ed.bd.2c 1 0 18 0
0
en2 1500 192.168.4 192.168.4.239 1 0 18 0
0
en1* 1500 0.4.76.34.82.99 0 0 0 0
0
sl0* 296 0 0 0 0
0
lo0 1536 26 0 26 0
0
lo0 1536 127 127.0.0.1 26 0 26 0
0
Routing tables
Destination Gateway Flags Refs Use Interface
Route Tree for Protocol Family 2:
(root node) =>
default 192.168.4.239 UG 0 0 en2
127.0.0.1 127.0.0.1 UH 1 0 lo0
192.168.4 192.168.4.239 U 1 26 en2
(root node)
and for the other node
ame Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
en1* 1500 0.4.76.34.80.d3 0 0 0 0
0
en2 1500 0.4.76.34.82.9e 19 0 25 0
0
en2 1500 192.168.4 192.168.4.236 19 0 25 0
0
sl0 296 66 0 57 0
0
sl0 296 192.168.4 192.168.4.236 66 0 57 0
0
lo0 1536 102 0 102 0
0
lo0 1536 127 127.0.0.1 102 0 102 0
0
Routing tables
Destination Gateway Flags Refs Use Interface
Route Tree for Protocol Family 2:
(root node) =>
default 192.168.4.236 UG 0 0 en2
127.0.0.1 127.0.0.1 UH 1 0 lo0
192.168.4 192.168.4.236 U 1 92 en2
192.168.4.231 192.168.4.236 UH 4 57 sl0
(root node)
<Horst.Hannappel@mbs-software.de> wrote in message
news:ah36iq$c7t$1@mbs-software.de…
Sheldon Parkes <> sheldon@onlinedata.com> > wrote:
Socket is starting up ok. I can do an ifconfig en2 and get back what I
would
expect from it on either of the nodes but they still cannot ping each
other
even though QNX level networking is working fine between the two nodes.
Its
a real head scratcher for me…
Could you post the output of “ifconfig [all interfaces]” and “netstat -rn”
on both nodes? Maybe someone will see a problem.
Did you try to connect just one pair of cards and see if the still QNX
networking
is OK and TCP/IP not?
Are all Cards on the same hub?
Sheldon
Horst.Hannappel@mbs-software.de> > wrote in message
news:ah0fui$nmi$> 1@mbs-software.de> …
Sheldon Parkes <> sheldon@onlinedata.com> > wrote:
I have 2 QNX 4 boxes set up each with 2 ethernet cards en1 and en2.
The
QNX
networking works perfectly and is using both interfaces as far as I
can
tell
from netinfo -l.
I installed TCPIP on both machines and they can ping themselves
perfectly
but cannot ping each other. The setup is dead simple, no routing
involved at
all, IP number range and subnet masks are the same, everything I can
think
of is setup correctly.
Has anyone run across this before? I’m guessing it has something to
do
with
the dual ethernet interfaces but who knows…
One thing that has bitten us is you have to wait with starting
Sock(l)et
until
the Net.anything have initialised and registered with Net. Otherwise
Socket
wont’t find an interface.
Thanks
Sheldon Parkes
sheldon@onlinedata.com
\