Version 3.4 keeps disconnecting and reconnecting every 10-15 seconds

grokker

I've tried it on three diffferent Windows computers and one MacOS one.

Maybe the problem is in a conflict with the server. I'm connecting to an Untangle 16.6.2 NG Firewall (now Arista NG Firewall).

OpenVPN Connect v. 3.3.7 on Windows works fine (I can't find where to download the previous version for MacOS).

Please ask for any log files that may help. I don't even know where they are.

4tonaf

for us its every 30 - 31 seconds.
Only windows, only as far as we can see the latest version, multiple sites, multiple users

JosephS

Hi,
Can you check the client logs and share the latest EVENT before the VPN disconnects?
It may provide some insight as to what may be causing the constant disconnect.

alb_73

Hi,

Fixed this by adding the following custom options to the client configuration:

allow-compression asym
compress lz4

Then exclude the default compress option in the client configuration too.

Redeploy the openvpn config file to clients.

More details can be found here:

https://community.openvpn.net/openvpn/wiki/Compression

Hope this helps...

grokker

Here are the lines showing the disconnection (sensible information replaced with xxxxxx)

⏎[Aug 11, 2023, 05:02:35] Connected via TUN_WIN
⏎[Aug 11, 2023, 05:02:35] LZO-ASYM init swap=0 asym=1
⏎[Aug 11, 2023, 05:02:35] Comp-stub init swap=0
⏎[Aug 11, 2023, 05:02:35] EVENT: CONNECTED xxxxxxxxxxxxxxxxxxxxx via /UDP on TUN_WIN/xxxxxxxxxx/ gw=[xxxxxxxxx/] mtu=(default)
⏎[Aug 11, 2023, 05:02:35] EVENT: COMPRESSION_ENABLED Asymmetric compression enabled.  Server may send compressed data.  This may be a potential security issue.
⏎[Aug 11, 2023, 05:03:04] Session invalidated: KEEPALIVE_TIMEOUT
⏎[Aug 11, 2023, 05:03:04] Client terminated, restarting in 2000 ms...
⏎[Aug 11, 2023, 05:03:04] SetupClient: signaling tun destroy event
⏎[Aug 11, 2023, 05:03:06] EVENT: RECONNECTING
⏎[Aug 11, 2023, 05:03:06] EVENT: RESOLVE
⏎[Aug 11, 2023, 05:03:06] Contacting xxxxxxxxxxx via UDP
⏎[Aug 11, 2023, 05:03:06] EVENT: WAIT
⏎[Aug 11, 2023, 05:03:06] WinCommandAgent: transmitting bypass route to xxxxxxxxxxxx

After that, it will connect again, and round and round it goes.

Oh, and you're right: it's mnore like every 30 seconds.

grokker

alb_73 wrote Hi,

Fixed this by adding the following custom options to the client configuration:

allow-compression asym
compress lz4

Then exclude the default compress option in the client configuration too.

Redeploy the openvpn config file to clients.

More details can be found here:

https://community.openvpn.net/openvpn/wiki/Compression

Hope this helps...

Thanks for the suggestion.

I hope the developers can find a better solution. I don't want to think of manually edit 50+ employees setup... I'd rather stay in 3.3.7, which works fine.

grokker

OpenVPN support tells me we have to deal with Arista (Untangle).

TRG

Thank you man, this fixed my problem on iPhone.

alb_73 wrote Hi,

Fixed this by adding the following custom options to the client configuration:

allow-compression asym
compress lz4

Then exclude the default compress option in the client configuration too.

Redeploy the openvpn config file to clients.

More details can be found here:

https://community.openvpn.net/openvpn/wiki/Compression

Hope this helps...

rodolfoberain

alb_73 wrote Hi,

Fixed this by adding the following custom options to the client configuration:

allow-compression asym
compress lz4

Then exclude the default compress option in the client configuration too.

Redeploy the openvpn config file to clients.

More details can be found here:

https://community.openvpn.net/openvpn/wiki/Compression

Hope this helps...

this fixed the issue with client 3.4 on both windows and mac.

openvpn_inc

Hello,

Just wanted to leave a message of caution. The solutions suggested here include re-enabling compression. At least to allow data from the server side to arrive encrypted. While in some cases you may not have control over the server side configuration, and this may help to at least get connected again, I want to point out the danger of using compression at all. The VORACLE vulnerability exists when compression and encryption are used at the same time. Therefore efforts are made to phase compression out of OpenVPN altogether. Just thought you should know so that, for those that are able to, they can look into making sure the server side does not do compression and cause this issue anymore.

Kind regards,
Johan