Indeed, the starting point is sharing IP's across servers with port-ranges.
But there is more:
* awesome performance allowed by anycast.
* ability to route /32 instead of /24 per datacenter.
Generally, with this tech we can have much better IP usage density, without sacrificing reliability or performance. You can call it "global anycast-based stateless NAT" but that often implies some magic router configuration, which we don't have.
Here's one example of problems we run into - the lack of connectx() syscall on Linux - makes it hard to actually select port range to originate connections from:
https://blog.cloudflare.com/how-to-stop-running-out-of-ephem...
Of course not every destination is an IPv6 host, so IPv4 remains necessary, but at least IPv6 can avoid the need for port slicing, since you can encode the same bucketing information in the IP address itself.
I've seen this idea used as a cool trick [0] to implement a SOCKS proxy that randomizes outbound IPv6 address to be within a publicly routed prefix for the host (commonly a /64).
I guess as long as you need to support IPv4, then port slicing is a requirement and IPv6 won't confer much benefit. (Maybe it could help alleviate port exhaustion if IPv6 addresses can use dynamic ports from any slice?)
Either way, thanks for the blog post, I enjoyed it!
Probably they didn't need to do much work with IPv6, since half of the post is solving IPv4 exhaustion problems.
Warp uses its own set of egress IPs and their geolocation is close to your real location.
Maybe this ends up reducing cost on customers though, because the international transit happens in your backbone network rather than on the internet (customer-side).
> To avoid geofencing issues, we need to choose specific egress addresses tagged with an appropriate country, depending on WARP user location. (...) Instead of having one or two egress IP addresses for each server, now we require dozens, and IPv4 addresses aren't cheap.
> Instead of assigning one /32 IPv4 address for each server, we devised a method of assigning a /32 IP per data center, and then sharing it among physical servers (...) splitting an egress IP across servers by a port range.