SUMMARY Feature request: Ability to cancel secondary (VPN) connection. When VPN is temporarily unavailable, it is not easy to skip VPN connection and just use a normal network connection without VPN. STEPS TO REPRODUCE 1. Add Wi-Fi connection in plasma-nm. 2. Add VPN (e.g. openvpn) in plasma-nm. 3. In the Wi-Fi connection's settings, enable "Automatically connect to VPN" and choose the openvpn VPN connection. 4. Break/stop the openvpn server or wait until it goes offline by itself ;) 5. In the plasma-nm applet, click Connect to connect to Wi-Fi. (Or imagine that you have just turn on the computer and now NetworkManager tries to reconnect to Wi-Fi automatically.) 6. Assume you can't fix the VPN server and you want to go online immediately using plain Wi-Fi connection without VPN. OBSERVED RESULT To go offline, you have to open plasma-nm settings dialog, select the Wi-Fi connection, disable "Automatically connect to VPN", then click OK/Apply and finally manually reconnect to Wi-Fi in the plasma-nm applet. This approach is complicated and time-consuming. I would like to avoid it, but there is no good alternative. EXPECTED RESULT There should be a button "Skip/Bypass VPN" in the plasma-nm applet on in a Plasma notification. This button appears when Wi-Fi connection is live, and at the same time the secondary VPN connection is being attempted but not ready yet. When you click on this button, plasma-nm should go online using just the Wi-Fi connection, like if you didn't enable "Automatically connect to VPN". SOFTWARE/OS VERSIONS Operating System: Fedora 31 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.12.5 Kernel Version: 5.3.7-301.fc31.x86_64 OS Type: 64-bit Processors: 2 × Intel® Celeron® CPU B800 @ 1.50GHz Memory: 3,8 ГиБ ADDITIONAL INFORMATION
This is unfortunately how NetworkManager behaves, we cannot do nothing about it. If you want such support, you will need to go to NetworkManager devs and open a bug there. You can do it here: https://gitlab.freedesktop.org/NetworkManager/NetworkManager
(In reply to Jan Grulich from comment #1) > This is unfortunately how NetworkManager behaves, we cannot do nothing about > it. If you want such support, you will need to go to NetworkManager devs and > open a bug there. > > You can do it here: > https://gitlab.freedesktop.org/NetworkManager/NetworkManager Reported at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/299