Adding automatic setting of ndisc_notify kernel parameter to 1 on all DANM managed V6 interfaces #222
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
… V6 interfaces. This is required to ensure when a previously allocated IP moves to another host the change is propagated throughout the fabric.
Levovar
changed the title
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 is required to ensure when a previously allocated IP moves to another host the change is propagated throughout the fabric.
In case of IPv4 we achieve the same effect by sending a gARP Reply through the interface, but this mechanism does not exist for IPv6. Previously we thought it is because such mechanism happens automatically in the kernel, however as we recently found out this functionality seemed to be configurable via the ndisc_notify kernel setting:
https://sysctl-explorer.net/net/ipv6/ndisc_notify/