diff options
| author | Mike Manning <mmanning@brocade.com> | 2017-09-25 22:01:36 +0100 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2017-09-30 05:24:45 +0100 |
| commit | 1f372c7bfb23286d2bf4ce0423ab488e86b74bb2 (patch) | |
| tree | 087fce5cfda51c9ea699848173ec1fc3152ae982 /kernel | |
| parent | fa8fefaa678ea390b873195d19c09930da84a4bb (diff) | |
| download | linux-1f372c7bfb23286d2bf4ce0423ab488e86b74bb2.tar.bz2 | |
net: ipv6: send NS for DAD when link operationally up
The NS for DAD are sent on admin up as long as a valid qdisc is found.
A race condition exists by which these packets will not egress the
interface if the operational state of the lower device is not yet up.
The solution is to delay DAD until the link is operationally up
according to RFC2863. Rather than only doing this, follow the existing
code checks by deferring IPv6 device initialization altogether. The fix
allows DAD on devices like tunnels that are controlled by userspace
control plane. The fix has no impact on regular deployments, but means
that there is no IPv6 connectivity until the port has been opened in
the case of port-based network access control, which should be
desirable.
Signed-off-by: Mike Manning <mmanning@brocade.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions