netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Andy Gospodarek <gospo@cumulusnetworks.com>,
	Scott Feldman <sfeldma@gmail.com>
Cc: Netdev <netdev@vger.kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	ddutt@cumulusnetworks.com
Subject: Re: [PATCH net-next] net: change fib behavior based on interface link status
Date: Wed, 03 Jun 2015 22:04:06 +0200	[thread overview]
Message-ID: <1433361846.719897.286115305.0CA7D2AA@webmail.messagingengine.com> (raw)
In-Reply-To: <20150603182718.GK588@gospo.home.greyhouse.net>

On Wed, Jun 3, 2015, at 20:27, Andy Gospodarek wrote:
> On Wed, Jun 03, 2015 at 11:15:55AM -0700, Scott Feldman wrote:
> > On Tue, Jun 2, 2015 at 8:07 PM, Andy Gospodarek
> > <gospo@cumulusnetworks.com> wrote:
> > > This feature is only enabled with the new sysctl set (default is off):
> > > net.core.kill_routes_on_linkdown = 1
> > 
> > One more thing, sorry.  This feature is typically implemented today in
> > user-space on a per-interface basis.  The example I'm thinking of is
> > Quagga's "link-detect" directive which goes on an interface.  Should
> > this be a bool on each interface in systcl?  That would let user not
> > enable on selected interfaces.
> That would not be my preference.
> 
> I'm willing to investigate the per-namespace support if Hannes would
> like and add switchdev support for v2, but would prefer this not become
> that granular.

Actually, this idea also came to my mind: flagging specific routes if
they are eligible to suppress if the link is down.

Bye,
Hannes

  parent reply	other threads:[~2015-06-03 20:04 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03  3:07 [PATCH net-next] net: change fib behavior based on interface link status Andy Gospodarek
2015-06-03  5:03 ` Scott Feldman
2015-06-03 15:12   ` Andy Gospodarek
2015-06-03 17:40     ` Scott Feldman
2015-06-03 17:57       ` Andy Gospodarek
2015-06-03 18:12         ` Scott Feldman
2015-06-03 18:16           ` Andy Gospodarek
2015-06-03  9:35 ` Hannes Frederic Sowa
2015-06-03 13:49   ` Andy Gospodarek
2015-06-03 13:53 ` Neil Horman
2015-06-03 14:13   ` Hannes Frederic Sowa
2015-06-03 14:21     ` Neil Horman
2015-06-03 14:45       ` Hannes Frederic Sowa
2015-06-03 14:46       ` Andy Gospodarek
2015-06-03 15:02         ` Neil Horman
2015-06-03 15:16           ` Andy Gospodarek
2015-06-03 17:47             ` Neil Horman
2015-06-03 15:17           ` Hannes Frederic Sowa
2015-06-03 14:03 ` Hannes Frederic Sowa
2015-06-03 14:24   ` Andy Gospodarek
2015-06-03 18:15 ` Scott Feldman
2015-06-03 18:27   ` Andy Gospodarek
2015-06-03 19:03     ` Scott Feldman
2015-06-03 20:11       ` Andy Gospodarek
2015-06-03 20:04     ` Hannes Frederic Sowa [this message]
2015-06-03 20:34       ` Andy Gospodarek
2015-06-03 20:36         ` Hannes Frederic Sowa
2015-06-03 18:25 ` Alexander Duyck
2015-06-03 20:02   ` Andy Gospodarek
2015-06-03 21:01     ` Alexander Duyck
2015-06-05 19:05       ` Andy Gospodarek

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=1433361846.719897.286115305.0CA7D2AA@webmail.messagingengine.com \
    --to=hannes@stressinduktion.org \
    --cc=davem@davemloft.net \
    --cc=ddutt@cumulusnetworks.com \
    --cc=gospo@cumulusnetworks.com \
    --cc=netdev@vger.kernel.org \
    --cc=sfeldma@gmail.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 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).