I'm a bit confused myself...  Just to re-cap.  You have three x86 boxes,
all connected together on the same Ethernet switch: a target T, A and B.

A and T can see each other through qnet.  B can not see either A or T. B
can ping A and T though (so IP works OK).

If T is named target and you do ls /net/target from B, does anything
appear.



-----Original Message-----
From: Eric Dong [mailto:eric.dongxx@gmail.com] 
Sent: Tuesday, June 24, 2008 11:19 AM
To: builds-networking
Subject: Re: RE: RE: RE: qnet problem under qnx6.3.2

thx, one target, machine A and machine B all with qnx 6.3.2 connected
via a hub. on the target and A, both can see each other under /net
directory. while B could only see itself. that's confusing... 

ps: could you please provide me with your explanation to my another
thread "script for two network cards?" got stuck quite a lot on my
current project. and do appreciate all of your responses so far. 

> And you were right that nicinfo looks as it should :) (but at least I
> know now that it's an Intel driver and that auto-negotiation is good
and
> there are no errors on the interface).
> 
> If you know the name of one of the other machines on the network, can
> you try an ls /net/name_of_other_computer and see if that works?  
> 
> One other point is that QNET is a layer 2 protocol that isn't routed.
> Are all of these hosts connected to the same layer 2 switch domain?
> 
> 
> 
> -----Original Message-----
> From: Eric Dong [mailto:eric.dongxx@gmail.com] 
> Sent: Tuesday, June 24, 2008 11:03 AM
> To: builds-networking
> Subject: Re: RE: RE: qnet problem under qnx6.3.2
> 
> yes, u guess is right. since the other hosts would be available under
> /net on the target, here is the output of nicinfo of the "wrong"
> machine:
> 
> INTEL 82558 Ethernet Controller
> 
>   Physical Node ID ........................... 000D60 106287
>   Current Physical Node ID ................... 000D60 106287
>   Current Operation Rate ..................... 100.00 Mb/s full-duplex
>   Active Interface Type ...................... MII
>     Active PHY address ....................... 1
>   Maximum Transmittable data Unit ............ 1514
>   Maximum Receivable data Unit ............... 1514
>   Hardware Interrupt ......................... 0xb
>   I/O Aperture ............................... 0x8000 - 0x803f
>   Memory Aperture ............................ 0xc0201000 - 0xc0201fff
>   Promiscuous Mode ........................... Off
>   Multicast Support .......................... Enabled
> 
>   Packets Transmitted OK ..................... 251
>   Bytes Transmitted OK ....................... 39582
>   Broadcast Packets Transmitted OK ........... 251
>   Multicast Packets Transmitted OK ........... 0
>   Memory Allocation Failures on Transmit ..... 0
> 
>   Packets Received OK ........................ 5285
>   Bytes Received OK .......................... 471963
>   Broadcast Packets Received OK .............. 5285
>   Multicast Packets Received OK .............. 0
>   Memory Allocation Failures on Receive ...... 0
> 
>   Single Collisions on Transmit .............. 0
>   Multiple Collisions on Transmit ............ 0
>   Deferred Transmits ......................... 0
>   Late Collision on Transmit errors .......... 0
>   Transmits aborted (excessive collisions) ... 0
>   Transmit Underruns ......................... 0
>   No Carrier on Transmit ..................... 0
>   Receive Alignment errors ................... 0
>   Received packets with CRC errors ........... 0
>   Packets Dropped on receive ................. 0
>   Short packets .............................. 0
>   Total Frames experiencing Collison(s) ...... 0
> 
>...