ecabfe6e49b9dd5897ab78ea4dc7fc3d51446dcd
howto/wireguard.md
| ... | ... | @@ -48,7 +48,7 @@ $ ip addr add 172.xx.xx.xx/32 peer 172.xx.xx.xx/32 dev <interface_name> |
| 48 | 48 | $ ip link set <interface_name> up |
| 49 | 49 | ``` |
| 50 | 50 | |
| 51 | -Nurtic-Vibe has another [script](https://git.dn42.us/Nurtic-Vibe/grmml-helper/src/master/create_wg.sh) to interactively automate the peering process. |
|
| 51 | +<!-- Nurtic-Vibe has another [script](https://git.dn42.us/Nurtic-Vibe/grmml-helper/src/master/create_wg.sh) to interactively automate the peering process. --> |
|
| 52 | 52 | |
| 53 | 53 | Maybe you should check the MTU to your peer with e.g. `ping -s 1472 <end_point_hostname_or_ip>`. If your output looks like `From gateway.local (192.168.0.1) icmp_seq=1 Frag needed and DF set (mtu = 1440)` substract `80` from the MTU and set it via `ip link set dev <interface_name> mtu <calculated_mtu>` |
| 54 | 54 |