Difference between revisions of "CentOS 8.x openvpn client troubleshooting"
(Created page with "<yambe:breadcrumb self="openvpn client troubleshooting">CentOS 8.x openvpn client|Openvpn client</yambe:breadcrumb> =CentOS 8.x openvpn client troubleshooting= ==Bad compress...") |
m |
||
| Line 1: | Line 1: | ||
[[Main Page|Home]] > [[CentOS]] > [[CentOS 8.x]] > [[CentOS 8.x networking tools]] > [[CentOS 8.x openvpn client]] > [[CentOS 8.x openvpn client troubleshooting]] | |||
==Bad compression stub decompression header byte: 102 error== | ==Bad compression stub decompression header byte: 102 error== | ||
| Line 23: | Line 22: | ||
[[Main Page|Home]] > [[CentOS]] > [[CentOS 8.x]] > [[CentOS 8.x networking tools]] > [[CentOS 8.x openvpn client]] > [[CentOS 8.x openvpn client troubleshooting]] | |||
Latest revision as of 17:11, 15 May 2022
Home > CentOS > CentOS 8.x > CentOS 8.x networking tools > CentOS 8.x openvpn client > CentOS 8.x openvpn client troubleshooting
Bad compression stub decompression header byte: 102 error
It is possible that while connecting to a VPN server (Could be firewall eg sophos or a openvpn server), that client receives error such as:
Bad compression stub decompression header byte: 102
These are often seen only while initiating a new connection to particular machines. This can be due to disabling of lzo-compression in configuration. To fix this edit the openvpn configuration file and update 'comp-lzo' from no to adaptive as:
comp-lzo adaptive
After this during connection you should not see the same error.
This is valid from openvpn 2.4 onwards. So you can also validate openvpn version using 'rpm -qa openvpn' before making above change.
Refer:
Home > CentOS > CentOS 8.x > CentOS 8.x networking tools > CentOS 8.x openvpn client > CentOS 8.x openvpn client troubleshooting
