OpenVPN Issues Anyone After Upgrading to 23.05?

Lavarocker

Re: To 23.05 or not ? that is the question :)

Has anyone tested OpenVPN after upgrading to 23.05? The last official update broke it.

Thanks

michmoor

@Lavarocker ive had no issue.

tedquade

@Lavarocker Zero issues with me.

Ted

4e71

yes @Lavarocker, gateway showed offline, failure to ping, regardless of swapping the monitoring IP with a good working one (i.e. WAN=1.1.1.1=ok and VPN=8.8.8.8=fail for WAN=8.8.8.8=ok and VPN=1.1.1.1=fail)

i noticed Bad compression stub (swap) decompression header byte: 250 entries in the log, for my OpenVPN client, Allow Compression setting was Decompress incoming, do not compress outgoing Asymmetric) with the Compression choice set to Disable Compression, retain compression packet framing [compress].

by changing Compression to Disable Compression [Omit Preference] and restarting, the problem vanished instantly, the Allow Compression setting is unchanged.

i am sure there are other options for what could be selected, but the above change worked for me, throughput and latency on the VPN remain unaffected, so i'm not sufficently motiviated to invest any more time troubleshooting this ¯_(ツ)_/¯

hope that helps in some small way :)

Ahoud

@Lavarocker Also had some problems prior to updating to 23.05, but they appeared to be not pfSense related. Are you having issues connecting to OpenVPN on iOS? It appears to be an issue that came with the 16.5 iOS update, workaround available: https://forums.openvpn.net/viewtopic.php?t=35763

NeVaR

@Lavarocker said in OpenVPN Issues Anyone After Upgrading to 23.05?:

Re: To 23.05 or not ? that is the question :)

Has anyone tested OpenVPN after upgrading to 23.05? The last official update broke it.

Thanks

I have issue with my OpenVPN Server and client. I was able to get OpenVPN Server working again by disable it and then re-enable it. As for my 2 OpenVPN clients, both show are connected but the gateway show offline/packetloss. I have rebuild it again since I can't fine any issue. My suggest is that there likely some new field being added to OpenVPN which causing issue on my end.