TCPIP and 2 interfaces

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…

Thanks

Sheldon Parkes
sheldon@onlinedata.com

Can you post netstat -in & netstat -rn for both hosts?

“Sheldon Parkes” <sheldon@onlinedata.com> wrote in message
news:agv0u7$hb9$1@inn.qnx.com

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…

Thanks

Sheldon Parkes
sheldon@onlinedata.com

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)





“Bill Caroselli (Q-TPS)” <QTPS@EarthLink.net> wrote in message
news:agv2k1$imn$1@inn.qnx.com

Can you post netstat -in & netstat -rn for both hosts?

“Sheldon Parkes” <> sheldon@onlinedata.com> > wrote in message
news:agv0u7$hb9$> 1@inn.qnx.com> …
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…

Thanks

Sheldon Parkes
sheldon@onlinedata.com

\

Geez forget that default entry in the netstat -rn output as well, that was
me just experimenting.

Sheldon

“Sheldon Parkes” <sheldon@onlinedata.com> wrote in message
news:agv35l$j13$1@inn.qnx.com

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)





“Bill Caroselli (Q-TPS)” <> QTPS@EarthLink.net> > wrote in message
news:agv2k1$imn$> 1@inn.qnx.com> …
Can you post netstat -in & netstat -rn for both hosts?

“Sheldon Parkes” <> sheldon@onlinedata.com> > wrote in message
news:agv0u7$hb9$> 1@inn.qnx.com> …
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…

Thanks

Sheldon Parkes
sheldon@onlinedata.com



\

Too bad. That was my first suggestion.

OK. Dumb question time.

Are you sure that the cable from the correct interface is going to the other
correct interface? Other than that, it looks OK to me.

“Sheldon Parkes” <sheldon@onlinedata.com> wrote in message
news:agv45s$jo4$1@inn.qnx.com

Geez forget that default entry in the netstat -rn output as well, that was
me just experimenting.

Sheldon

“Sheldon Parkes” <> sheldon@onlinedata.com> > wrote in message
news:agv35l$j13$> 1@inn.qnx.com> …
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)





“Bill Caroselli (Q-TPS)” <> QTPS@EarthLink.net> > wrote in message
news:agv2k1$imn$> 1@inn.qnx.com> …
Can you post netstat -in & netstat -rn for both hosts?

“Sheldon Parkes” <> sheldon@onlinedata.com> > wrote in message
news:agv0u7$hb9$> 1@inn.qnx.com> …
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…

Thanks

Sheldon Parkes
sheldon@onlinedata.com





\

These computers are remote to me so I can’t check but what I did do earlier
( having the same thought as you ) was to start the one Socket on en1 and
the other on en2 ( and vice versa ) but still with no luck.

Sheldon

“Bill Caroselli (Q-TPS)” <QTPS@EarthLink.net> wrote in message
news:agv4t5$k6f$1@inn.qnx.com

Too bad. That was my first suggestion.

OK. Dumb question time.

Are you sure that the cable from the correct interface is going to the
other
correct interface? Other than that, it looks OK to me.

“Sheldon Parkes” <> sheldon@onlinedata.com> > wrote in message
news:agv45s$jo4$> 1@inn.qnx.com> …
Geez forget that default entry in the netstat -rn output as well, that
was
me just experimenting.

Sheldon

“Sheldon Parkes” <> sheldon@onlinedata.com> > wrote in message
news:agv35l$j13$> 1@inn.qnx.com> …
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)





“Bill Caroselli (Q-TPS)” <> QTPS@EarthLink.net> > wrote in message
news:agv2k1$imn$> 1@inn.qnx.com> …
Can you post netstat -in & netstat -rn for both hosts?

“Sheldon Parkes” <> sheldon@onlinedata.com> > wrote in message
news:agv0u7$hb9$> 1@inn.qnx.com> …
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…

Thanks

Sheldon Parkes
sheldon@onlinedata.com







\

OK, Dumb question from me.

Are you saying .236 can’t ping to .239 ? Or you are saying
…231 can’t ping to .239 ?

