On Thu, 2005-01-13 at 18:32 -0500, Bill Moss wrote: > I see the same thing at the office. The default line in > > [~] $ /sbin/route > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use Iface > 192.168.2.0 * 255.255.255.0 U 0 0 0 eth1 > 169.254.0.0 * 255.255.0.0 U 0 0 0 lo > default 192.168.2.1 0.0.0.0 UG 0 0 0 eth1 > default * 0.0.0.0 U 0 0 0 eth1 > > may be generated by whatever application is generating the link local > address 169.254.0.0. No, I don't think so. I did repeated calls top /sbin/route while NM does it's discovery and configuration. This is how it looks before NM brings up eth1 Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 169.254.0.0 * 255.255.0.0 U 0 0 0 lo then comes Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 169.254.0.0 * 255.255.0.0 U 0 0 0 lo default * 0.0.0.0 U 0 0 0 eth1 and finally Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.2.0 * 255.255.255.0 U 0 0 0 eth1 169.254.0.0 * 255.255.0.0 U 0 0 0 lo default 192.168.2.1 0.0.0.0 UG 0 0 0 eth1 default * 0.0.0.0 U 0 0 0 eth1 So I strongly suggest that it's NM at work here. (first and last displays are maybe 5 seconds apart) jtl
Attachment:
signature.asc
Description: This is a digitally signed message part