On Monday 09 June 2003 18:28, Roger wrote: > Around Mon,Jun 09 2003, at 10:06, Nick White, wrote: > > In RedHat 9 the 169.254.0.0/16 gets added to the routing table on > > boot. Probably to play nicely with windows boxen. In Windows > > 2000+, if there is no DHCP server available, an APIPA address > > (169.254.x.x) is assigned. > > Not just windows uses the 169.254.x.x I've seen Macs use it as well > as Windows. RFC-3330 defines the net block for use. > Does Redhat 9 always set the routing table for that block, or does it > get set when the DHCP server is slow to respond.
It appears that RH9 will add that route regardless of DHCP/STATIC/GOOD/BAD interface unless each and every /etc/sysconfig/network-scripts/ifcfg-* has the 'NOZEROCONF=yes' parameter. Odd, considering it's usual function of providing a IP address/route in case a valid one doesn't exist, but there it is. Mind you, I haven't read rfc-3330 mentioned above and it may actually advise this behavior but it's certainly different that has been used, admittedly by Microsoft, for the past 5 or so years. I think this is why everyone is scratching their heads trying to figure out why that route is there when there isn't any other "problem" with the interfaces. Regards, Mike Klinke -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
