Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Jandre Olivier <jandre@megaserve.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] simple routing query
Date: Fri, 11 Nov 2005 10:21:37 +0000	[thread overview]
Message-ID: <437470B1.4010703@megaserve.net> (raw)
In-Reply-To: <20051110174536.GA10440@tranquility.scriptkitchen.com>

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

      parent reply	other threads:[~2005-11-11 10:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-10 17:45 [LARTC] simple routing query Payal Rathod
2005-11-10 17:50 ` Brett Charbeneau
2005-11-10 18:33 ` Payal Rathod
2005-11-10 18:36 ` Brett Charbeneau
2005-11-10 18:42 ` Andreas Unterkircher
2005-11-10 18:47 ` Payal Rathod
2005-11-10 19:13 ` Andreas Unterkircher
2005-11-11 10:21 ` Jandre Olivier [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=437470B1.4010703@megaserve.net \
    --to=jandre@megaserve.net \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox