a6c032aac465b50a51a965a80a17455bbcec8852
howto/wireguard.md
... | ... | @@ -46,8 +46,7 @@ $ ip addr add 172.xx.xx.xx/32 peer 172.xx.xx.xx/32 dev <interface_name> |
46 | 46 | $ ip link set <interface_name> up |
47 | 47 | ``` |
48 | 48 | |
49 | -Mic92 uses this [script](https://github.com/Mic92/bird-dn42/tree/master/wireguard) to automate this. |
|
50 | - |
|
49 | +Mic92 uses this [script](https://github.com/Mic92/bird-dn42/tree/master/wireguard) to automate this. |
|
51 | 50 | 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 | 51 | |
53 | 52 | 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>` |