Fix Egress with WireGuard encryption enabled #7628
Open
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
antoninbas
reviewed
Dec 12, 2025
Contributor
antoninbas
left a comment
antoninbas
left a comment
There was a problem hiding this comment.
We need to highlight somewhere that Egress traffic is not encrypted between the source Node and the Egress Node
cc @tnqn
xliuxu
force-pushed
the
topic/fix-wg-egress
branch
from
e5eed84 to
c4ef54a
Compare
When WireGuard encryption is enabled, Egress traffic from remote Pods needs tunnel-based forwarding and policy routing rules similar to hybrid mode. This commit removes the WireGuard exception from tunnel interface creation and adds the necessary OpenFlow flows and routing rules to support Egress functionality with WireGuard. Fixes: antrea-io#6190 Signed-off-by: Xu Liu <[email protected]>
xliuxu
force-pushed
the
topic/fix-wg-egress
branch
from
c4ef54a to
1af6b00
Compare
luolanzone
added
the
action/release-note
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
When WireGuard encryption is enabled, Egress traffic from remote Pods needs tunnel-based forwarding and policy routing rules similar to hybrid mode. This commit removes the WireGuard exception from tunnel interface creation and adds the necessary OpenFlow flows and routing rules to support Egress functionality with WireGuard.
Fixes: #6190