feat(natgw): extended nexthop support to advertise ipv4 NRLI over ipv6 sessions #4704
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
…6 sessions Signed-off-by: SkalaNetworks <contact@skala.network>
dosubot
bot
added
size:S
zhangzujian
approved these changes
Nov 7, 2024
zbb88888
pushed a commit
that referenced
this pull request
Nov 27, 2024
…6 sessions (#4704) Signed-off-by: SkalaNetworks <contact@skala.network>
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.
Currently, it is not possible to use only IPv6 sessions between NAT gateways running in BGP mode/Kube-OVN speakers and remote BGP servers.
IPv4 prefixes are never advertised to IPv6 neighbors.
This patch introduces extended-nexthop support to fix this problem.