From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: David Miller <davem@davemloft.net>
Cc: homecreate@list.ru, netdev@vger.kernel.org
Subject: Re: Why linux keeps connected routes when link goes down
Date: Fri, 20 Feb 2009 12:19:12 -0500 [thread overview]
Message-ID: <20090220171912.GA7315@csclub.uwaterloo.ca> (raw)
In-Reply-To: <20090218.155207.139931991.davem@davemloft.net>
On Wed, Feb 18, 2009 at 03:52:07PM -0800, David Miller wrote:
> Because the IP addresses are still assigned to the interface.
>
> IP addresses are owned by the "host" rather than specific interfaces
> under Linux. So just bringing an interface down does not disable
> IP addresses configured to that interface.
>
> If you want all the routes to go away, explicitly delete the IP
> addresses.
An interface IP address and the router to the connected subnet are not
the same thing. Keep the IP address but drop the route to the subnet
you can no longer reach.
By elliminating the route to stuff you can no longer reach, quagga can
do its job to provide an alternative way to reach the subnet. It can
not do so as long as the kernel insist on providing a now useless route.
--
Len Sorensen
next prev parent reply other threads:[~2009-02-20 17:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 21:03 Why linux keeps connected routes when link goes down Ханкин Константин
2009-02-18 23:52 ` David Miller
2009-02-19 6:22 ` Ханкин Константин
2009-02-20 17:19 ` Lennart Sorensen [this message]
2009-02-20 20:15 ` David Miller
2009-02-23 14:38 ` Lennart Sorensen
2009-02-23 18:02 ` Ханкин Константин
2009-02-23 21:14 ` Lennart Sorensen
2009-02-23 21:38 ` Stephen Hemminger
2009-02-23 23:41 ` David Miller
2009-02-23 23:33 ` David Miller
2009-02-24 18:52 ` Lennart Sorensen
2009-02-19 0:04 ` Stephen Hemminger
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=20090220171912.GA7315@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=davem@davemloft.net \
--cc=homecreate@list.ru \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).