feat: auto-detect WireGuard MTU from underlay interface #406
+83
−4
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.
Summary
--mtuflag default from a fixed1420to"auto", which detects the MTU of the underlay network interface and subtracts the WireGuard overhead (80 bytes)Motivation
In multi-cloud deployments, different locations may have different underlay MTUs (e.g. 1500 on bare metal vs 1400 on Azure). A fixed MTU causes packet fragmentation or drops when the underlay MTU is smaller than expected. Auto-detection eliminates the need for per-node MTU configuration.
Changes
pkg/wireguard/wireguard.go: AddWireGuardOverheadconstant (80 bytes) andSetMTU()helperpkg/mesh/mesh.go: AdddetectMTU()function,mtu/autoMTUfields, MTU re-detection inapplyTopology()cmd/kg/main.go: Change--mtuflag fromuinttostringwith"auto"default