Repository navigation
fw: nat6 (NPTv6) connections stay out of the flowtable - #125
Merged
Merged
Conversation
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.
What
With nat6 policies, emit
meta nfproto ipv6 ct status snat ct state established accept(comment nat6-no-flowtable) after the access-control rules and beforeflow add @ft, so NPTv6-translated flows stay on the CPU path. No change without nat6 policies.Why
Once such a flow entered the flowtable its later packets stopped reaching the far end (QUIC handshakes over IPv6 failed). Step 1 of #124; the kernel-side root cause is still open.
Verification
Unit test (rule present, ordered between access control and flow add, absent without nat6), net.sh e2e asserts the loaded rule, full CI green.
Closes #124