From d0a693466e434a30dac86ea216f494ef0b014f8b Mon Sep 17 00:00:00 2001
From: cjon256 <3659487+cjon256@users.noreply.github.com>
Date: Fri, 21 Mar 2025 11:06:05 -0400
Subject: [PATCH] Remove MTU 1500 examples
These seem likely to lead people down the wrong path.
---
README.md | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/README.md b/README.md
index 5be01f9..45c0bfd 100644
--- a/README.md
+++ b/README.md
@@ -625,7 +625,7 @@ Config files can opt to use the limited set of `wg` config options, or the more
¶ `PrivateKey = localPrivateKeyAbcAbcAbc=`
¶ `DNS = 1.1.1.1,8.8.8.8`
¶ `Table = 12345`
-¶ `MTU = 1500`
+¶ `MTU = 1420`
¶ `PreUp = /bin/example arg1 arg2 %i`
¶ `PostUp = /bin/example arg1 arg2 %i`
¶ `PreDown = /bin/example arg1 arg2 %i`
@@ -743,14 +743,17 @@ Table = 1234
Optionally defines the maximum transmission unit (MTU, aka packet/frame size) to use when connecting to the peer, not necessary to configure for most setups.
-The MTU is automatically determined from the endpoint addresses or the system default route, which is usually a sane choice.
+The MTU is automatically determined from the endpoint addresses or the system default route, which is usually a sane choice.
+
+You should avoid setting this if at all possible. You almost certainly do not want 1500 here due to the encapsulation overhead.
https://git.zx2c4.com/WireGuard/about/src/tools/man/wg-quick.8
+https://www.dropvps.com/blog/mtu-setting-wireguard/
**Examples**
```ini
-MTU = 1500
+MTU = 1420
```