Hi, On Thu, Feb 09, 2023 at 10:36:38PM +0100, Stella Ashburne wrote: > > Otherwise, talk to the VPN > > vendor you are paying for, and ask them why it's not working with them > > Fair enough. I shall ask my VPN vendor/provider why it doesn't implement > opvn-dco.
That's actually the wrong question - "implement DCO" is our job, but
they should not use incompatible options, unless there is a strong
reason.
What they need to do is to enable "compression migrate" on the server
side, and stop unconditionally pushing "comp-lzo no" to clients that
are not signalling that they can handle this.
"compression migrate" is a new server-side option which will figure out
whether compression is enabled on the client (by means of option handshaking)
and then send either "compress stub-v2", which will turn *off* compression,
including compression framing, or fall back to "comp-lzo no" for clients
that are so old that they can not handle stub-v2.
With this, a DCO capable client will receive stub-v2 (= off), and really
really old clients - OpenVPN 2.3 and older - will use "comp-lzo no". The
server will automatically adjust its internal settings to handle whatever
the client needs.
gert
--
"If was one thing all people took for granted, was conviction that if you
feed honest figures into a computer, honest figures come out. Never doubted
it myself till I met a computer with a sense of humor."
Robert A. Heinlein, The Moon is a Harsh Mistress
Gert Doering - Munich, Germany g...@greenie.muc.de
signature.asc
Description: PGP signature
_______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
