vpp-manager: Add static neighbor for LL address on tap0#938
Merged
Conversation
This patch adds a static neighbor for the node's LinkLocal address on tap0. This simplify things as we know the node's link local in advance and use it for other purposes, so we save a resolution. Also we do not yet support it changing. Finally if we do not have this, we learn the neighbor through gratuitous requests from linux to ND proxy and NS/ND, but as we do not have a glean toward linux, we cannot learn the neighbor if packets are coming from the uplink without prior linux initiated sollicits. As an example DHCPv6 sollicts replies need forwarding and we might have forgotten the neighbor by then. Signed-off-by: Nathan Skrzypczak <nathan.skrzypczak@gmail.com>
5fe7821 to
bb4aa89
Compare
aritrbas
approved these changes
Mar 2, 2026
This file contains hidden or 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
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 patch adds a static neighbor for the node's LinkLocal
address on tap0. This simplify things as we know the node's
link local in advance and use it for other purposes, so we
save a resolution. Also we do not yet support it changing.
Finally if we do not have this, we learn the neighbor through
gratuitous requests from linux to ND proxy and NS/ND, but as
we do not have a glean toward linux, we cannot learn the neighbor
if packets are coming from the uplink without prior linux
initiated sollicits. As an example DHCPv6 sollicts replies
need forwarding and we might have forgotten the neighbor by then.