vpp-manager: fix DHCPv6 ip6tables hop-limit workaround#961
Draft
vpp-manager: fix DHCPv6 ip6tables hop-limit workaround#961
Conversation
Signed-off-by: Aritra Basu <aritrbas@cisco.com>
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
1 participant
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 removes the temporary DHCPv6 hop-limit workaround from
vpp-managerand updates the VPP clone script to consume a VPP build that includes the tap locally originated TTL/hop-limit fix.vpp-managerpreviously injected a host-sideip6tablesmangleOUTPUTrule for DHCPv6 (udp/546 -> udp/547) to force hop-limit=2. This was a workaround for packets sourced from the Linux host and entering VPP viatap, where consuming a router hop caused hop-limit/TTL=1 traffic to be dropped in forwarding paths.By relying on VPP’s tap locally originated handling, the solution is generic and protocol-agnostic for control-plane traffic sourced from the host namespace. This removes the need for DHCPv6-specific hacks and keeps node firewall state clean.