On Tue, Mar 18, 2008 at 05:30:48AM -0400, Jacob Dall wrote:
> We've installed a qnx6.3.2 box in the wild, connecting to it over a wireless network. 
> 
> The setup is as follows (- is wired, ~ is wireless):
> 
> PC (192.168.1.10) 
> <-> 
> (192.168.1.253) Gateway (192.168.2.254) 
> <-> 
> Access Point (192.168.2.253) 
> <~> 
> Bridge (192.168.2.160) 
> <-> 
> box (192.168.2.142)
> laptop (192.168.2.143)
>            
>   
> Now, having powered up the box, I telnet to the box and execute
> 
> # route show
> Routing tables
> 
> Internet:
> Destination       Gateway            Flags
> localhost.localdo 127.0.0.1          UH
> 192.168.2.0       link#2             U
> 192.168.2.143     00:16:d3:57:96:46  UH
> 
> # arp -a
> ? (192.168.2.143) at 00:16:d3:57:96:46 on en0
> 
> 
> From the PC, I try and ping the box:
> 
> > ping 192.168.2.142
> Pinging 192.168.2.142 with 32 bytes of data:
> 
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> 
> Ping statistics for 192.168.2.142:
>     Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
> 
> 
> Back in the box, pinging the gateway (that blocks ping from wan):
> 
> # ping -c 1 192.168.2.254
> PING 192.168.2.254 (192.168.2.254): 56 data bytes
> 
> ----192.168.2.254 PING Statistics----
> 1 packets transmitted, 0 packets received, 100% packet loss
> 
> 
> And, again from the PC, pinging the box
> 
> >ping 192.168.2.142
> 
> Pinging 192.168.2.142 with 32 bytes of data:
> 
> Reply from 192.168.2.142: bytes=32 time=2ms TTL=255
> Reply from 192.168.2.142: bytes=32 time=2ms TTL=255
> 
> Ping statistics for 192.168.2.142:
>     Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
>     Minimum = 2ms, Maximum = 2ms, Average = 2ms
> 
> 
> For the last time, at the box:
> 
> # route show
> Routing tables
> 
> Internet:
> Destination       Gateway            Flags
> localhost.localdo 127.0.0.1          UH
> 192.168.2.0       link#2             U
> 192.168.2.143     00:16:d3:57:96:46  UH
> 192.168.2.254     00:1c:f0:4e:71:9b  UH
> 
> # arp -a
> ? (192.168.2.143) at 00:16:d3:57:96:46 on en0
> ? (192.168.2.254) at 00:1c:f0:4e:71:9b on en0
> 
> 
> So, in plain english, one can not initially ping the box from the LAN. 
> Doing a ping of the gateway from the box, one can now ping the box.
> 
> But waiting a few minutes, then another ping from LAN fails. 
> 'route show' and 'arp -a' shows the same info as previously, when the ping succeded.
> The only way (so far) to get that ping from LAN working again, is to do another ping from the box.
> 
> I've tried to make the mac address of the gateway permanent upon startup of the box (arp -s 192.168.2.254 00:1c:f0:4e:
71:9b) - it changes absolutely nothing. Only way around is to do a ping from the box.
> 
> So, can someone please tell me what's going on? 
> What have I missed? 
> Is this an arp cache issue? 
> Any ideas how to solve this?
> 
> Thanks,
> Jacob dall
> 

I don't see how this could ever work.  If you try pinging
the 'pc' from the 'box' in this configuration you should get
'no route to host'.  You need to add a route to network
192.168.1 on the 'box':

# route add -net 192.168.1/24 192.168.2.254

-seanb