Fix: ignore loopback NA during IPv6 DAD (RFC 4862, 5.4.3) #60
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- add edge case for loopback NA during IPv6 DAD Operation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses an edge case in Duplicate Address Detection (DAD)
where a node receives its own Neighbor Advertisement (NA) message
(broadcast via ff02::1) and mistakenly considers it as evidence of
address duplication, resulting in the unintended removal of its
link-local address.
According to RFC 4862 Section 5.4.3, such loopbacked messages must
not be interpreted as a sign of address duplication.
This patch adds a check to ensure that the source address of the
incoming NA does not match the node’s own address