-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Monday, 5 April 2021 18:34, Gert Doering <g...@greenie.muc.de> wrote: > Hi, > > On Mon, Apr 05, 2021 at 02:51:23PM +0000, tincantech via Openvpn-users wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA256 > > Ref: https://forums.openvpn.net/viewtopic.php?f=4&t=32100 > > Regarding compression, it is unclear what the best options are. > > The server config above uses > > {{{ > > allow-compression no > > compress > > comp-lzo no > > push "comp-lzo no" > > }}} > > If you have no compelling use-case for using compression, then just > leave out anything that starts with "compression" or "comp-lzo" from > your config. > > "comp-lzo no" is - due to historic mishaps - not the same as > "no compression" > > > However the manual states: > > --compress alg > > Note: the `stub` (or empty) option is NOT compatible with the older option > > --comp-lzo no. > > My guess would be that the server config above is indeed an error because > > it uses --compress > > and pushes --comp-lzo no. > > It also sets "comp-lzo no", which overrides the previous "compress" > statement anyway. > Ah right, thanks. That clears up the logic a little.. > > The server then randomly aborts with: > > vpn-ext kernel: [15774] pid 46022 (openvpn), jid 0, uid 65534: exited on > > signal 11 > > This is not good, and needs debugging. OpenVPN should never SIGSEGV. > > This is likely unrelated to compression setting, though. One would > need a verb 4 log to see what leads to this. > I'll see what I can do.. > > Assuming that the client is using some combination of compression options > > which cannot be changed, > > or more likely that it is too much trouble to change all the clients, is > > there a recommended setting to disable > > all compression from the server only ? > > compress migrate > > this will push whatever the client understands to disable compression > (or nothing at all if the client has no compression in its config in > the first place). > > Works with 2.2 and up clients (after the recent fixup patch). Will that be included in version 2.5.2 ? Thanks -----BEGIN PGP SIGNATURE----- Version: ProtonMail wsBzBAEBCAAGBQJga1d5ACEJEE+XnPZrkLidFiEECbw9RGejjXJ5xVVVT5ec 9muQuJ30ygf/XtOpB64STbC6USdSRbNGiGf61IafsQu//PZk1QAgm2+Oczuv RQDXP05yUwE0ZwGggVPy+J8Re6SD+ylkaaAxXCQmI0ZBGFdpJsdUDGHEKAiN JjgAMhL3olhUe6RkJ3mU3+ue/NVS+FO9kltUQmchvWKP8bCjZm4evDGRlNoa y/yeWySPi7dp5JB0nboGOGHvxvnM1RArLNv7sUarAwO/bIK+Z6OpC6a9iMZG MfYTq2r7cdu7rVP+72N/8P1rsN/b83vkOYOTz+iAeZ/4Sl7Gc4jsFdZ5UUVy 0FGse7q887Wer5KL7CH5qTjXwmFXX4VggTmBrMehKfFswUqz5piwAw== =IcEe -----END PGP SIGNATURE-----
publickey - tincantech@protonmail.com - 0x09BC3D44.asc
Description: application/pgp-keys
publickey - tincantech@protonmail.com - 0x09BC3D44.asc.sig
Description: PGP signature
_______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
