News for hackers. Stuff that matters.
Re:Cloudflare servers don't own IPs now, so how do they conn... by majke on Friday November 25, 2022 @11:36AM (#33744051)
Author here, I know this is a dismissive comment, but I'll bite anyway.

As far as I understand the history of the IP protocol, initially an IP address pointed to a host. (/etc/hosts file seems that way)

Then it was realized a single entity might have multiple network interfaces, and an IP started to point to a network card on a host. (a host can have many IP's). Then all the VRF, dummy devices, tuntaps, VETH and containers. I guess an IP is now pointing to a container or VM. But there is more. For performance you can (almost should!) have an unique IP address per NUMA node. Or even logical CPU.

In modern internet a server IP: points to a single CPU on a container in a VM on a host.

Then consider Anycast, like 1.1.1.1 or 8.8.8.8. An IP means something else... it means a resource.

On the "client" side we have customer NAT's. CG NAT's and VPN's. An IP means similarly little.

The IP's are really expensive, so in some cases there is a strong advantage to save them. Take a look at https://blog.cloudflare.com/addressing-agility/

"So, test we did. From a /20 address set, to a /24 and then, from June 2021, to an address set of one /32, and equivalently a /128 (Ao1). It doesn’t just work. It really works"

We're able to serve "all cloudflare" from /32.

There is this whole trend of getting denser and denser IP usage. It's not avoidable. It's not "breaking the Internet" in any way more than "NAT's are breaking the Internet". The network evolves, because it has to. And for one, I don't think this is inherently bad.

Re:Cloudflare servers don't own IPs now, so how do they conn... by superkuh on Friday November 25, 2022 @12:33PM (#33744774)
>It's not avoidable. It's not "breaking the Internet" in any way more than "NAT's are breaking the Internet".

I agree. NATs, particularly the Carrier NAT that smartphone users are behind, has broken the internet. It's made it so most people do not have ports and cannot participate in the internet. So now software developers cannot write software that uses the internet (without depending on third parties). This is bad. So is what you've done.

Someday ipv6 will save us.

Re:Cloudflare servers don't own IPs now, so how do they conn... by oxplot on Friday November 25, 2022 @11:14PM (#33749858)
From your website:

> If your browser is warning you about the SSL certificate, ignore it. Self-signed (and >380 day) certificates are perfectly valid and making users think they are dangerous is maladaptive.

Given that's irresponsible thing to write and share with your visitors and most likely the result of either ignorance or laziness on your part on the most basic aspect of Internet security, you shouldn't really advertise your opinion on anything Internet related, for your own sake.

Re:Cloudflare servers don't own IPs now, so how do they conn... by ignoramous on Saturday November 26, 2022 @01:19AM (#33750440)
> And for one, I don't think this is inherently bad.

Ao1 has super nice censorship resistance properties. With ECH, that essentially is game over for firewalls. Can't wait to see just how Cloudflare rolls Ao1 out (I'd imagine it'd be opt-in, like Green Compute).

> Then it was realized a single entity might have multiple network interfaces, and an IP started to point to a network card on a host

Much to Nagle's chagrin: https://news.ycombinator.com/item?id=21088736 (a Berkeleyism as he calls it)