jhaprins Hello, I manage several openvpn servers, and the config of these servers has been relatively stable for almost 15 years. Of course I changed things over the years and did a lot of improvement etc, but one thing has always been in the config and that was comp-lzo compression. The config line only says comp-lzo without anything behind it, and when a client connects without this in the config he won't have a working config. Now I received requests from my userbase, telling me that Tunnelblick is warning about this depricated config option. Because of this I would like to get it out of my config, but because everyone has it in the config I'm searching for a way to migrate it out in a way that everything keeps working and the users can remove the config option when they see fit. I noticed that the comp-lzo config option has three options, yes, no and adaptive. I suspect that my current config forces the option to yes, which would explain that a client without the option would have a problem connecting. What is the best way to migrate this configuration? Would it work to change the server to adaptive? Jan Hugo
jhaprins If I push comp-lzo options from the server, will this overwrite the client config? I push a lot of config from the server, but nothing to overwrite the client configuration. Jan Hugo
Pippin Also take a look at --allow-compression mode in manual 2.5: https://build.openvpn.net/man/openvpn-2.5/openvpn.8.html
TinCanTech Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.
jhaprins Pippin wrote Also take a look at --allow-compression mode in manual 2.5: https://build.openvpn.net/man/openvpn-2.5/openvpn.8.html 2.5 options are not available in my setup yet. Jan Hugo Prins
