diff options
author | Stefano Brivio <sbrivio@redhat.com> | 2024-08-15 00:40:43 +0200 |
---|---|---|
committer | Stefano Brivio <sbrivio@redhat.com> | 2024-08-18 01:29:52 +0200 |
commit | f4e9f26480ef56ec09a871abf552cd2baac6cb10 (patch) | |
tree | 8b33e2144c9f92810e520b171843e3a405bb4f6b /tcp.c | |
parent | d6f022073124edd7a46fb849a8496d6ea6ce136f (diff) | |
download | passt-f4e9f26480ef56ec09a871abf552cd2baac6cb10.tar passt-f4e9f26480ef56ec09a871abf552cd2baac6cb10.tar.gz passt-f4e9f26480ef56ec09a871abf552cd2baac6cb10.tar.bz2 passt-f4e9f26480ef56ec09a871abf552cd2baac6cb10.tar.lz passt-f4e9f26480ef56ec09a871abf552cd2baac6cb10.tar.xz passt-f4e9f26480ef56ec09a871abf552cd2baac6cb10.tar.zst passt-f4e9f26480ef56ec09a871abf552cd2baac6cb10.zip |
pasta: Disable neighbour solicitations on device up to prevent DAD
As soon as we the kernel notifier for IPv6 address configuration
(addrconf_notify()) sees that we bring the target interface up
(NETDEV_UP), it will schedule duplicate address detection, so, by
itself, setting the nodad flag later is useless, because that won't
stop a detection that's already in progress.
However, if we disable neighbour solicitations with IFF_NOARP (which
is a misnomer for IPv6 interfaces, but there's no possibility of
mixing things up), the notifier will not trigger DAD, because it can't
be done, of course, without neighbour solicitations.
Set IFF_NOARP as we bring up the device, and drop it after we had a
chance to set the nodad attribute on the link.
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Diffstat (limited to 'tcp.c')
0 files changed, 0 insertions, 0 deletions