GNOME Bugzilla – Bug 784644
Wi-Fi reconnect issue with VPN autoconnect
Last modified: 2020-11-12 14:29:12 UTC
I have set my Wi-Fi to connect automatically when a network is available, which works fine. However, if I set the Wi-Fi to automatically connect to a VPN connection as well, than the Wi-Fi keeps dropping on any occasion it tries to connect. This happens after booting into Fedora or after the Wi-Fi connection is lost and Gnome tries to reconnect. The network is found and Gnome tries to autoconnect to the Wi-Fi but fails while the VPN is trying to connect simultaneously. Than Gnome tries again to connect and fails again. This is going on until I manually connect to the Wi-Fi or until I disable the VPN manually from connecting until the Wi-Fi is connected. I have set the following settings using the nm-connection-editor. "Automatically connect to this network when it is available" set ON "Automatically connect to VPN when using this connection" set ON Fedora 25. Wayland. kernel 4.11.7-200.fc25.x86_64. gnome-shell 3.22.3. NetworkManager 1.4.4
FWIW I found that just marking the VPN 'persistent' gets me closer to a working configuration. That way, I still have to bring up the VPN manually but at least it stays logically "up" over a suspend or other reconnect, and I don't have to authenticate to the VPN again as I would if it was a new connection triggered each time. NM doesn't quite get that right because it doesn't set up the VPN routing again, but there's a workaround in a dispatcher script in bug #794190
Maybe related to Bug 785699
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).