You have a complex situation, due to the superposition of two distinct issues: OpenVPN and NetworkManager. It is not clear to me where exactly the problem lies, so I suggest you activate OpenVPN directly, without passing thru Network-Manager:
sudo openvpn --config /path/to/your/file.conf
If this this works, then we can be sure that the fault lies squarely with Network-Manager, while if it does not, error messages will be provided (either in /etc/openvpn or in /var/log/openvpn.log, depending on how you set this up).
I never pass thru Network-manager because I have had problems with it in the past. Since you are a fellow Archer, one might think that we may have experienced a similar problem, but I think this unlikely. I have never managed to pinpoint it, but I found that a reduction of the mtu helps: say, use mssfix or even mtu-test in the configuration file. However, these options only make sense for OpenVPN over UDP (my case), but if I read your comments right, you are using OpenVPN over TCP, so no dice there.
At any rate, I have resorted to connecting to OpenVPN directly, as per the command above. Hope this helps, cheers.
Is your VPN host booting you off because they have a policy against sending specific types of traffic? – Dave Lucre – 2017-02-24T00:09:47.197
I would say no. I have been using them without problems. They even allow P2P traffic. – Joe – 2017-02-24T00:14:14.773
Do you see an interruption of traffic or are ping replies your only indication? The destination you sent pings to had a very high latency. Internet facing devices often lower the priority of ICMP echo reply traffic. – TDurden – 2017-02-27T23:18:06.547
Hey @TDurden I have recorded a new video using mtr tool. There is a interruption of traffic. https://youtu.be/-SI7K92kiv8
– Joe – 2017-03-03T00:11:02.183Is it possible your ISP or work administrator (depending upon whether you were at home or at work when you recorded these videos) is preventing you from using a VPN? If so, the simplest is to change the OpenVPN server to listen on port 443TCP because most nasty firewalls must allow connection to safe sites, and these are automatically encrypted. Also, you should try connecting outside the network manager. Can you try these two things? – MariusMatutiae – 2017-03-03T07:36:26.170
I think the Internet freezes because it's very busy doing DNS requests that have no results. On Windows I would advice to untick in the VPN properties the option of "Use default gateway on remote network", but I don't know the equivalent operation on your VPN. I would also advice using "route add" to add a default route toward your normal ISP, so only requests mentioning the VPN are directed to it. – harrymc – 2017-03-03T17:42:46.127
Thank you @MariusMatutiae I am connected using the port 443. I will try to connect directly from OpenVPN and add some logs. I will get back to you. +harrymc I am using DNScrypt so I am not using their DNS server, but if you see I am pinging the IP address directly anyway. Adding my ISP as a route wouldn't defeat a VPN propose? – Joe – 2017-03-04T10:26:53.357
Adding such a route is sometimes called split tunneling (useful link). I don't know DNScrypt, but it seems to only be a protocol, not a server. I can't think of anything else that would be freezing the connection than DNS. I would suggest simplifying everything to the limit, such as not using DNScrypt, just in case something drives mad the VPN's DNS server (if there is one).
– harrymc – 2017-03-04T20:01:26.780@MariusMatutiae so, using openvpn directly seems to work perfectly. I am now sure there is a networkmanager problem. I have posted this into archlinux forums since it looks like it can be a bug link Is there anything I can check to solve this? +harrymc Thank you for the link, it was very interesting. I will have a look.
– Joe – 2017-03-10T03:05:46.030@MariusMatutiae would you like to type your answer so I can give you the bounty offered? – Joe – 2017-03-11T01:46:53.247