If the first case, can we see “arp -na” output after a ping?
If the second case, you have several things to check:

  1. is .236 (the router)'s Tcpip eanbled with “forward” ?
  2. the .239 need to know how to get to .231 (certainly no
    directly through en2)
  3. the .231 need to be informed that to goto .239, it should
    hit .236.

-xtang

Sheldon Parkes <sheldon@onlinedata.com> wrote:

These computers are remote to me so I can’t check but what I did do earlier
( having the same thought as you ) was to start the one Socket on en1 and
the other on en2 ( and vice versa ) but still with no luck.

Sheldon

“Bill Caroselli (Q-TPS)” <> QTPS@EarthLink.net> > wrote in message
news:agv4t5$k6f$> 1@inn.qnx.com> …
Too bad. That was my first suggestion.

OK. Dumb question time.

Are you sure that the cable from the correct interface is going to the
other
correct interface? Other than that, it looks OK to me.

“Sheldon Parkes” <> sheldon@onlinedata.com> > wrote in message
news:agv45s$jo4$> 1@inn.qnx.com> …
Geez forget that default entry in the netstat -rn output as well, that
was
me just experimenting.

Sheldon

“Sheldon Parkes” <> sheldon@onlinedata.com> > wrote in message
news:agv35l$j13$> 1@inn.qnx.com> …
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)





“Bill Caroselli (Q-TPS)” <> QTPS@EarthLink.net> > wrote in message
news:agv2k1$imn$> 1@inn.qnx.com> …
Can you post netstat -in & netstat -rn for both hosts?

“Sheldon Parkes” <> sheldon@onlinedata.com> > wrote in message
news:agv0u7$hb9$> 1@inn.qnx.com> …
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…

Thanks

Sheldon Parkes
sheldon@onlinedata.com







\

231 is not really in the picture yet ( I could understand 231 not being able
to ping one of 236 or 239 because I have no gateway setup for the slip
connection ). The problem is between 236 and 239. Neither one can ping each
other even though they are on the same physical network and QNX networking
is working.

arp shows no entries after attempting a ping. I even tried using arp -s to
map the card addresses to the IP addresses manually but it still won’t go.

Sheldon

“Xiaodan Tang” <xtang@qnx.com> wrote in message
news:agvd00$rm2$1@nntp.qnx.com

OK, Dumb question from me.

Are you saying .236 can’t ping to .239 ? Or you are saying
.231 can’t ping to .239 ?

If the first case, can we see “arp -na” output after a ping?
If the second case, you have several things to check:

  1. is .236 (the router)'s Tcpip eanbled with “forward” ?
  2. the .239 need to know how to get to .231 (certainly no
    directly through en2)
  3. the .231 need to be informed that to goto .239, it should
    hit .236.

-xtang

Sheldon Parkes <> sheldon@onlinedata.com> > wrote:
These computers are remote to me so I can’t check but what I did do
earlier
( having the same thought as you ) was to start the one Socket on en1
and
the other on en2 ( and vice versa ) but still with no luck.

Sheldon

“Bill Caroselli (Q-TPS)” <> QTPS@EarthLink.net> > wrote in message
news:agv4t5$k6f$> 1@inn.qnx.com> …
Too bad. That was my first suggestion.

OK. Dumb question time.

Are you sure that the cable from the correct interface is going to the
other
correct interface? Other than that, it looks OK to me.

“Sheldon Parkes” <> sheldon@onlinedata.com> > wrote in message
news:agv45s$jo4$> 1@inn.qnx.com> …
Geez forget that default entry in the netstat -rn output as well,
that
was
me just experimenting.

Sheldon

“Sheldon Parkes” <> sheldon@onlinedata.com> > wrote in message
news:agv35l$j13$> 1@inn.qnx.com> …
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)





“Bill Caroselli (Q-TPS)” <> QTPS@EarthLink.net> > wrote in message
news:agv2k1$imn$> 1@inn.qnx.com> …
Can you post netstat -in & netstat -rn for both hosts?

“Sheldon Parkes” <> sheldon@onlinedata.com> > wrote in message
news:agv0u7$hb9$> 1@inn.qnx.com> …
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…

Thanks

Sheldon Parkes
sheldon@onlinedata.com









\

A follow up of things I tried to resolve why I can’t ping between 2 nodes. I
ran netsniff on the node that is 192.168.4.236 and pinged it from
192.168.4.239 and saw that the packets were actually arriving. Now can
someone please interpret what this means exactly:

In my netmap file node 8 ( which is 192.168.4.239 ) has

8 1 000102edbd2c
8 2 000476348299

Node 9 ( which is 192.168.4.236 ) has

9 1 0004763400d3
9 2 00047634829e


Now the MAC address for the Src in the netsniff output is the correct one
for en2 as I would expect. What exactly is ARP request sender? ( it contains
the MAC address for en1 for some reason - which is likely my problem ).

I tried using arp -s to map the ip address to the correct MAC address on
both nodes but still can’t ping. I seek the wisdom of the gurus out there…

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914822
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target 00:00:00:00:00:00
192.168.4.236

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914823
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target 00:00:00:00:00:00
192.168.4.236

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914824
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target 00:00:00:00:00:00
192.168.4.236

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914825
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target 00:00:00:00:00:00
192.168.4.236

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914826
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target 00:00:00:00:00:00
192.168.4.236

“Sheldon Parkes” <sheldon@onlinedata.com> wrote in message
news:agv0u7$hb9$1@inn.qnx.com

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…

Thanks

Sheldon Parkes
sheldon@onlinedata.com

It may be useful for testing to only configure one interface and get that
working first.

“Sheldon Parkes” <sheldon@onlinedata.com> wrote in message
news:ah3v7f$e2b$1@inn.qnx.com

A follow up of things I tried to resolve why I can’t ping between 2 nodes.
I
ran netsniff on the node that is 192.168.4.236 and pinged it from
192.168.4.239 and saw that the packets were actually arriving. Now can
someone please interpret what this means exactly:

In my netmap file node 8 ( which is 192.168.4.239 ) has

8 1 000102edbd2c
8 2 000476348299

Node 9 ( which is 192.168.4.236 ) has

9 1 0004763400d3
9 2 00047634829e


Now the MAC address for the Src in the netsniff output is the correct one
for en2 as I would expect. What exactly is ARP request sender? ( it
contains
the MAC address for en1 for some reason - which is likely my problem ).

I tried using arp -s to map the ip address to the correct MAC address on
both nodes but still can’t ping. I seek the wisdom of the gurus out
there…

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914822
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target
00:00:00:00:00:00
192.168.4.236

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914823
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target
00:00:00:00:00:00
192.168.4.236

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914824
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target
00:00:00:00:00:00
192.168.4.236

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914825
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target
00:00:00:00:00:00
192.168.4.236

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914826
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target
00:00:00:00:00:00
192.168.4.236

“Sheldon Parkes” <> sheldon@onlinedata.com> > wrote in message
news:agv0u7$hb9$> 1@inn.qnx.com> …
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…

Thanks

Sheldon Parkes
sheldon@onlinedata.com

\

Looks like en1 and en2 are mixed in the netmap file for node 8.

What does netinfo -l say about the MAC addresses? Do these match the MAC
addresses reported via netstat? Those reported by netinfo should match those
reported by netstat and should also match those listed in the netmap file.

The leading 00 are not required in the netmap entries.


“Sheldon Parkes” <sheldon@onlinedata.com> wrote in message
news:ah3v7f$e2b$1@inn.qnx.com

A follow up of things I tried to resolve why I can’t ping between 2 nodes.
I
ran netsniff on the node that is 192.168.4.236 and pinged it from
192.168.4.239 and saw that the packets were actually arriving. Now can
someone please interpret what this means exactly:

In my netmap file node 8 ( which is 192.168.4.239 ) has

8 1 000102edbd2c
8 2 000476348299

Node 9 ( which is 192.168.4.236 ) has

9 1 0004763400d3
9 2 00047634829e


Now the MAC address for the Src in the netsniff output is the correct one
for en2 as I would expect. What exactly is ARP request sender? ( it
contains
the MAC address for en1 for some reason - which is likely my problem ).

I tried using arp -s to map the ip address to the correct MAC address on
both nodes but still can’t ping. I seek the wisdom of the gurus out
there…

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914822
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target
00:00:00:00:00:00
192.168.4.236

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914823
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target
00:00:00:00:00:00
192.168.4.236

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914824
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target
00:00:00:00:00:00
192.168.4.236

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914825
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target
00:00:00:00:00:00
192.168.4.236

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914826
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target
00:00:00:00:00:00
192.168.4.236

“Sheldon Parkes” <> sheldon@onlinedata.com> > wrote in message
news:agv0u7$hb9$> 1@inn.qnx.com> …
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…

Thanks

Sheldon Parkes
sheldon@onlinedata.com

\

You’re absolutely right, my netstat -i does not match my netinfo -l. Now
what does this imply? I rely upon the output from netinfo -l for the values
I put into the netmap. Where is the setup that netstat -i is reporting
coming from?

Sheldon

“Brown, Richard” brownr_aecl_ca@127.0.0.1 wrote in message
news:ah47uk$kru$1@inn.qnx.com

Looks like en1 and en2 are mixed in the netmap file for node 8.

What does netinfo -l say about the MAC addresses? Do these match the MAC
addresses reported via netstat? Those reported by netinfo should match
those
reported by netstat and should also match those listed in the netmap file.

The leading 00 are not required in the netmap entries.


“Sheldon Parkes” <> sheldon@onlinedata.com> > wrote in message
news:ah3v7f$e2b$> 1@inn.qnx.com> …
A follow up of things I tried to resolve why I can’t ping between 2
nodes.
I
ran netsniff on the node that is 192.168.4.236 and pinged it from
192.168.4.239 and saw that the packets were actually arriving. Now can
someone please interpret what this means exactly:

In my netmap file node 8 ( which is 192.168.4.239 ) has

8 1 000102edbd2c
8 2 000476348299

Node 9 ( which is 192.168.4.236 ) has

9 1 0004763400d3
9 2 00047634829e


Now the MAC address for the Src in the netsniff output is the correct
one
for en2 as I would expect. What exactly is ARP request sender? ( it
contains
the MAC address for en1 for some reason - which is likely my problem ).

I tried using arp -s to map the ip address to the correct MAC address on
both nodes but still can’t ping. I seek the wisdom of the gurus out
there…

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914822
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target
00:00:00:00:00:00
192.168.4.236

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914823
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target
00:00:00:00:00:00
192.168.4.236

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914824
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target
00:00:00:00:00:00
192.168.4.236

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914825
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target
00:00:00:00:00:00
192.168.4.236

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914826
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target
00:00:00:00:00:00
192.168.4.236

“Sheldon Parkes” <> sheldon@onlinedata.com> > wrote in message
news:agv0u7$hb9$> 1@inn.qnx.com> …
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…

Thanks

Sheldon Parkes
sheldon@onlinedata.com



\

If the netmap file and netinfo agree about the MAC addresses and netstat
still disagrees then it may be related to Net driver start order. Try
starting “Net.xxxx -l1 …” before “Net.xxxx -l2 …”, etc.


“Sheldon Parkes” <sheldon@onlinedata.com> wrote in message
news:ah4fjb$q5m$1@inn.qnx.com

You’re absolutely right, my netstat -i does not match my netinfo -l. Now
what does this imply? I rely upon the output from netinfo -l for the
values
I put into the netmap. Where is the setup that netstat -i is reporting
coming from?

Sheldon

“Brown, Richard” brownr_aecl_ca@127.0.0.1 wrote in message
news:ah47uk$kru$> 1@inn.qnx.com> …
Looks like en1 and en2 are mixed in the netmap file for node 8.

What does netinfo -l say about the MAC addresses? Do these match the MAC
addresses reported via netstat? Those reported by netinfo should match
those
reported by netstat and should also match those listed in the netmap
file.

The leading 00 are not required in the netmap entries.


