GNOME Bugzilla – Bug 704595
OpenVPN plugin does not want to start a VPN connection if there is currently no default gateway
Last modified: 2020-11-12 14:34:03 UTC
I have a wired ethernet configuration with some static routes to specific hosts, including a VPN gateway: IPv4 Settings Method: Manual Address: 192.168.0.33 Netmask: 255.255.255.0 Gateway: 0.0.0.0 DNS Servers: 8.8.8.8,8.8.4.4 [ ] Require IPv4 addressing for this connection to complete Routes... Address: 46.246.x.y Netmask: 255.255.255.255 Gateway: 192.168.0.1 I use this configuration when I want to be sure that, even if the VPN connection fails, my active applications do not start leaking data out over a regular connection (because they will have no gateway to do so). If I start openvpn manually (to the 46.246.x.y gateway), everything works and the connection comes up fine and I get a default gateway via my VPN adapter. If I click my VPN connection in the applet drop down menu, nothing happens, but if I create an identical configuration with a default gateway and click it, it works. I request that the logic that handles connection activation check whether the VPN gateway has been defined as an IP address, and that in the absence of a default route, there is atleast a route for that IP address. If so, it should continue anyway, rather than doing nothing.
i am also having this issue in 2018
bugzilla.gnome.org is being shut down in favor of a GitLab instance. We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time. If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/ Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).