From: Stephen Hemminger <shemminger@vyatta.com>
To: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
Cc: ???????????? ???????????????????? <homecreate@list.ru>,
netdev@vger.kernel.org
Subject: Re: Why linux keeps connected routes when link goes down
Date: Mon, 23 Feb 2009 13:38:15 -0800 [thread overview]
Message-ID: <20090223133815.6acd817d@extreme> (raw)
In-Reply-To: <20090223211411.GI23244@csclub.uwaterloo.ca>
On Mon, 23 Feb 2009 16:14:11 -0500
lsorense@csclub.uwaterloo.ca (Lennart Sorensen) wrote:
> On Mon, Feb 23, 2009 at 11:02:55PM +0500, ???????????? ???????????????????? wrote:
> > Can I hope that it will be done some day?
>
> I don't have much hope that the kernel will ever be changed to behave
> as desired for a router.
>
> > Linux is used as router in many places, such behavior is a suicide. Of course,
> > one can use ifplugd (so do I), but it's a crap for network OS, don't you think
> > so?
>
> Well you will need some user space support to handle static routes,
> unless you want to make major changes to the kernel route management.
> We use zebra to manage static routes when the link goes up or down, with
> the kernel simply patched to delete the subnet route when an interface
> goes down, and re add it when it comes back up. All other routes are
> handled by zebra.
>
> With the current patch I am using all routes assigned to an interface goes
> away when the link goes down, but the kernel only recreates the directly
> connected network's route when it comes up. Any other static routes
> have to be recreated by user space, hence the user of zebra for that.
>
> Better and more friendly would be if routes could be marked inactive
> and ignored by the kernel for routing decisions when a link went down.
> That way multiple routes with different metrics could be used with the
> best one who's link is up would be in use. I find this too much to try
> and put into the kernel though, so I will stick to zebra for that task.
>
> > Who made linux network subsystem? Can Linus Torvalds say some words about this
> > problem?
> >
> > I'm not a developer, but network administrator. So I can't make a patch. I can
> > only find a solution or make it. So please make my work a bit easier
>
Like I said already, it is possible to fix Quagga; we have done it the
patches are available. unfortunately quagga is without a real
software maintenance infrastructure at this point.
next prev parent reply other threads:[~2009-02-23 21:38 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
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 [this message]
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=20090223133815.6acd817d@extreme \
--to=shemminger@vyatta.com \
--cc=homecreate@list.ru \
--cc=lsorense@csclub.uwaterloo.ca \
--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 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.