SSLVPN and OpenVPN2.5 compatibility issue

Hi Damien,

I am not aware of any discussions to add this to the UTM, I would recommend you to raise it as a Feature Request on Sophos Ideas.

Thanks,

Looks like someone has sugguested something similar: https://ideas.sophos.com/forums/17359-sg-utm/suggestions/34142695-update-ssl-vpn-to-newest-openvpn-version so I voted for this.

Do not do the following without explicit approval in an email from Sophos Support!

As root at the command line:

cp /var/sec/chroot-openvpn/etc/openvpn/openvpn.conf /var/sec/chroot-openvpn/etc/openvpn/openvpn.conf.bak
cp /var/sec/chroot-openvpn/etc/openvpn/openvpn.conf-default /var/sec/chroot-openvpn/etc/openvpn/openvpn.conf-default.bak

edit /var/sec/chroot-openvpn/etc/openvpn/openvpn.conf

Delete the line containing comp-lzo and write.

edit /var/sec/chroot-openvpn/etc/openvpn/openvpn.conf-default

Delete the line containing comp-lzo [<DISABLE_COMP>] and write.

Reboot.

No changing of the client configs is required.

You should be OK going forward unless Sophos changes openvpn.conf-default without removing comp-lzo.

Cheers - Bob

Thanks for this. I shall note this down and then implement it when Tunnelblick no longer supports the old OpenVPN Sophos is using.

We are getting this warning. Anyone knows if we have to do this or if the change is reflected in any updates since?

No, it still has the warning on the latest firmware (9.602-3, well, almost latest)

Thanks.

Has anyone tried BAlfson's method?

Thanks.

Has anyone tried BAlfson's method?