PureVPN IPv6 Leak

I strongly suggest that you use something like Network Namespaces through Vopono[0] or Gluetun[1] if you use a commercial VPN for "privacy" or "security" aka torrenting and shitposting. Relying on these clients is always a gamble and if your software (Browser, Torrentclient, etc.) cannot know you public IP only the internal IP of the VPN you are also safe against some exploits and misconfigurations a desktop client won't protect you against.

[0] https://github.com/jamesmcm/vopono [1] https://github.com/qdm12/gluetun

Re: PureVPN IPv6 Leak

#5

Post by nikanj » Wed, Sep 17, 2025, 1:05 PM UTC

IlikeKitties wrote: post #4

I strongly suggest that you use something like Network Namespaces through Vopono[0] or Gluetun[1] if you use a commercial VPN for "privacy" or "security" aka torrenting and shitposting. Relying on these clients is always a gamble and if your software (Browser, Torrentclient, etc.) cannot know you public IP only the internal IP of the VPN you are also safe against some exploits and misconfigurations a desktop client w…

I strongly suggest you disable ipv6, as nothing will break by disabling it but many things break with it enabled.

Re: PureVPN IPv6 Leak

#6

Post by Varelion » Wed, Sep 17, 2025, 1:06 PM UTC

IlikeKitties wrote: post #4

I strongly suggest that you use something like Network Namespaces through Vopono[0] or Gluetun[1] if you use a commercial VPN for "privacy" or "security" aka torrenting and shitposting. Relying on these clients is always a gamble and if your software (Browser, Torrentclient, etc.) cannot know you public IP only the internal IP of the VPN you are also safe against some exploits and misconfigurations a desktop client w…

Wouldn't blocking IPv6 and using a kill-switch prevent leaking?

Re: PureVPN IPv6 Leak

#7

Post by indigo945 » Wed, Sep 17, 2025, 1:06 PM UTC

nikanj wrote: post #5

IlikeKitties wrote: post #4

I strongly suggest that you use something like Network Namespaces through Vopono[0] or Gluetun[1] if you use a commercial VPN for "privacy" or "security" aka torrenting and shitposting. Relying on these clients is always a gamble and if your software (Browser, Torrentclient, etc.) cannot know you public IP only the internal IP of the VPN you are also safe against some exploits and misconfigurations a desktop client w…

I strongly suggest you disable ipv6, as nothing will break by disabling it but many things break with it enabled.

Alternatively, disable ipv4. The same statement holds true.

Re: PureVPN IPv6 Leak

#8

Post by ZiiS » Wed, Sep 17, 2025, 1:10 PM UTC

indigo945 wrote: post #7

nikanj wrote: post #5

Earlier quoted context omitted.

I strongly suggest you disable ipv6, as nothing will break by disabling it but many things break with it enabled.

Alternatively, disable ipv4. The same statement holds true.

Unfortunately this is not true, loads of cool techy stuff (Sentry, GitHub) etc still don't work properly on IPv6, less techy stuff really didn't care at all.

Re: PureVPN IPv6 Leak

#9

Post by rasengan » Wed, Sep 17, 2025, 1:13 PM UTC

Separately, PureVPN is one of the providers you can’t trust [1].

[1] https://www.makeuseof.com/worst-vpns-you-shouldnt-trust/

Re: PureVPN IPv6 Leak

#10

Post by IlikeKitties » Wed, Sep 17, 2025, 1:21 PM UTC

Varelion wrote: post #6

IlikeKitties wrote: post #4

I strongly suggest that you use something like Network Namespaces through Vopono[0] or Gluetun[1] if you use a commercial VPN for "privacy" or "security" aka torrenting and shitposting. Relying on these clients is always a gamble and if your software (Browser, Torrentclient, etc.) cannot know you public IP only the internal IP of the VPN you are also safe against some exploits and misconfigurations a desktop client w…

Wouldn't blocking IPv6 and using a kill-switch prevent leaking?

No, not in all cases. Imagine your Browser gets 0-dayed and just send all IPs it sees to an endpoint.