Ubuntu 16.04.1 -- ping: unknown host google.com

[dx486 0]

Hello!

 

My system is a fresh Ubuntu 16.04.1 64 bit.

 

network-manager-openvpn and network-manager-openvpn-gnome packages are installed.

 

I created my .ovpn file using Config Generator. I added this file as a VPN connection using NetworkManager.

 

It can connect to VPN server successfully, however I cannot connect to anywhere.

 

$ ping google.com
ping: unknown host google.com

$ sudo openvpn --config AirVPN_Netherlands_UDP-443.ovpn
Thu Oct  6 19:31:46 2016 OpenVPN 2.3.10 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Feb  2 2016
...
...
Thu Oct  6 19:31:54 2016 Initialization Sequence Completed

$ cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback

$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.1.1

 

 

[dx486 0]

This is an update/correction to my first post, so I decided to make a reply instead of editing it.

 

I realized that I can connect to web pages if I connect via openvpn command in Terminal. However when I use "network manager" to connect, I cannot connect anywhere, although the VPN connection is established without any problem.

 

I made the configuration as it is described here:

 

1. Choose your OS: Linux

2. Choose server: Netherlands

3. Connection modes: "Direct, protocol UDP, port 443 ^(*) " is checked.

4. "Advanced mode" is checked.

5. "Separate keys/certs from .ovpn" file is checked.

6. Configuration file is imported to NetworkManager & connected via NetworkManager.

 

What is wrong here?

[xinu 0]

I hit the same issue. It seems that the config generator specifies: "comp-lzo no"

 

So I needed to manually enable "Use LZO data compression" in the VPN connection's Advanced settings before my connection worked.

[Staff 9972]

Hello,

 

"comp-lzo no" is correct. The reported issue appears as a mis-interpretation of network-manager-openvpn. "comp-lzo no" for OpenVPN does not mean that LZO must be forcefully disabled. If this directive is omitted, you will not be able to accept properly a comp-lzo yes or no push.

 

On the other hand we strongly recommend to not use network-manager-openvpn and we will not tweak a correct configuration just to fix a bad behavior.

 

Kind regards