Hi, I have 2 interfaces - one for adsl and other for LAN on my Linux gateway machine. The IP addresses are 10.10.10.3 & 192.168.10.101 respectively. Now my routing tables show this particular entry. What exactly is this? 169.254.0.0/16 dev eth0 scope link Or by traditional route -n, 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 What exactly is this 169.254.0.0/16 thing? Thanks in advance. With warm regards, -Payal
On Thu, 10 Nov 2005, Payal Rathod wrote: PR> What exactly is this 169.254.0.0/16 thing? Remember - Google is your friend on stuff like this. Here''s a good rundown on the subject: http://www.cas.ilstu.edu/shac/Knowledge/Spam/iana.htm see the "Autoconfiguration" IP Addresses section. -- ******************************************************************** Brett Charbeneau Network Administrator Williamsburg Regional Library 7770 Croaker Road Williamsburg, VA 23188-7064 (757)259-4044 www.wrl.org (757)259-4079 (fax) brett@wrl.org ********************************************************************
On Thu, Nov 10, 2005 at 12:50:34PM -0500, Brett Charbeneau wrote:> http://www.cas.ilstu.edu/shac/Knowledge/Spam/iana.htm > > see the "Autoconfiguration" IP Addresses section.Yes, I read it, thnaks but I don''t understand it. | Addresses in the range 169.254.0.0 to 169.254.255.255 are used |automatically by some PCs and Macs when they are configured to use IP, |do not have a static IP Address assigned, and are unable to obtain an |IP address using DHCP. | |This traffic is intended to be confined to the local network, so the |administrator of the local network should look for misconfigured hosts. What do they mean by this? Is it at address given by error due to misconfiguaration. Payal
On Thu, 10 Nov 2005, Payal Rathod wrote: PR> What do they mean by this? Is it at address given by error due to PR> misconfiguaration. That''s always been my experience. If I were you I''d double-check the way your interfaces are configured. Something is goofy or not getting flushed or something - that 169.154.x.x address seems, in some hardware, to mean that there is confusion somewhere down the line. -- ******************************************************************** Brett Charbeneau Network Administrator Williamsburg Regional Library 7770 Croaker Road Williamsburg, VA 23188-7064 (757)259-4044 www.wrl.org (757)259-4079 (fax) brett@wrl.org ********************************************************************
I had such a experience with SuSE on a server with two network interface. While only one of them was connected to the lan with a fixed IP, the other was configured by YaST to get it''s IP from a DHCP server. Cause it can''t reach it and timed out, the interface didn''t get an IP address, but suddenly a 169.254.x.x route appeared. Probably you hit the same thing. Payal Rathod wrote:>On Thu, Nov 10, 2005 at 12:50:34PM -0500, Brett Charbeneau wrote: > > >>http://www.cas.ilstu.edu/shac/Knowledge/Spam/iana.htm >> >> see the "Autoconfiguration" IP Addresses section. >> >> > >Yes, I read it, thnaks but I don''t understand it. >| Addresses in the range 169.254.0.0 to 169.254.255.255 are used >|automatically by some PCs and Macs when they are configured to use IP, >|do not have a static IP Address assigned, and are unable to obtain an >|IP address using DHCP. >| >|This traffic is intended to be confined to the local network, so the >|administrator of the local network should look for misconfigured hosts. > >What do they mean by this? Is it at address given by error due to >misconfiguaration. > >Payal >_______________________________________________ >LARTC mailing list >LARTC@mailman.ds9a.nl >http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc > >
On Thu, Nov 10, 2005 at 07:42:06PM +0100, Andreas Unterkircher wrote:> I had such a experience with SuSE on a server with two network > interface. While only one of them was > connected to the lan with a fixed IP, the other was configured by YaST > to get it''s IP from a DHCP server.I too am on SuSE. One IP is my LAN IP but the SuSE box is the DHCP server itself. But many of my friend have seen this on their RedHat servers. 169.254.0.0/16 dev eth0 scope link Their machines had only 1 network card and had fixed IPs. What is the solution to this? With warm regards, -Payal
Solution? Leave it as it is or delete it :) It shouldn''t make any problem It''s a local block of ip addresses and don''t get routed. Cheers, Andreas PS: But perhaps dhcpcd or pump is running in background on due some miss configuration? Payal Rathod wrote:>On Thu, Nov 10, 2005 at 07:42:06PM +0100, Andreas Unterkircher wrote: > > >>I had such a experience with SuSE on a server with two network >>interface. While only one of them was >>connected to the lan with a fixed IP, the other was configured by YaST >>to get it''s IP from a DHCP server. >> >> > >I too am on SuSE. One IP is my LAN IP but the SuSE box is the DHCP >server itself. But many of my friend have seen this on their RedHat >servers. >169.254.0.0/16 dev eth0 scope link > >Their machines had only 1 network card and had fixed IPs. > >What is the solution to this? > >With warm regards, >-Payal > >
How do I disable the zeroconf route so that the system will boot without the 169.254.0.0 / 255.255.0.0 route? by Cynthia Davis Symptom: Every time the system boots, the zeroconf route (169.254.0.0) is enabled. You manually disable it by turning off the firewall and remove the route with 169.254.0.0 / 255.255.0.0 using the route command. Example output of the route with the zeroconf route enables would like similar to the following: # route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.15.50.0 * 255.255.252.0 U 0 0 0 eth0 169.254.0.0 * 255.255.0.0 U 0 0 0 eth0 Solution: To disable the zeroconf route during system boot, edit the /etc/sysconfig/network file and add the following NOZEROCONF value to the end of the file: NETWORKING=YES HOSTNAME=localhost.localdomain NOZEROCONF=yes Additional Information: Find out more about zeroconf at http://www.zeroconf.org/. Jandre Andreas Unterkircher wrote:> Solution? Leave it as it is or delete it :) It shouldn''t make any problem > It''s a local block of ip addresses and don''t get routed. > > Cheers, > Andreas > > PS: But perhaps dhcpcd or pump is running in background on due some > miss configuration? > > Payal Rathod wrote: > >> On Thu, Nov 10, 2005 at 07:42:06PM +0100, Andreas Unterkircher wrote: >> >> >>> I had such a experience with SuSE on a server with two network >>> interface. While only one of them was >>> connected to the lan with a fixed IP, the other was configured by >>> YaST to get it''s IP from a DHCP server. >>> >> >> >> I too am on SuSE. One IP is my LAN IP but the SuSE box is the DHCP >> server itself. But many of my friend have seen this on their RedHat >> servers. >> 169.254.0.0/16 dev eth0 scope link >> >> Their machines had only 1 network card and had fixed IPs. >> >> What is the solution to this? >> >> With warm regards, >> -Payal >> >> > > > _______________________________________________ > LARTC mailing list > LARTC@mailman.ds9a.nl > http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc-- /*---------------------------------------------------------------------*/ __ _ ---------- / / (_)__ __ ____ __ --------- ------- / /__/ / _ \/ // /\ \/ / -------- ---- /____/_/_//_/\_,_/ /_/\_\ ------ localhost@localdomain.za.net