public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: test of lzo option in OpenVPN
Date: Mon, 04 Sep 2023 21:51:48 +0200	[thread overview]
Message-ID: <808a7743-ab88-4293-b88a-030bacc42474@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]

Hi All,

As discussed in the conf call I did a test of the LZO option and the 
result was not what I had hoped for, at least with Network Manager - 
openvpn plugin.

Using my vm testbed, I created a client with LZO option enabled.

I made an opnvpn connection which was successful and worked.

Then I disabled LZO on the server but left the client as it was.

Remade the connection. The connection showed as CONNECTED in the openvpn 
WUI page but in my Arch Linux log for the network manager I got a 
periodic message of

nm-openvpn[1266]: Bad LZO decompression header byte: 42

Additionally trying to use the browser through the tunnel failed with 
the web sites timing out.

So at least with Network Manager Openvpn plugin turning LZO off on the 
server ,when the client has it specified, does not work the way we 
discussed.

I will do a further test with openvpn directly on the command line but 
if one openvpn client doesn't accept LZO being turned off on the server 
if it is enabled in the client this means we can't remove the LZO option 
and default it to disabled on the WUI page.

Regards,

Adolf.

-- 
Sent from my laptop


             reply	other threads:[~2023-09-04 19:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-04 19:51 Adolf Belka [this message]
2023-09-04 20:15 ` Adolf Belka
2023-09-05 16:30   ` Michael Tremer
2023-09-05 19:17     ` Adolf Belka
2023-09-06 13:54       ` Michael Tremer
2023-09-09 11:18         ` Adolf Belka
2023-09-09 11:25           ` Adolf Belka
2023-09-12 13:47           ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=808a7743-ab88-4293-b88a-030bacc42474@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox