GNOME Bugzilla – Bug 759949
[regression 1.0.10] Connection to VPN no longer sets route
Last modified: 2016-01-06 09:42:34 UTC
Since the upgrade of NetworkManager (and network-manager-applet) to 1.0.10, whenever I connect to the VPN (based on openvpn), the routes provided through the tunnel are not configured in my system. I reverted NetworkManager back to 1.0.8 and the setup works correct (network-manager-applet was left at 1.0.10; the various vpn plugins are also at 1.0.8 as they have not seen releases since)
Can you attach a debug-logfile when that happens? Maybe a duplicate of bug 759892 ?
Created attachment 318134 [details] Debug output I have experienced the same issue, attaching a file with the debug output of my attempt to connect to my VPN. I've sanitized the log a bit to remove sensitive information, like the VPN endpoint IP, my WLAN SSID and BSSID and VPN connection name, I left in all local IP addresses. The specific error lines to look for are: <warn> platform-linux: do-add-ip4-route: failure adding ip4-route '19: 192.168.0.0/16 50': Unspecific failure (1) <warn> platform-linux: do-add-ip4-route: failure adding ip4-route '19: 192.168.240.1/32 50': Unspecific failure (1) My workaround is the same, downgrade to 1.0.8
This also affects static routes added to the connection, not just those pushed by the VPN server, but the connection fails if you've configured static routes
According to the logfile from comment 2, this is a dupe of bug 759892 and fixed in the meantime. Thanks for reporting *** This bug has been marked as a duplicate of bug 759892 ***