All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: Patrick McHardy <kaber@trash.net>
Cc: Stephen Hemminger <stephen.hemminger@vyatta.com>,
	Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
	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 09:31:59 -0700	[thread overview]
Message-ID: <20080603093159.36070e73@extreme> (raw)
In-Reply-To: <48456B62.8050909@trash.net>

On Tue, 03 Jun 2008 18:03:46 +0200
Patrick McHardy <kaber@trash.net> wrote:

> Stephen Hemminger wrote:
> > 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'
> 
> 
> Can't the routing daemon simply ignore routes with a
> device that has no carrier?
> 

It does that, but the problem is that packets get routed in kernel
to interfaces without carrier, rather than being correctly rerouted
over alternate paths.

  reply	other threads:[~2008-06-03 16:32 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
2008-06-03 16:03     ` Patrick McHardy
2008-06-03 16:31       ` Stephen Hemminger [this message]
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=20080603093159.36070e73@extreme \
    --to=shemminger@vyatta.com \
    --cc=davem@davemloft.net \
    --cc=kaber@trash.net \
    --cc=lsorense@csclub.uwaterloo.ca \
    --cc=netdev@vger.kernel.org \
    --cc=stephen.hemminger@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.