News for hackers. Stuff that matters.
Re:Mullvad exit IPs are surprisingly identifying by gruez on Thursday May 14, 2026 @11:15PM (#48144138)
>Surprisingly, the exit IP you are given is not randomized each time you connect to the server, but deterministically picked based on your WireGuard key

What's the point of this? This seems more complicated to implement than mapping exit ips at the server level, so surely they must be doing this for a good reason?

Re:Mullvad exit IPs are surprisingly identifying by arciini on Thursday May 14, 2026 @11:18PM (#48144157)
I'd guess that this is to ensure one abusive user doesn't get every other user blocked from a large service (say, Google) for botting over the VPN and constantly rotating IPs.

It's a practical measure, but definitely has a privacy cost though.

Re:Mullvad exit IPs are surprisingly identifying by stevekemp on Thursday May 14, 2026 @11:24PM (#48144194)
It's possible that contributes, but to be honest most VPN users are split "privacy seeking" and "abusive". Though I grant you paid users are probably slightly more circumspect than users of Tor, etc.

It seems more likely this is just about load-balancing use against their available nodes.

Re:Mullvad exit IPs are surprisingly identifying by TheDong on Thursday May 14, 2026 @11:57PM (#48144386)
It's a lot easier to implement because it's more stateless, and it's a better user experience.

If you get a new exit IP each time you connect, you need something like a NAT table to look up "key 0xabc exits ip 1.2.3.4", and that grows to be the size of the number of users you have active, so fairly large.

With a static mapping derived from the key, you don't need a table like that.

It's also better UX since it means reconnecting your VPN software (say you switch wifi hotspots) doesn't give you a different IP address, so things like SSH sessions can resume, which wouldn't be possible if it were a different public IP each time.

Re:Mullvad exit IPs are surprisingly identifying by Riany on Friday May 15, 2026 @12:05AM (#48144437)
My guess is deterministic assignment makes load distribution and debugging easier. But for a privacy product, that convenience probably needs to be reconsidered
Re:Mullvad exit IPs are surprisingly identifying by tempest_ on Thursday May 14, 2026 @11:18PM (#48144158)
I imagine there are a bunch of things on the internet that break if you start trying to connect to them from varying IP addresses. Things like the various CAPTCHA schemes and rate limiting etc, IP reputation etc.
Re:Mullvad exit IPs are surprisingly identifying by lmm on Thursday May 14, 2026 @11:34PM (#48144259)
> I imagine there are a bunch of things on the internet that break if you start trying to connect to them from varying IP addresses. Things like the various CAPTCHA schemes and rate limiting etc, IP reputation etc.

Given how much of the world is stuck behind CGNAT now, I would expect any major sites to handle it.

Re:Mullvad exit IPs are surprisingly identifying by nly on Friday May 15, 2026 @03:33AM (#48145635)
Ironically the CGNAT at my ISP is so broken at peak times the only way I can actually use the internet is via a VPN (presumably because I then only occupy one connection tracking slot on the NAT)

I'm also stuck in a 2 year ISP contract