Your message dated Mon, 27 Mar 2017 11:33:29 +0200
with message-id <[email protected]>
and subject line Nothing to see here
has caused the Debian Bug report #858560,
regarding openVPN 2.4.0 IPv4 "comp-lzo" no issue
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
858560: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858560
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: openvpn
Version: 2.4.0-4
This issue has also been reported as a openVPN @ openVPN:
https://community.openvpn.net/openvpn/ticket/861
When I connect to a 2.3.12 FreeBSD via 2.4.* Linux Client with this
configuration:
client
dev tun
tun-ipv6 # In DebianStretch this option was disabled. Because of Note: option
tun-ipv6 is ignored because modern operating systems do not need special IPv6
tun handling anymore
nobind
inactive 86400
comp-lzo no
<connection>
remote server port udp
</connection>
cipher AES-256-CBC
auth sha256
pkcs12 /<path>/file.p12
verify-x509-name server name
user nobody
persist-key
persist-tun
I see this warning if I connect to a IPv4 host:
Thu Mar 23 13:35:38 2017 UID set to nobody
Thu Mar 23 13:35:38 2017 Initialization Sequence Completed
Thu Mar 23 13:35:50 2017 Bad compression stub decompression header byte: 102
Thu Mar 23 13:35:50 2017 Bad compression stub decompression header byte: 102
Thu Mar 23 13:35:50 2017 Bad compression stub decompression header byte: 102
Thu Mar 23 13:35:51 2017 Bad compression stub decompression header byte: 102
Thu Mar 23 13:35:51 2017 Bad compression stub decompression header byte: 102
Thu Mar 23 13:35:53 2017 Bad compression stub decompression header byte: 102
Thu Mar 23 13:35:56 2017 Bad compression stub decompression header byte: 102
Thu Mar 23 13:36:48 2017 Bad compression stub decompression header byte: 102
Thu Mar 23 13:36:48 2017 Bad compression stub decompression header byte: 102
Thu Mar 23 13:36:48 2017 Bad compression stub decompression header byte: 102
Thu Mar 23 13:36:49 2017 Bad compression stub decompression header byte: 102
Thu Mar 23 13:36:49 2017 Bad compression stub decompression header byte: 102
Thu Mar 23 13:36:51 2017 Bad compression stub decompression header byte: 102
Thu Mar 23 13:37:27 2017 Bad compression stub decompression header byte: 102
Thu Mar 23 13:37:27 2017 Bad compression stub decompression header byte: 102
Thu Mar 23 13:37:28 2017 Bad compression stub decompression header byte: 102
Thu Mar 23 13:37:28 2017 Bad compression stub decompression header byte: 102
Thu Mar 23 13:37:29 2017 Bad compression stub decompression header byte: 102
Thu Mar 23 13:37:30 2017 Bad compression stub decompression header byte: 102
If I connect via IPv6 I don't have any issue.
If I change option comp-lzo
For: comp-lzo no
To: comp-lzo yes
Everything is fine too, even tough the server has been configured, with:
comp-lzo no
This has been tested on openvpn 2.4.0 as well as openvpn 2.4.1
Have tested in on openSUSE toop version 2.4.0 and 2.4.1 with the same issue.
There for it looks like a openVPN issue.
--- End Message ---
--- Begin Message ---
Closing per submitter request.
--
Alberto Gonzalez Iniesta | Formación, consultoría y soporte técnico
mailto/sip: [email protected] | en GNU/Linux y software libre
Encrypted mail preferred | http://inittab.com
Key fingerprint = 5347 CBD8 3E30 A9EB 4D7D 4BF2 009B 3375 6B9A AA55
--- End Message ---
