I set client MTU to 99999 and problems ensue

[vpnnovice1680]

I was playing with tun-mtu and mssfix on the client in order to improve my connection speed and then I had the genius idea to increase tun-mtu to 99999. Consequently, the client would drop out immediately after establishing connection. Is there any way to fix this if I don't have direct access to the client?

Client Config

Code: Select all

remote address.to.my.server
client
port 4321
proto tcp4
dev tun
tls-client
tls-auth "path/to/ta.key" 1

remote-cert-tls server
tun-mtu 99999
tun-mtu-extra 32
mssfix 99949

ca "path/to/ca.crt"
cert "path/to/client.crt"
key "path/to/client.key"
auth-nocache
reneg-sec 0
keepalive 10 120
cipher AES-256-GCM
#comp-lzo
user nobody
persist-key
persist-tun
verb 3
mute 20

Server Config

Code: Select all

dev-node "ServerVPN2" 
tls-server
port 2345
proto tcp4
dev tun
tls-auth "path\\to\\ta.key" 0

tun-mtu 99999
tun-mtu-extra 32
mssfix 99949

ca "path\\to\\ca.crt"
cert path\\to\\ServerVPN.crt"
key "path\\to\\ServerVPN.key"
dh "path\\to\\dh4096.pem"
server 10.10.8.0 255.255.255.0
keepalive 10 120
cipher AES-256-GCM
ncp-disable
persist-key
persist-tun
client-config-dir "path\\to\\config"
verb 4
route-method exe
route 192.168.2.0 255.255.255.0

The consequence:

Code: Select all

Wed Apr 06 16:00:09 2022 us=464092 Client/171.254.159.102:51676 Connection reset, restarting [0]
Wed Apr 06 16:00:09 2022 us=464092 Client/171.254.159.102:51676 SIGUSR1[soft,connection-reset] received, client-instance restarting
Wed Apr 06 16:00:09 2022 us=464092 TCP/UDP: Closing socket
Wed Apr 06 16:01:39 2022 us=125168 MANAGEMENT: CMD 'signal SIGHUP'
Wed Apr 06 16:01:39 2022 us=125168 TCP/UDP: Closing socket

[TinCanTech]

Is there any way to fix this if I don't have direct access to the client?

No.