Your 'route -n' output should look similar to
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
<LAN here> 0.0.0.0 <LAN netmask> U 0 0 0 eth0
0.0.0.0 <gateway here> 0.0.0.0 UG 0 0 0 eth0
Does the gateway belong to a different network than the addresses it gives out via DHCP? The dhcp server here at work does that to clients it doesn't know - and they, too, can ping lo and their own eth address, but won't get anywhere else.
Even if your routing table lists an explicit rule to the gateway, the gateway in turn has to know how to talk back to you - which wouldn't be the case in the above scenario. :) |
