Fix default MTU to 1420 as it has Wireguard kernel module set by defa… #660
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
|
I second this. I was having such weird problems, I thought I had messed up my firewall rules but then discovered that the MTU was 1450?? had to manually change it to wireguard's default MTU to get it working again. |
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.
Hello,
setting a MTU to 1450 by default in wireguard-ui makes tunnel created significantly downgraded performance as WG have 60byte header on IPv4 network and 80byte header on IPv6, so packet will get fragmented in both cases on standard 1500 MTU ethernet interface.
There should be sane default set and it can be changed in special circumastances