News for hackers. Stuff that matters.
Re:Cloudflare servers don't own IPs now, so how do they conn... by chatmasta on Friday November 25, 2022 @11:41AM (#33744131)
I was surprised IPv6 was only briefly mentioned! Is that something you're looking at next, or are you already running an IPv6 egress network?

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!

[0] https://github.com/blacklanternsecurity/TREVORproxy

Re:Cloudflare servers don't own IPs now, so how do they conn... by miyuru on Friday November 25, 2022 @01:03PM (#33745091)
I was also interested to know how this was handled for IPv6, but it was only briefly mentioned.

Probably they didn't need to do much work with IPv6, since half of the post is solving IPv4 exhaustion problems.

Re:Cloudflare servers don't own IPs now, so how do they conn... by chriscappuccio on Friday November 25, 2022 @05:13PM (#33747388)
Cloudflare wants to make money. The IPv6 features can come second as v6 usage increases.
Re:Cloudflare servers don't own IPs now, so how do they conn... by dknecht on Friday November 25, 2022 @05:36PM (#33747591)
All of Cloudflare services ship with IPv6 day 1. IPv6 not an issue as we have enough IPv6 for each machine to have own IPs.