Hi there.
Using XG Home with latest SFOS 19.5.3 MR-3-Build652 exporting the openVPN SSL file and using it on iOS 17.0.3 openVPN App V. 3.4.0. In advanced settings of the openvpn is an option of recommended secuity level. If I choose it, I get an error message:
server pushed compression settings that are not allowed and will result in a non-working connection
and the connection fails. I had try to delete this line (comp-lzo no) in the openvpn-file and achieve to connect without an error but there is no connection. I've also tried to put a semicolon before this line in client-config-template.ovpn over ssh. Again no chance to connect properly.
Any point to the solution would be fine.
Thanks
btw: Some more info regarding the comp-lzo option.
Hey fink ,
Thank you for reaching out to the community, following are parameters options you can opt for:client
dev tun
proto [<OPENVPN_PROTOCOL>]
verify-x509-name "[<OPENVPN_SERVER_DN>]"
;route remote_host 255.255.255.255 net_gateway
resolv-retry infinite
nobind
persist-key
persist-tun
ca [<OPENVPN_CA_FILE>]
cert [<OPENVPN_CLIENT_CERT>]
key [<OPENVPN_CLIENT_KEY>]
auth-user-pass
cipher [<OPENVPN_CIPHER>]
auth [<OPENVPN_AUTH>]
comp-lzo [<OPENVPN_COMPRESSION>]
;can_save [<OPENVPN_SEVECREDENTIAL>]
;otp [<OPENVPN_TWOFATOKEN>]
;run_logon_script [<OPENVPN_ADLOGON>]
;auto_connect [<OPENVPN_AUTOCONNECT>]
;route-delay 4
verb 3
reneg-sec 0
XG - RR Temporary Fix OpenVPN (3.4.0)
Thanks & Regards,
_______________________________________________________________
Vivek Jagad | Team Lead, Technical Support, Global Customer Experience
Log a Support Case | Sophos Service Guide
Best Practices – Support Case | Security Advisories
Compare Sophos next-gen Firewall | Fortune Favors the prepared
Sophos Community | Product Documentation | Sophos Techvids | SMS
If a post solves your question please use the 'Verify Answer' button.
I didn' change comp-lzo to yes because this option is no longer supported. There are known vulnerabilities on compression with OpenVPN since 2018 according to this OpenVPN-Site. So better not to use.
Use only following parameter and delete all the rest. it works for me:
client dev tun proto udp explicit-exit-notify verify-x509-name "xxxxxxxxx" route remote_host 255.255.255.255 net_gateway resolv-retry infinite nobind persist-key persist-tun
We are looking into this actively, currently “comp-lzo” is the attribute causing some issues in making it work with the “preferred” security level.
With the latest release of Android (3.4.0), there seems some issue with “comp-lzo no” and legacy mode too, which is highlighted in the OpenVPN community at https://forums.openvpn.net/viewtopic.php?t=43571.
The current workaround to make Android-based OpenVPN connect clients to work is by enabling “compression” on SFOS global settings and reimport of configuration.
Openvpn Connect version |
Security Level |
Compression on SFOS |
Tunnel status |
Data plane |
Android Phone |
Legacy |
ON |
Up |
Up |
OFF |
Up |
Down Error: 2024-01-30 10:18:08Z [7565] user1/xx: 35854 Bad compression stub decompression header byte:251 |
||
iOS Phone |
Legacy |
ON/OFF |
Up |
Up |
MacOS |
Legacy |
ON/OFF |
Up |
Up |
Windows |
Legacy |
ON/OFF |
Up |
Up |
Windows |
- |
ON/OFF |
Up |
Up |