From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Andy Gospodarek <gospo@cumulusnetworks.com>,
netdev@vger.kernel.org, davem@davemloft.net,
ddutt@cumulusnetworks.com, sfeldma@gmail.com,
alexander.duyck@gmail.com, hannes@stressinduktion.org,
stephen@networkplumber.org
Subject: Re: [PATCH net-next 0/3 v4] changes to make ipv4 routing table aware of next-hop link status
Date: Wed, 17 Jun 2015 18:05:32 +0200 [thread overview]
Message-ID: <55819ACC.3010702@6wind.com> (raw)
In-Reply-To: <1434386001-1157-1-git-send-email-gospo@cumulusnetworks.com>
Le 15/06/2015 18:33, Andy Gospodarek a écrit :
> This series adds the ability to have the Linux kernel track whether or
> not a particular route should be used based on the link-status of the
> interface associated with the next-hop.
>
> Before this patch any link-failure on an interface that was serving as a
> gateway for some systems could result in those systems being isolated
> from the rest of the network as the stack would continue to attempt to
> send frames out of an interface that is actually linked-down. When the
> kernel is responsible for all forwarding, it should also be responsible
> for taking action when the traffic can no longer be forwarded -- there
> is no real need to outsource link-monitoring to userspace anymore.
>
> This feature is only enabled with the new per-interface or ipv4 global
> sysctls called 'ignore_routes_with_linkdown'.
>
> net.ipv4.conf.all.ignore_routes_with_linkdown = 0
> net.ipv4.conf.default.ignore_routes_with_linkdown = 0
> net.ipv4.conf.lo.ignore_routes_with_linkdown = 0
> ...
Sorry for my late reply, but is it possible to advertise this sysctl via the
netconf infra (grep NETCONFA_)?
Regards,
Nicolas
next prev parent reply other threads:[~2015-06-17 16:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 16:33 [PATCH net-next 0/3 v4] changes to make ipv4 routing table aware of next-hop link status Andy Gospodarek
2015-06-15 16:33 ` [PATCH net-next 1/3 v4] net: track link-status of ipv4 nexthops Andy Gospodarek
2015-06-18 10:26 ` David Miller
2015-06-18 14:55 ` Andy Gospodarek
2015-06-15 16:33 ` [PATCH net-next 2/3 v4] net: ipv4 sysctl option to ignore routes when nexthop link is down Andy Gospodarek
2015-06-18 10:27 ` David Miller
2015-06-15 16:33 ` [PATCH net-next 3/3 v4] iproute2: add support to print 'linkdown' nexthop flag Andy Gospodarek
2015-06-17 16:05 ` Nicolas Dichtel [this message]
2015-06-17 19:10 ` [PATCH net-next 0/3 v4] changes to make ipv4 routing table aware of next-hop link status Andy Gospodarek
2015-06-17 19:52 ` Nicolas Dichtel
2015-06-17 20:25 ` 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=55819ACC.3010702@6wind.com \
--to=nicolas.dichtel@6wind.com \
--cc=alexander.duyck@gmail.com \
--cc=davem@davemloft.net \
--cc=ddutt@cumulusnetworks.com \
--cc=gospo@cumulusnetworks.com \
--cc=hannes@stressinduktion.org \
--cc=netdev@vger.kernel.org \
--cc=sfeldma@gmail.com \
--cc=stephen@networkplumber.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.