Add option to set server MTU #1052
segevfiner
started this conversation in
Ideas
Replies: 3 comments
-
Does |
Beta Was this translation helpful? Give feedback.
0 replies
-
It sets the client MTU, but the server MTU is still set based on logic inside wg-quick. And I had a problem with Docker getting it wrong. I ended up configuring Docker to set the correct MTU for its interfaces in |
Beta Was this translation helpful? Give feedback.
0 replies
-
For those wondering, I did it like this in {
"mtu": 1460,
"default-network-opts": {
"bridge": {
"com.docker.network.driver.mtu": "1460"
}
}
} |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the bug
On GCP, the default VPC MTU is 1460, the default MTU of WireGuard is 1420 (1500 - 80) which is too large, a needs to be 1380 (1460 - 80), GCP VPC doesn't support IP fragmentation, which results in fragmented packages being dropped.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
For there to be a setting for the server MTU to fix this.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Basically we need a
WG_SERVER_MTU
that just generates the MTU directive into the WireGuard server config file, and we are set AFAIK.Beta Was this translation helpful? Give feedback.
All reactions