“Sheldon Parkes” <> sheldon@onlinedata.com> > wrote in message
news:ah3v7f$e2b$> 1@inn.qnx.com> …
A follow up of things I tried to resolve why I can’t ping between 2
nodes.
I
ran netsniff on the node that is 192.168.4.236 and pinged it from
192.168.4.239 and saw that the packets were actually arriving. Now can
someone please interpret what this means exactly:

In my netmap file node 8 ( which is 192.168.4.239 ) has

8 1 000102edbd2c
8 2 000476348299

Node 9 ( which is 192.168.4.236 ) has

9 1 0004763400d3
9 2 00047634829e


Now the MAC address for the Src in the netsniff output is the correct
one
for en2 as I would expect. What exactly is ARP request sender? ( it
contains
the MAC address for en1 for some reason - which is likely my
problem ).

I tried using arp -s to map the ip address to the correct MAC address
on
both nodes but still can’t ping. I seek the wisdom of the gurus out
there…

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914822
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target
00:00:00:00:00:00
192.168.4.236

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914823
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target
00:00:00:00:00:00
192.168.4.236

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914824
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target
00:00:00:00:00:00
192.168.4.236

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914825
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target
00:00:00:00:00:00
192.168.4.236

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914826
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target
00:00:00:00:00:00
192.168.4.236

“Sheldon Parkes” <> sheldon@onlinedata.com> > wrote in message
news:agv0u7$hb9$> 1@inn.qnx.com> …
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…

Thanks

Sheldon Parkes
sheldon@onlinedata.com





\

I have exactly the same problem.

I have a board with 2 82559ER ethernet controllers
which I start with “nettrap start”. “netmap” always reports the devices and
ethernet addresses correctly but “netstat -i” show that most boots
the ethernet addresses are swaped.

Any ideas whats going on?

Charles.

“Brown, Richard” brownr_aecl_ca@127.0.0.1 wrote in message
news:ah67c2$7as$1@inn.qnx.com

If the netmap file and netinfo agree about the MAC addresses and netstat
still disagrees then it may be related to Net driver start order. Try
starting “Net.xxxx -l1 …” before “Net.xxxx -l2 …”, etc.


“Sheldon Parkes” <> sheldon@onlinedata.com> > wrote in message
news:ah4fjb$q5m$> 1@inn.qnx.com> …
You’re absolutely right, my netstat -i does not match my netinfo -l. Now
what does this imply? I rely upon the output from netinfo -l for the
values
I put into the netmap. Where is the setup that netstat -i is reporting
coming from?

Sheldon

“Brown, Richard” brownr_aecl_ca@127.0.0.1 wrote in message
news:ah47uk$kru$> 1@inn.qnx.com> …
Looks like en1 and en2 are mixed in the netmap file for node 8.

What does netinfo -l say about the MAC addresses? Do these match the
MAC
addresses reported via netstat? Those reported by netinfo should match
those
reported by netstat and should also match those listed in the netmap
file.

The leading 00 are not required in the netmap entries.


“Sheldon Parkes” <> sheldon@onlinedata.com> > wrote in message
news:ah3v7f$e2b$> 1@inn.qnx.com> …
A follow up of things I tried to resolve why I can’t ping between 2
nodes.
I
ran netsniff on the node that is 192.168.4.236 and pinged it from
192.168.4.239 and saw that the packets were actually arriving. Now
can
someone please interpret what this means exactly:

In my netmap file node 8 ( which is 192.168.4.239 ) has

8 1 000102edbd2c
8 2 000476348299

Node 9 ( which is 192.168.4.236 ) has

9 1 0004763400d3
9 2 00047634829e


Now the MAC address for the Src in the netsniff output is the
correct
one
for en2 as I would expect. What exactly is ARP request sender? ( it
contains
the MAC address for en1 for some reason - which is likely my
problem ).

I tried using arp -s to map the ip address to the correct MAC
address
on
both nodes but still can’t ping. I seek the wisdom of the gurus out
there…

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914822
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target
00:00:00:00:00:00
192.168.4.236

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914823
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target
00:00:00:00:00:00
192.168.4.236

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914824
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target
00:00:00:00:00:00
192.168.4.236

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914825
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target
00:00:00:00:00:00
192.168.4.236

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914826
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target
00:00:00:00:00:00
192.168.4.236

