Using the OpenVPN Client - whats with comp-lzo?

I've been fiddeling around with the OpenVPN client that ships with fvdw on a SPD8020, but what I'm running into is that every (commercially availeble) VPN I have access to that supports OpenVPN, uses the option comp-lzo, and the client claims its an unknown option. Now I've google'd my way around, for OpenVPN the new option is -compress, and comp-lzo is depricated. But the packaged version is 2.3.3 where comp-lzo is still the proper way to tell OpenVPN what's expected from it. Is it by any chance compiled without? Or is there some other reason it won't recognise it?
The way I've gone about it - and it's really straightforward: dump all the required files in a folder, e.g.
Then run it with from that folder with the readily available client:
And all goes well, but for one thing:
If I remove the option, all of them connect beautifully and add their routing options to make it work. Except they spit out this error every other few seconds:
Wich after some google-foo relates to the compression not being set/recognised - and no traffic is able to pass trough the routing either.
Help? :P
The way I've gone about it - and it's really straightforward: dump all the required files in a folder, e.g.
- Code: Select all
/share/1000/fvdw/NameOfTheVPN
Then run it with from that folder with the readily available client:
- Code: Select all
root@nameofmynas:/share/1000/fvdw/NameOfTheVPN # openvpn --config ConfigFileOfThatVPN.ovpn
And all goes well, but for one thing:
- Code: Select all
Options error: Unrecognized option or missing parameter(s) in ConfigFileOfThatVPN.ovpn:13: comp-lzo (2.3.3)
If I remove the option, all of them connect beautifully and add their routing options to make it work. Except they spit out this error every other few seconds:
- Code: Select all
Sat Dec 1 21:28:47 2018 write to TUN/TAP : Invalid argument (code=22)
Wich after some google-foo relates to the compression not being set/recognised - and no traffic is able to pass trough the routing either.
Help? :P