Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Don't create tunnel interface (antrea-tun0) when using Wireguard #5885

Merged
merged 1 commit into from
Jan 19, 2024
Merged

Don't create tunnel interface (antrea-tun0) when using Wireguard #5885

merged 1 commit into from
Jan 19, 2024

Commits on Jan 17, 2024

  1. Don't create tunnel interface (antrea-tun0) when using Wireguard 

    When using Wireguard for inter-Node traffic, there is no need to create
the OVS tunnel port (antrea-tun0) interface, as traffic will go through
antrea-wg0, which is managed by Linux directly.

The exception is when using Multi-cluster (in gateway mode), as
antrea-tun0 is then still used for cross-cluster traffic, for example to
tunnel traffic from the source Node to the local gateway Node.

Fixes antrea-io#5869

Signed-off-by: Antonin Bas <[email protected]>
    @antoninbas
    antoninbas committed Jan 17, 2024
    Configuration menu
    Copy the full SHA
    1caf9ed View commit details
    Browse the repository at this point in the history