generated from networkservicemesh/cmd-template
-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing IPv6 neighbors in VPP #864
Labels
bug
Something isn't working
Comments
Hi @zolug , Can we close the issue? |
Hi @glazychev-art, Yes, feel free to close the issue. Thanks. |
nsmbot
pushed a commit
that referenced
this issue
Oct 17, 2024
…k-vpp@main PR link: networkservicemesh/sdk-vpp#864 Commit: f8b5d51 Author: Network Service Mesh Bot Date: 2024-10-17 18:48:40 -0500 Message: - Update go.mod and go.sum to latest version from networkservicemesh/sdk-kernel@main (#864) PR link: networkservicemesh/sdk-kernel#692 Commit: 4f9e691 Author: Network Service Mesh Bot Date: 2024-10-17 18:45:10 -0500 Message: - Update go.mod and go.sum to latest version from networkservicemesh/sdk@main (#692) PR link: networkservicemesh/sdk#1686 Commit: 9a6b64b Author: dependabot[bot] Date: 2024-10-17 19:42:57 -0400 Message: - Bump github.com/nats-io/nkeys from 0.4.4 to 0.4.6 (#1686) Bumps [github.com/nats-io/nkeys](https://github.com/nats-io/nkeys) from 0.4.4 to 0.4.6. - [Release notes](https://github.com/nats-io/nkeys/releases) - [Changelog](https://github.com/nats-io/nkeys/blob/main/.goreleaser.yml) - [Commits](nats-io/nkeys@v0.4.4...v0.4.6) --- updated-dependencies: - dependency-name: github.com/nats-io/nkeys dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: NSMBot <nsmbot@networkservicmesh.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In case of an IPv6 cluster dynamic neighbor address resolution does not work, because ingress ACL rules drop ICMPv6 Neighbor Advertisement messages.
This for example might lead to non-working remote VxLAN xconnects. (In case a VPP instance started by the forwarder was not informed about a certain neighbor at start, or a new node is added to the cluster.)
Trace in vppctl:
The text was updated successfully, but these errors were encountered: