From: Stephen Hemminger <stephen.hemminger@vyatta.com>
To: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
Cc: Stephen Hemminger <shemminger@vyatta.com>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] IPV4: remove addresses and routes when carrier is lost
Date: Tue, 3 Jun 2008 08:57:07 -0700 [thread overview]
Message-ID: <20080603085707.51fdabbb@speedy> (raw)
In-Reply-To: <20080603150524.GA16165@csclub.uwaterloo.ca>
On Tue, 3 Jun 2008 11:05:24 -0400
lsorense@csclub.uwaterloo.ca (Lennart Sorensen) wrote:
> On Mon, Jun 02, 2008 at 04:52:49PM -0700, Stephen Hemminger wrote:
> > This patch adds a new configuration sysctl that causes link loss to clear
> > FIB state in the same way as admin down. This allows for routing daemons
> > like Quagga which have option to remove routes when carrier is lost.
> >
> > This has been a long standing problem with Quagga on Linux with complaints
> > on the developers list going back to 2004. Fixing it properly, so the routing
> > daemon manages the RIB, and the kernel manages the FIB, requires changes to
> > both parts.
>
> Does this cover only the local route for the interface, or all routes
> assigned staticly to the interface too?
The patch makes carrier down == interface down. So the same
behaviour as doing 'ip link set dev eth3 down'
> Certianly if I do ifconfig eth3 down, it removes all the routes, but
> doing ifconfig eth3 up only adds back the directly connected network
> based on the IP and netmask, but my static routes are gone which is a
> problem.
If you are using a routing daemon like quagga, it will restore your static
routes.
> I have been considering writing a user space daemon to listen on netlink
> for link up/down events to remove routes from the routing table and then
> add them back when the link is restored since I couldn't find a good way
> to make the kernel remember the static routes when the link was brought
> down.
That is pretty much what zebra portion of quagga does.
next prev parent reply other threads:[~2008-06-03 15:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-02 23:52 [PATCH 1/2] IPV4: remove addresses and routes when carrier is lost Stephen Hemminger
2008-06-02 23:53 ` [PATCH 1/2] IPV6: " Stephen Hemminger
2008-06-03 16:17 ` YOSHIFUJI Hideaki / 吉藤英明
2008-06-03 17:21 ` Stephen Hemminger
2008-06-03 17:25 ` David Miller
2008-06-03 17:28 ` Patrick McHardy
2008-06-03 17:31 ` David Miller
2008-06-03 17:28 ` YOSHIFUJI Hideaki / 吉藤英明
2008-06-03 17:30 ` David Miller
2008-06-03 17:46 ` Stephen Hemminger
2008-06-03 17:53 ` David Miller
2008-06-03 18:34 ` Stephen Hemminger
2008-06-03 19:06 ` David Miller
2008-06-03 21:40 ` Stephen Hemminger
2008-06-03 15:05 ` [PATCH 1/2] IPV4: " Lennart Sorensen
2008-06-03 15:57 ` Stephen Hemminger [this message]
2008-06-03 16:03 ` Patrick McHardy
2008-06-03 16:31 ` Stephen Hemminger
2008-06-03 16:44 ` Patrick McHardy
2008-06-03 21:45 ` Lennart Sorensen
2008-06-03 22:32 ` Patrick McHardy
2008-06-04 13:53 ` Lennart Sorensen
2008-06-03 21:44 ` Lennart Sorensen
2008-06-06 14:56 ` Lennart Sorensen
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=20080603085707.51fdabbb@speedy \
--to=stephen.hemminger@vyatta.com \
--cc=davem@davemloft.net \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.