From: Bob Gilligan <gilligan@aristanetworks.com>
To: netdev@vger.kernel.org
Subject: No netlink notification for user-initiated NUD state change
Date: Tue, 26 Nov 2013 18:28:07 -0800 [thread overview]
Message-ID: <529558B7.5000506@aristanetworks.com> (raw)
Hi -- The neighbour code sends up an RTM_NEWNEIGH netlink notification
if the NUD state of a neighbour cache entry is changed by a timer (e.g.
from REACHABLE to STALE), even if the lladdr of the entry has not changed.
But a user-initiated change to the the NUD state of a neighbour cache
entry that does not change the lladdr (e.g. via "ip -4 neigh change ...
nud ...") does not trigger a netlink notification.
I'm wondering if that is intended behavior? Is there any reason not to
send a netlink notification in this case? The situation we've seen
where it would be nice to have these notifications is if a user changes
an existing resolved entry to PERMANENT.
This one-line change to neigh_update() would trigger netlink
notifications on all user-initiated state changes:
Index: linux-3.12.1/net/core/neighbour.c
===================================================================
--- linux-3.12.1.orig/net/core/neighbour.c
+++ linux-3.12.1/net/core/neighbour.c
@@ -1161,6 +1161,7 @@ int neigh_update(struct neighbour *neigh
neigh->parms->reachable_time :
0)));
neigh->nud_state = new;
+ notify = 1;
}
if (lladdr != neigh->ha) {
I'd be happy to submit a properly formatted patch if there's agreement
that this is an issue.
Bob.
next reply other threads:[~2013-11-27 2:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 2:28 Bob Gilligan [this message]
2013-12-10 17:15 ` No netlink notification for user-initiated NUD state change Nicolas Dichtel
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=529558B7.5000506@aristanetworks.com \
--to=gilligan@aristanetworks.com \
--cc=netdev@vger.kernel.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 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).