From: YOSHIFUJI Hideaki <hideaki.yoshifuji@miraclelinux•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
Cc: hideaki.yoshifuji@miraclelinux•com
Subject: Re: [PATCH net-next 2/3 v3] net: ipv4 sysctl option to ignore routes when nexthop link is down
Date: Thu, 11 Jun 2015 11:57:47 +0900 [thread overview]
Message-ID: <5578F92B.8060604@miraclelinux.com> (raw)
In-Reply-To: <1433990233-958-3-git-send-email-gospo@cumulusnetworks.com>
Hi,
Andy Gospodarek wrote:
> 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
:
> Signed-off-by: Andy Gospodarek <gospo@cumulusnetworks•com>
> Signed-off-by: Dinesh Dutt <ddutt@cumulusnetworks•com>
> ---
:
> diff --git a/kernel/sysctl_binary.c b/kernel/sysctl_binary.c
> index 7e7746a..c9d0a0e 100644
> --- a/kernel/sysctl_binary.c
> +++ b/kernel/sysctl_binary.c
> @@ -253,6 +253,7 @@ static const struct bin_table bin_net_ipv4_conf_vars_table[] = {
> { CTL_INT, NET_IPV4_CONF_NOPOLICY, "disable_policy" },
> { CTL_INT, NET_IPV4_CONF_FORCE_IGMP_VERSION, "force_igmp_version" },
> { CTL_INT, NET_IPV4_CONF_PROMOTE_SECONDARIES, "promote_secondaries" },
> + { CTL_INT, NET_IPV4_CONF_IGNORE_ROUTES_WITH_LINKDOWN, "ignore_routes_with_linkdown" },
> {}
> };
>
Please do not add new binary sysctl knob. Thank you.
--
Hideaki Yoshifuji <hideaki.yoshifuji@miraclelinux•com>
Technical Division, MIRACLE LINUX CORPORATION
next prev parent reply other threads:[~2015-06-11 2:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 2:37 [PATCH net-next 0/3 v3] changes to make ipv4 routing table aware of next-hop link status Andy Gospodarek
2015-06-11 2:37 ` [PATCH net-next 1/3 v3] net: track link-status of ipv4 nexthops Andy Gospodarek
2015-06-11 2:53 ` Scott Feldman
2015-06-11 3:28 ` Andy Gospodarek
2015-06-11 4:14 ` Scott Feldman
2015-06-11 6:07 ` Scott Feldman
2015-06-11 11:23 ` Andy Gospodarek
2015-06-11 14:47 ` Scott Feldman
2015-06-11 14:50 ` Alexander Duyck
2015-06-11 15:25 ` Scott Feldman
2015-06-11 16:53 ` Dinesh Dutt
2015-06-11 2:37 ` [PATCH net-next 2/3 v3] net: ipv4 sysctl option to ignore routes when nexthop link is down Andy Gospodarek
2015-06-11 2:57 ` YOSHIFUJI Hideaki [this message]
2015-06-11 3:00 ` Scott Feldman
2015-06-11 3:36 ` Andy Gospodarek
2015-06-11 4:32 ` David Miller
2015-06-11 19:35 ` Andy Gospodarek
2015-06-11 2:37 ` [PATCH net-next 3/3 v3] iproute2: add support to print 'linkdown' nexthop flag Andy Gospodarek
2015-06-11 3:02 ` Scott Feldman
2015-06-11 3:13 ` Andy Gospodarek
2015-06-11 3:07 ` [PATCH net-next 0/3 v3] changes to make ipv4 routing table aware of next-hop link status Scott Feldman
2015-06-11 3:19 ` Andy Gospodarek
2015-06-11 3:33 ` Andy Gospodarek
2015-06-11 15:44 ` Scott Feldman
2015-06-11 18:17 ` 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=5578F92B.8060604@miraclelinux.com \
--to=hideaki.yoshifuji@miraclelinux$(echo .)com \
--cc=alexander.duyck@gmail$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=ddutt@cumulusnetworks$(echo .)com \
--cc=gospo@cumulusnetworks$(echo .)com \
--cc=hannes@stressinduktion$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sfeldma@gmail$(echo .)com \
--cc=stephen@networkplumber$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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