bruce wrote: > hi john... > > i might be missing/lost some emails... so let me start at the very > beginning!! bear with me if you find yourself repeating something you've > already stated... > > my initial system (two boxes, nothing between them) > > windows linux > box1 ----- >>> ------ box2 >>>>>> (future separate lan box) > eth0 (wireless) ath0 eth0 > > box1 > eth0 - 192.168.1.3 > > box2 > ath0 - 192.168.1.5 > eth0 - 192.168.2.5 > > from box1, i can ping 192.168.1.5 > from box1, i can't ping 192.168.2.5 > > from box2, i can ping box1 (192.168.1.3) > > so, what do i/should i do to connect/ping box2/eth0 from box1? > Unless your Windows box knows that 192.168.1.5 is the gateway to 192.168.2.5, it is not going to be able to ping it. It will send the packets for 192.168.2.5 using the default route, and using the default gateway. This is probably 192.168.1.1. But the router on 192.168.1.1 does not know what to do with it, so it does not send it to 192.168.1.5 to be forwarded to 192.168.2.5. So you either have to add a route to the windows box, or to the router. Chances are, the linux box never "sees" the packets for 192.168.2.5, and in any case the MAC address the packet is sent to is not for that machine. The wireless box never sends the packets for 192.168.2.5 over the wireless link. But as I said before, you are trying to use the wrong tool for the job. You would be much better off bridging ath0 and eth0 on the Linux box, and putting everything on the 192.168.1.0 network. Mikkel -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting a bad thing?
Description: OpenPGP digital signature