Important change to custom MTU handling (mainly to fix issue #1357)

- When NOT providing a custom MTU, 1420 is used for both clients and server.
    Using such value for clients can break WireGuard connections on some networks,
    so iOS and Android clients have logic in place to select a proper MTU value
    when not specified. Now "pivpnMTU" with only be used to set the MTU value for
    the PiVPN installation but not for profile creation.
This commit is contained in:
Orazio 2021-09-15 17:52:17 +02:00
parent 027f257931
commit 50798ccd42

View file

@ -103,10 +103,6 @@ echo "[Interface]
PrivateKey = $(cat "keys/${CLIENT_NAME}_priv")
Address = ${NET_REDUCED}.${COUNT}/${subnetClass}" > "configs/${CLIENT_NAME}.conf"
if [ -n "${pivpnMTU}" ]; then
echo "MTU = ${pivpnMTU}" >> "configs/${CLIENT_NAME}.conf"
fi
echo -n "DNS = ${pivpnDNS1}" >> "configs/${CLIENT_NAME}.conf"
if [ -n "${pivpnDNS2}" ]; then
echo ", ${pivpnDNS2}" >> "configs/${CLIENT_NAME}.conf"