[Solved] increase TLS handshake timeout during login?

bastler

Hi there!

I run an openVPN server installation at a local site which has been working fine in general, but now I have a problem:

I am using very large keys and strong ciphers. When connecting from a powerful device (laptop) through a reliable infrastructure (wired network) this works flawlessly.

If I try however to connect from a less powerful device (smartphone), or using a very slow connection (GPRS in area with low signal coverage), then the initialization process regularly fails during TLS handshake, because a timeout occurs before my client is done calculating the respective session keys.

Is there a CLI/config file argument I can use to lengthen this timeout and allow successful connection, even if the client is very slow to respond during login?

Thanks!

maikcat

hi there,

you can try to set

tls-timeout

directive and see if that helps

Michael.

valent

bastler wroteHi there!

I run an openVPN server installation at a local site which has been working fine in general, but now I have a problem:

I am using very large keys and strong ciphers. When connecting from a powerful device (laptop) through a reliable infrastructure (wired network) this works flawlessly.

If I try however to connect from a less powerful device (smartphone), or using a very slow connection (GPRS in area with low signal coverage), then the initialization process regularly fails during TLS handshake, because a timeout occurs before my client is done calculating the respective session keys.

Thanks!

I'm having similar issue. I created 2048 bit keys, and clients are embedded arm machines (wifi routers running OpenWrt).

These routers start vpn without issue over wifi if they are in same room as AP. But if they are in different room, and there is other AP close by that could cause some interference, I get TLS timeout...

Does this happen to others when wifi signal is not perfect 10/10? Any other suggestions? Should I migrate vpn server to use tcp instead udp?