Jeff Hoare pecked at the keyboard and wrote:
Hi,
Why is there a route to 169.254.x network on the same interface as the 192.168.x network? 169.x networks are usually given out after a failure to get an address via dhcp (unless you are using the 169 network)
Regards Jeff
On Fri, 12 Dec 2008 04:37:46 Andy Harrison wrote:
On Thu, Dec 11, 2008 at 10:10 AM, Ken Schneider
wrote: Almost sounds like a routing issue instead of a dns issue. Could you please post the results of route -n?
# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 172.24.0.0 0.0.0.0 255.255.254.0 U 0 0 0 eth3 192.168.0.0 0.0.0.0 255.255.240.0 U 0 0 0 eth0 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.1.1 0.0.0.0 UG 0 0 0 eth0
That in itself is not unusual what is unusual is that the 172.24.0.0 network is using the 192.168.1.1 gateway. Could you explain a little more about your network setup especially the eth3 interface? -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org