“Sheldon Parkes” <> sheldon@onlinedata.com> > wrote in message
news:agv0u7$hb9$> 1@inn.qnx.com> …
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…

Thanks

Sheldon Parkes
sheldon@onlinedata.com







\

It appears that the first “en” interfaces is assigned to the first
NIC that got started by its driver.
It is not necessary to run netmap in order for the TCP/IP stack
to function, and as far as I can tell ifconfig cares nothing about
LAN numbers.
Using nettrap to start the drivers can be slow at best, and un-
predictable, as you apparently observe.

Try setting up the Net.ether82557 drivers “by hand” in the sysinit.
Use the -p or -i options to control which card starts first.

Richard

Charles Dobson wrote:

I have exactly the same problem.

I have a board with 2 82559ER ethernet controllers
which I start with “nettrap start”. “netmap” always reports the devices and
ethernet addresses correctly but “netstat -i” show that most boots
the ethernet addresses are swaped.

Any ideas whats going on?

Charles.

“Brown, Richard” brownr_aecl_ca@127.0.0.1 wrote in message
news:ah67c2$7as$> 1@inn.qnx.com> …
If the netmap file and netinfo agree about the MAC addresses and netstat
still disagrees then it may be related to Net driver start order. Try
starting “Net.xxxx -l1 …” before “Net.xxxx -l2 …”, etc.


“Sheldon Parkes” <> sheldon@onlinedata.com> > wrote in message
news:ah4fjb$q5m$> 1@inn.qnx.com> …
You’re absolutely right, my netstat -i does not match my netinfo -l. Now
what does this imply? I rely upon the output from netinfo -l for the
values
I put into the netmap. Where is the setup that netstat -i is reporting
coming from?

Sheldon

“Brown, Richard” brownr_aecl_ca@127.0.0.1 wrote in message
news:ah47uk$kru$> 1@inn.qnx.com> …
Looks like en1 and en2 are mixed in the netmap file for node 8.

What does netinfo -l say about the MAC addresses? Do these match the
MAC
addresses reported via netstat? Those reported by netinfo should match
those
reported by netstat and should also match those listed in the netmap
file.

The leading 00 are not required in the netmap entries.


“Sheldon Parkes” <> sheldon@onlinedata.com> > wrote in message
news:ah3v7f$e2b$> 1@inn.qnx.com> …
A follow up of things I tried to resolve why I can’t ping between 2
nodes.
I
ran netsniff on the node that is 192.168.4.236 and pinged it from
192.168.4.239 and saw that the packets were actually arriving. Now
can
someone please interpret what this means exactly:

In my netmap file node 8 ( which is 192.168.4.239 ) has

8 1 000102edbd2c
8 2 000476348299

Node 9 ( which is 192.168.4.236 ) has

9 1 0004763400d3
9 2 00047634829e


Now the MAC address for the Src in the netsniff output is the
correct
one
for en2 as I would expect. What exactly is ARP request sender? ( it
contains
the MAC address for en1 for some reason - which is likely my
problem ).

I tried using arp -s to map the ip address to the correct MAC
address
on
both nodes but still can’t ping. I seek the wisdom of the gurus out
there…

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914822
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target
00:00:00:00:00:00
192.168.4.236

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914823
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target
00:00:00:00:00:00
192.168.4.236

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914824
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target
00:00:00:00:00:00
192.168.4.236

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914825
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target
00:00:00:00:00:00
192.168.4.236

Src 000476 348299 [8] Dst FFFFFF FFFFFF [?] Len 48 Lan 2(Eth)
1026914826
ARP request sender 00:01:02:ed:bd:2c 192.168.4.239 target
00:00:00:00:00:00
192.168.4.236

“Sheldon Parkes” <> sheldon@onlinedata.com> > wrote in message
news:agv0u7$hb9$> 1@inn.qnx.com> …
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…

Thanks

Sheldon Parkes
sheldon@onlinedata.com







\