On Tue, Jun 22, 2004 at 05:21:59AM +0200, Anders Johansson wrote:
Strange, but could you post the routing table of a machine on the other LAN? If it has a similar error, it won't know how to reply
Here is the routing table of a W2K machine on wlan0 (192.168.0.2) of the server: Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.129 1 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 192.168.0.0 255.255.255.0 192.168.0.129 192.168.0.129 1 192.168.0.129 255.255.255.255 127.0.0.1 127.0.0.1 1 192.168.0.255 255.255.255.255 192.168.0.129 192.168.0.129 1 192.168.1.0 255.255.255.0 192.168.0.2 192.168.0.129 1 224.0.0.0 224.0.0.0 192.168.0.129 192.168.0.129 1 255.255.255.255 255.255.255.255 192.168.0.129 192.168.0.129 1 Default Gateway: 192.168.0.1 This machine can ping anthing on 192.168.0.0/24, it can ping the gateway 192.168.0.1, and it can ping eth0 in the server 192.168.1.2. It cannot ping anything on the 192.168.1.0/24 subnet attached to eth0. For reference here again is the routing table of my server: $sudo /sbin/route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 192.168.1.2 255.255.255.0 UG 0 0 0 eth0 192.168.0.0 192.168.0.2 255.255.255.0 UG 0 0 0 wlan0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 wlan0 Thanks, Henry