I subscribe to NordVPN and I'd like to use it. There seems to be a Long-standing bug in the gnome network manager (I found posts dating back to '12) where it does not always parse OpenVPN config files (i.e.: .ovpn extension files). A work-around that seems effective for some people is to dissect the config file manually, and then point network-manager to where the certificates and config files are located. I've tired this with no luck.

Strangely, I can start an OpenVPN session with the standard (un-parsed) config file by simply: "sudo openvpn --config name.of.nord.config.ovpn". After I start a vpn session from the command line, everything connects but DNS does not work. I can ping outside addresses, like 8.8.8.8, but DNS lookups don't work.

So here's what I think the problem is, but I don't have a clue about how to fix it: 1) I think there is some kind of permissions problem trying to start openvpn with the gnome network-manager. I checked the "allow all users to use this connection", but find it odd that I can make all these modifications without every sudo-ing...

2) Regarding command line openvpn, DNS doesn't work. I the problem may reside in dhcp somehow, but I don't know how to go about fixing it. It seems like DHCP "should" accept and update-resolv from the openvpn configuration files.

Thanks for any help!

Reply via email to