Problem with networkmanager 0.9.10.0-2 and openvpn

farseer2012 · 2014-08-06 09:14:20

Before the upgrade of networkmanager to (0.9.10.0-2), everything works fine for me.
I didn't use networkmanager-openvpn, just a openvpn systemd service file.

However, after the update, although the openvpn tunnel is established successfully, it is not used.
I managed to get it working by installing networkmanager-openvpn, first start the systemd service (create 1 tunnel),
then use networkmanager-openvpn to connect to it (another tunnel).

With those two tunnels, vpn connection will last a few minutes, then it will lose effect again.

And If I downgrade networkmanger to 0.9.8.10-3, it works perfect again.

Anyone has any idea what is going on?

tetra · 2014-08-08 07:29:48

I have the same problem. NetworkManager 0.9.10.0-2 is establishing the OpenVPN connection but does not set the routes correctly. The result varies but usually ends in having two default routes with my home router's IP having the lower metric value (ip -4 route) resulting in my tunnel not getting used at all. A restart of networkmanager with 'systemctl restart NetworkManager.service' and reestablishing the connection to the AP and OpenVPN tunnel usually fixes this and the routes are fine. This is of course really annoying.

I am using a wireless connection with IPv4 + IPv6 SLAAC.

farseer2012 · 2014-08-08 11:25:46

tetra wrote:

I have the same problem. NetworkManager 0.9.10.0-2 is establishing the OpenVPN connection but does not set the routes correctly. The result varies but usually ends in having two default routes with my home router's IP having the lower metric value (ip -4 route) resulting in my tunnel not getting used at all. A restart of networkmanager with 'systemctl restart NetworkManager.service' and reestablishing the connection to the AP and OpenVPN tunnel usually fixes this and the routes are fine. This is of course really annoying.
I am using a wireless connection with IPv4 + IPv6 SLAAC.

I have tried to restart the nm service and reconnect vpn several times. I find that whether it is working is really random...
Whatever, I have already downgraded it. the old version just seems better to me...

almightybunghole · 2014-08-10 15:57:08

Glad I'm not the only one. Succesful VPN connection when starting openvpn with a config file, but nothing is routed through the tunnel.
Guess it's time to learn to downgrade.

wilberfan · 2014-08-13 21:42:24

Same problem here.

Instead of downgrading, I restored a pre-upgrade image (I had a LOT of packages update), and then tried putting all the networking apps on hold (network-manager-applet, networkmanager, networkmanager-openvpn, networkmanager-pptp, networkmanager-vpnc).

The upgrade seemed to go okay, by when I rebooted my network-manager-applet was odd: Click on the icon and I see a grayed-out "No network devices available"--but I have a functioning ethernet connection WITH a good VPN connection (verified by going to ipchicken).

If none of those packages updated, why would my applet be wonky like this? (If I hover over it, it displays "Ethernet network connection 'eth0' active".

Here's what upgraded:

I just now noticed that netctl upgraded...could that account for the applet weirdness??

[edit] Tried downgrading netctl, but that didn't change the applet oddities. Is it possible to just re-enter my connection & VPN info into the applet to get that stuff back--or does it read it from somewhere else?

Last edited by wilberfan (2014-08-13 21:48:09)

wilberfan · 2014-08-14 00:22:16

Okay, based on this thread: ( http://comments.gmane.org/gmane.linux.d … ser/480319 ) I downloaded libnm-glib to 0.9.8.10-3.

That resulted in my pre-existing network/VPN settings returning to the applet. However, I had two ethernet networks visible: my standard 'eth0' and a new one that....something.....generated on it's own? 'Network Connection 1' (or something to that effect).

I went ahead and implemented the "Change device name" part of the wiki ( https://wiki.archlinux.org/index.php/Ne … evice_name ), manually deleted the "Network Connection 1" via the applet, and rebooted. Everything seems back to normal at this point (I think).

[edit] Forgot to mention that I have 3 arch installs xfce, gnome, and kde. The lxde system is the one that had this networkmanager upgrade issue...

Last edited by wilberfan (2014-08-14 00:32:03)

Arch Linux

#1 2014-08-06 09:14:20

Problem with networkmanager 0.9.10.0-2 and openvpn

#2 2014-08-08 07:29:48

Re: Problem with networkmanager 0.9.10.0-2 and openvpn

#3 2014-08-08 11:25:46

Re: Problem with networkmanager 0.9.10.0-2 and openvpn

#4 2014-08-10 15:57:08

Re: Problem with networkmanager 0.9.10.0-2 and openvpn

#5 2014-08-13 21:42:24

Re: Problem with networkmanager 0.9.10.0-2 and openvpn

#6 2014-08-14 00:22:16

Re: Problem with networkmanager 0.9.10.0-2 and openvpn

Board footer