# ProtonVPN IP Leakage on Linux and Workaround

**URL:** https://discuss.privacyguides.net/t/protonvpn-ip-leakage-on-linux-and-workaround/26727
**Category:** General
**Tags:** article, software
**Created:** 2025-04-15T15:22:09Z
**Posts:** 27
**Showing post:** 25 of 27

## Post 25 by @ignoramous — 2025-12-20T21:25:21Z

> [@anon98749087](#):
>
> My main priority is NO LEAKS, so I set my browser homepage to [Connection check | Mullvad VPN](https://mullvad.net/en/check) and everything looks good right now

Browser side checks don’t reveal the complete picture. And in some cases, paint the wrong picture.

> [@ProtonVPN potentially misleading UI](https://discuss.privacyguides.net/t/protonvpn-potentially-misleading-ui/26543/24):
>
> And then we wonder why some accuse privacy (especially or rather exclusively VPN) companies as selling snake oil. PG (both the community and the website) is right to call it out should stay away from those. This topic is on a privacy-focused VPN app, not an rich person’s aerodynamic race fantasy death shell. Edit If I had a dime for the number of times I get sent this screenshot because my app is “leaking DNS” … thinking

> [@anon98749087](#):
>
> Or, as long as the wg icon is showing connected in my gnome options menu, is this a true killswitch like on android?

Android’s killswitch is under the control of the end-user. These are named “Always-on VPN” and “Block connections without VPN” (in English), and both must be turned ON for your VPN app, from Android’s VPN settings.

Note that, on Android (and on most OSes), some high privileged apps (mostly OEM and Google apps), which are typically pre- installed (some you can disable but none can you uninstall), do retain the capability to bypass the “killswitch”. A network monitor project I co-develop keeps track of such bypasses in AOSP here: [Show Android components that can bypass VPN even in lockdown mode · Issue #224 · celzero/rethink-app · GitHub](https://github.com/celzero/rethink-app/issues/224)

And even if (hypothetically) AOSP never allowed such a bypass, the OEMs can change that behaviour for their Android distribution (unfortunately, as of Android 16, as part of its compatibility requirements, Google doesn’t enforce OEMs confirm to “Block connections without VPN” ([ref](https://source.android.com/docs/compatibility/16/android-16-cdd) / [mirror](https://archive.vn/oRpYS)).

> [@anon98749087](#):
>
> Can I safely use wg-quick down and wg-quick up without risk of a leak?

Not quite sure, as it depends on the commands being run by wg-quick on `up` and `down` on your setup. Which setup guide are you using?

> [@anon98749087](#):
>
> ALSO: Does anyone know what features are missing when you use mullvad this way? I know DAITA requires the mullvad gui, but is there anything else?

They’ve recently added [“light weight” anti-censorship measures](https://discuss.privacyguides.net/t/introducing-lightweight-wireguard-obfuscation-mullvad-vpn/32753/3), too. That said, I consider custom features such as DAITA a form of lock-in. I’d not worry about it too much, if I were you.

---

_[View the full topic](https://discuss.privacyguides.net/t/protonvpn-ip-leakage-on-linux-and-workaround/26727)._