From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jandre Olivier Date: Fri, 11 Nov 2005 10:21:37 +0000 Subject: Re: [LARTC] simple routing query Message-Id: <437470B1.4010703@megaserve.net> List-Id: References: <20051110174536.GA10440@tranquility.scriptkitchen.com> In-Reply-To: <20051110174536.GA10440@tranquility.scriptkitchen.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lartc@vger.kernel.org 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 _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc