Quick setting, add autoconnect toggle to VPN connections#1937
Quick setting, add autoconnect toggle to VPN connections#1937Citingmarc wants to merge 1 commit into
Conversation
|
I like the idea of making finding the setting simpler. But I noticed a couple of things. @pop-os/ux Built from source; testing with two ProtonVPN connections using seperate interfaces (proton0 & proton1):More than one VPN can have Built from source; Testing with two ProtonVPN connections using the same interface (proton0):When both VPNs are on different interfaces, and both connections have |
|
Yeah it can still lead to confusing situations. My two cents is that I was happy that they defaulted to auto connect (although it was unexpected). But when adding multiple ones, they both connected and it was very obvious what the problem was, just not how to solve it. I personally lean towards keeping the drop down as minimal as possible. Advanced users they can dig into the settings or use nmcli directly if they want to adjust priorities and interfaces. Just that for some people especially light users they may want to control which VPN auto connects if any at all. Especially if they only have one VPN just this single toggle is enough to avoid digging further into any other settings. Some VPNs may significantly slow down the internet, and the default behavior of auto connecting would not be ideal then. |

I've been loving CosimcDE, great work!
I added a couple of incompatible wireguard connections as VPNs through the settings app is that they both would auto connect on login or reboot. Being that both were incompatible I had to disable one of them every restart. I couldn't immediately find the auto connect setting, had to look it up. So I figured since I had a bit of rust experience that it would be fun to try and make it more accessible. Now, not sure if you'll care for this feature or may prefer to keep it on the settings, so feel free to close this if it's not a good fit. But I've found it useful and very nice to work on this codebase 👍