I'm running 18.2 on a laptop. I used PIA for years with no issues, but decided to switch over to NordVPN. I check all of my OpenVPN installs, and made sure everything was up to date.

But, when I go through and add a connection manually via the Network Manager, it tells me that it is connected, but I can't actively connect to anything online. I can't ping anything online. I've tried this with both UDP and TCP. I also attempted with ProtonVPN (the free version, just as a test to see if it was an issue with Nord servers being down), and had the exact same result.

If I connect to Nord via terminal it works, but usually drops connection within the hour if I'm running KTorrent (with no activity). It will stay connected for simple web browsing. The issue is clearly on my end, but I have no idea what it is.

I would prefer to connect via Network Manager for ease of use, and an icon telling me when I am/am not connected. What's going on with my system, and does anyone have any clue how to fix it?

I'm very new to linux, but have used VPNs for years, so please consider my input as conversation vs advice. This sounds like a DNS or firewall issue to help sort that (and info the Linux experienced helpers hereabouts prefer to see) please run the following commands in terminal and paste the results into code boxes in reply.

I have discovered that if I connect to Nord directly through sudo config in terminal, not through their app or Network Manager, that there is no dropping issues. Lots of reply warnings (I haven't muted them so I can monitor the connection. And I'm not sure how to mute them to be honest), but a steady connection.

I'm comparing your results with mine on those commands but don't have the knowledge to determine what may be missing, for example I see on my ifconfig results there is destination info on tun0 (the ovpn virtual adapter) also see a huge difference in frame results (RX line of wlp2s0) yours is 2255436 whereas mine shows 0 on all adapters listed. Not even sure if either or both of those factors are relevent... but do believe the info will help the troubleshooters in forum.

ufw isn't a factor ("inactive" which to me says all going out will be allowed and unsolicited incoming connections will be dropped).

When you look at NM connection information what do you see for DNS servers under TUN and WIfi? (IPv4&v6)

is power saving turned off for your wifi adapter?

Please paste in some of the terminal "reply warnings" you are seeing when connected that way, perhaps something in config will be evident from that.

There is check connection and reconnect VPN in NM settings we can try in effort to get NM managing this connection for you as well. Open NM "edit connections", select the connection name of VPN you imported config for, hit the gear box (edit), VPN tab, open advanced (lower right), you want to enable (checkmarked) the "Specify ping interval:" and set that to 10

also enable the very bottom option "Specify exit or restart ping:" select "ping-restart" from the drop down and set 60 in the timer box.

click "OK"

before "Save" (since we have VPN open) what do you see under IPv4 and v6 tabs "method"? is set to Automatic (or Auto addresses only and manual info typed in for DNS)?

make sure to click "Save" to exit out of VPN edit. The try to connect VPN via NM and lets see if it's any better~

Moem kōan 42: Should tool manufacturers be required to fix their products so that you cannot use their saws to cut the tree branch that you're sitting on?

(The answer to the ultimate question of life, the universe and everything is... 42!!;)

It's not a major issue, it's a good way to monitor the connection in Terminal. I switched to a tcp from a ucp connection, and it has eliminated the bad packet issue. But, as going through Terminal to connect works, I'm going to be sticking with that for now. It's not an inconvenience for me, it just takes a few seconds more. But direct connecting that way has eliminated the connection drops as well, which was the main issue via the NordVPN app.

I looked around at NordVPN site and do see one thing you may want to adjust, according to their faqs Nord does not support IPv6 (yet), note says due in 2018 and manual methods (not using their client) say to disable IPv6 altogether (and I concur, for privacy/anti-leak measures, especially if they don't support it)

If you disable IPv6 using NM I recommend do it for all adapters (wifi and tun) by entering NM edit connections, select connection, hit the gear box (edit), IPv6 setting tab, Method: Ignore. and see if this helps when using NM to connect VPN. It would explain the timeouts I think we're seeing.

Moem kōan 42: Should tool manufacturers be required to fix their products so that you cannot use their saws to cut the tree branch that you're sitting on?

(The answer to the ultimate question of life, the universe and everything is... 42!!;)

more info on disable IPv6, I have done four methods locally, via NM, in sysctl.conf, in etc/hosts and in Grub menu. NordVPN's guide to disable is what I have done (sysctl method) and can be found here (under debian based)https://nanorep.nordvpn.com/Connectivit ... -Linux.htm