Connection-specific VPN settings #9103
Replies: 3 comments
-
|
Hello! Thanks for your detailed feature request! 🙌 We'll keep an eye on the interest from the community on this. We know that similar feature requests have been made before, so it's not an esoteric request. |
Beta Was this translation helpful? Give feedback.
-
|
I'm also looking for this, and there is a real use case for that. WireGuard is blocked in my cellular network so I use Shadowsocks, but my other networks that doesn't block WireGuard also has to use Shadowsocks unless I disable it, which is not something you'd want to do every time you're going to a place and leaving. There is a performance loss happening due to Shadowsocks, it's small but it's there. So we should be able to customize connection details for specific conditions. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I've been looking for this feature too: in my home, I have some git repositories hosted locally only and some servers I can connect to using ssh. Having a per-network setting would be really helpful for these cases! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I have checked if others have suggested this already
Feature description
I'd appreciate if Mullvad would offer connection-specific overrides for all/most VPN settings. Specifically, I would have had a use for this with
but I think it makes sense for several other settings as well.
Currently, anytime the necessity to change these settings (away from a secure and performant default) arises, I'll usually proceed via:
By making such setting adaptations per-network, these issues would be remedied to a large extent, for a better UX and effectively improved security.
In #3218, some concerns regarding security have been voiced. However, at least in my case, the real concern is insecure public Wifis rather than someone spoofing a BSSID I trust.
Anyone who actually fears a targeted spoofing attack can simply not use connection-specific settings, and appropriate warnings in the UI could create the awareness for this.
Some further ideas to in this regard:
Related feature requests are:
Alternative solutions
I don't think there's a real alternative: This really needs to be as automated as possible, otherwise, I'll inevitably forget to change settings back. Usually, I realize this only a long time afterwards, for example when seeing unexpected network devices discovered by the file manager (i.e. too late).
Type of feature
Operating System
Beta Was this translation helpful? Give feedback.
All reactions