Earlier quoted context omitted.
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.
PureVPN IPv6 Leak
21–30 of 93 posts
Re: PureVPN IPv6 Leak
#22Re: PureVPN IPv6 Leak
#23I donwt know any single VPN provider apart from Mullvad with proper v6 implementation.
I'm satisfied!
Re: PureVPN IPv6 Leak
#24I 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
#25Earlier quoted context omitted.
Everything is TLS-encrypted anyway these days, so the primary concern is metadata privacy. When it comes to that, I trust VPN providers about as much as ISPs (i.e. absolutely not).
VP.NET doesn't require any trust at all [1][2]. [1] https://vp.net/l/en-US/blog/Don%27t-Trust-Verify [2] I work for VP.NET and can answer any questions regarding the technology as well!
Re: PureVPN IPv6 Leak
#26What about NordVPN and ExpressVPN are those somewhat trustworthy?
Re: PureVPN IPv6 Leak
#27I agree that relying solely on desktop VPN clients (especially closed-source ones) is risky... The network namespaces approach is new to me, but it looks like a solid way to isolate traffic and avoid these kinds of leaks entirely. Thanks for the suggestions.
Re: PureVPN IPv6 Leak
#28I donwt know any single VPN provider apart from Mullvad with proper v6 implementation.
Solid dev + OSS ecosystem + Flat rates I'm satisfied!
Re: PureVPN IPv6 Leak
#29I 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
#30Earlier quoted context omitted.
Alternatively, disable ipv4. The same statement holds true.
Lots of things will break if you disable ipv4, including my work provided zscaler windows laptop (and not break in the good way where it fails open when you block traffic to zscaler nodes on your router) Very little will break if you disable ipv6