Sun, March 29, 2020 · 2 min read

OpenVPN: Bad compression stub decompression header byte: 102 RESOLVED

Bad Compression error

OpenVPN: Bad compression stub decompression header byte: 102 RESOLVED

OpenVPN 2.4 became the default version your connections use. OpenVPN 2.4 adds many security and performance improvements.

Because OpenVPN 2.4 is a major release, there are some setting incompatibilities you may have from your OpenVPN 2.3 configurations. The most common incompatibility is compression settings and the deprecation of the comp-lzo command.

Due to which our data traffic is halted, but connection is not dropped (vpn). Connecting to sophos VPN, we were able to ping to the desired machine in office network but unable to connect to machine via SSH or VNC.

Bad Compression error

Solution:

Step 1: Go to Settings and select Networks.

Step 2: Install the following packages:

sudo apt-get install network-manager-openvpn
sudo apt-get install network-manager-openvpn-gnome
sudo apt-get install network-manager-pptp
sudo apt-get install network-manager-vpnc

Step 3: Click on the + mark under VPN.

Step 4: Click on Import From File and import the .ovpn file from Sophos.

Import VPN

Step 5: After importing successfully, enter your credentials like username and password.

Step 6: Click on Advanced Settings.

Advanced settings

Step 7: Change the LZO Data Compression value from no to Adaptive.

LZO setting

Step 8: Click ok and Apply and connect to your VPN.

Important update: If you don’t get internet access after connecting to VPN, go to network settings > VPN configuration > IPv4 > Routes > “Use this connection only for resources on its network”.

Use this connection only for resources on its network