21–30 of 372 posts
This is 2.5% of the total adress space - not usable, total. It's about the equivalent of 6.25 class A (/8) prefixes. Quite impressive.
Nothing compared to the US federal government. I count 13 /8 blocks for the DoD, and one for the USPS, so 14 in total. https://en.wikipedia.org/wiki/List_of_assigned_/8_IPv4_addre...
From what I understand the problem with IPv6 isn't technical problems it is with legacy. According to what I know in Africa and Asia they have mostly already been running on IPv6 the problem is just basically a bunch of lazy network admins in NA and the EU that don't want to learn the new tech and organizations that don't want to switch.
Earlier quoted context omitted.
https://github.com/seligman/aws-ip-ranges Regardless of how you calculate the %, it's doubled in a few years. I still would love to know what they were thinking when they added 252.0.0.0/10 to their list.
Is that 252.0.0.0 publicly routed? I can't find an official whois entry, so they just took some reserved address space without asking? It's listed as reserved here: https://www.iana.org/assignments/ipv4-address-space/ipv4-add...
I got the impression it was meant for some internal to AWS use and was pushed to their list of IP addresses erroneously, but I barely speak to AWS, much less speak for them.
How are we not out of IPv4 addresses already? Aren't there a billion phones out there? And probably the same number of PCs and god knows how many servers?
Does anyone sell a /30 or smaller block?
From what I understand the problem with IPv6 isn't technical problems it is with legacy. According to what I know in Africa and Asia they have mostly already been running on IPv6 the problem is just basically a bunch of lazy network admins in NA and the EU that don't want to learn the new tech and organizations that don't want to switch.
> …a bunch of lazy network admins in NA and the EU that don't want to learn the new tech…
That’s a cheap shot, and it’s not called for.
Network admins are paid to make the networks run. Anything else is less important. If your IPv6 network experiences some small problems, well, you’re going to hold on to IPv4 because small network problems can mean big inefficiencies or lost sales.
Just a few weeks ago I was on the phone with my WiFi router’s vendor for a couple hours or more because IPv6 traffic wasn’t working through it. I had narrowed the problem down to the router itself. It’s not necessarily that IPv6 is poorly tested or has technical problems, it’s that there’s a long tail of devices/configurations/software out there which screw it up, and it’s often cheaper to just use IPv4 rather than suffer even the minor inconveniences and troubleshooting sessions necessary to run IPv6.
It’s moving forward but it’s slow progress, and it’s not because network admins are lazy or stupid. It’s because there’s a lot of work to be done and not everyone has much of an incentive to do it at all.
Earlier quoted context omitted.
https://github.com/seligman/aws-ip-ranges Regardless of how you calculate the %, it's doubled in a few years. I still would love to know what they were thinking when they added 252.0.0.0/10 to their list.
Is that 252.0.0.0 publicly routed? I can't find an official whois entry, so they just took some reserved address space without asking? It's listed as reserved here: https://www.iana.org/assignments/ipv4-address-space/ipv4-add...
I’d be curious how that compares to other cloud providers.
2,344,576 IPs, so ~47mm on the same math.