docs: Remove outdated note on IPv6 BPF masqerading being incompatible with the Host Firewall #32685
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
Since commits 9c1031e ("bpf: fix missing ipv6 ct entry for snated traffic") and cfed66e ("Revert "daemon: Forbid IPv6 BPF masquerading with the host firewall""), IPv6 BPF masquerading is compatible with the Host Firewall. The documentation still states the opposite, as we forgot to remove the related note. Clean it up now. Signed-off-by: Quentin Monnet <[email protected]>
qmonnet
added
area/documentation
|
/test |
lambdanis
approved these changes
May 24, 2024
maintainer-s-little-helper
bot
added
the
ready-to-merge
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.
Since commits 9c1031e ("bpf: fix missing ipv6 ct entry for snated traffic") and cfed66e ("Revert "daemon: Forbid IPv6 BPF masquerading with the host firewall""), IPv6 BPF masquerading is compatible with the Host Firewall. The documentation still states the opposite, as we forgot to remove the related note. Clean it up now.