V0.8.3 release candidate #56
Merged
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
…ill need to add outbound icmp and rule matching
…t in bpf_sk_splice5 which was limiting the number of allowed key matches to 1
…erfaceRules": false to match the non interface specific rules used in the example /opt/openziti/bin/user/user_rules.sh
…fw_tc_outbound_track.c that was preventing ipv6 support on loopback when appplied.
jlin-nf
approved these changes
Jul 10, 2024
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.
This pr was mainly created to introduce single interface ingress/egress filtering. While ingress filtering has always been supported, egress filtering has not. Prior to this PR if you wanted to filter outbound traffic it required two interfaces and only subtending client traffic could be filtered the WAN. This PR allows stateful filtering of both host and subtending client traffic with EBPF enabled only on the WAN facing interface.