netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: "Ханкин Константин" <homecreate@list.ru>
Cc: netdev@vger.kernel.org
Subject: Re: Why linux keeps connected routes when link goes down
Date: Wed, 18 Feb 2009 16:04:36 -0800	[thread overview]
Message-ID: <20090218160436.44f19ea0@extreme> (raw)
In-Reply-To: <200902190203.41497.homecreate@list.ru>

On Thu, 19 Feb 2009 02:03:40 +0500
Ханкин Константин  <homecreate@list.ru> wrote:

> Hello!
> Why kernel keeps connected routes when link is not in RUNNING state? It's not 
> only linux behavior, some other OSes do so, but why?
> It's interesting for me because I have a problem with setting up Quagga for 
> OSPF support. When link goes down (!IFF_RUNNING), Quagga updates only its own 
> routing table. I must use ifplugd to update routes in kernel (actually to 
> delete connected route), but I think it is not a right way.
> So the main question is: why linux keeps connected routes when link goes down?
> PS: ``ip monitor'' reports about link fail after a minute or longer (on 
> 8139too and 3c905x). On some Acorp cards it doesn't notice link failure. Is it 
> a bad driver or crappy cards? On r8169 I have no problems

There are patches in Vyatta version of Quagga to what you want.
They have been submitted to quagga-developers but the community
process on quagga is much slower than the kernel.

      parent reply	other threads:[~2009-02-19  0:04 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
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 [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=20090218160436.44f19ea0@extreme \
    --to=shemminger@vyatta.com \
    --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).