From: David Ahern <dsahern@gmail.com>
To: netdev@vger.kernel.org
Cc: jhs@mojatatu.com, David Ahern <dsahern@gmail.com>,
Satish Ashok <sashok@cmulusnetworks.com>
Subject: [PATCH net-next 3/3] net: ipv6: flush neighbor entries when carrier is off
Date: Sun, 5 Nov 2017 22:57:53 -0800 [thread overview]
Message-ID: <1509951473-25990-4-git-send-email-dsahern@gmail.com> (raw)
In-Reply-To: <1509951473-25990-1-git-send-email-dsahern@gmail.com>
Similar to IPv4, flush non-permanent neighbor entries on carrier down
to improve path selection for multipath routes.
Signed-off-by: Satish Ashok <sashok@cmulusnetworks.com>
Signed-off-by: David Ahern <dsahern@gmail.com>
---
net/ipv6/addrconf.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/net/ipv6/addrconf.c b/net/ipv6/addrconf.c
index 5a8a10229a07..85bddff5eac6 100644
--- a/net/ipv6/addrconf.c
+++ b/net/ipv6/addrconf.c
@@ -3432,6 +3432,9 @@ static int addrconf_notify(struct notifier_block *this, unsigned long event,
run_pending = 1;
}
} else if (event == NETDEV_CHANGE) {
+ if (idev && idev->cnf.ignore_routes_with_linkdown)
+ neigh_carrier_down(&nd_tbl, dev);
+
if (!addrconf_link_ready(dev)) {
/* device is still not ready. */
break;
--
2.1.4
next prev parent reply other threads:[~2017-11-06 6:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 6:57 [PATCH net-next 0/3] net: flush neighbor entries when carrier is off David Ahern
2017-11-06 6:57 ` [PATCH net-next 1/3] net: neigh: Add helper to flush entries on carrier down David Ahern
2017-11-06 6:57 ` [PATCH net-next 2/3] net: ipv4: flush neighbor entries when carrier is off David Ahern
2017-11-06 10:47 ` Ido Schimmel
2017-11-06 14:49 ` David Ahern
2017-11-07 5:29 ` David Ahern
2017-11-06 6:57 ` David Ahern [this message]
[not found] ` <CAKYOsXz3RFqbzENy1rz8kjsr3aF0u2kxBHrSQ3uNfFfQTWbJRQ@mail.gmail.com>
2017-11-08 3:39 ` [PATCH net-next 0/3] net: " David Miller
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=1509951473-25990-4-git-send-email-dsahern@gmail.com \
--to=dsahern@gmail.com \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=sashok@cmulusnetworks.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).