AWS adds an extra 5.5M IPv4 addresses
github.com
AWS adds an extra 5.5M IPv4 addresses
1–10 of 283 posts
Re: AWS adds an extra 5.5M IPv4 addresses
#2low whistle I imagine they paid a pretty penny for those /12s.
A thought comes to me: If IPv6 adoption continues to drag along, and AWS/Azure/GCP continue to expand their IP blocks like this, how quickly are we in danger of the cloud providers effectively being the Internet?
Re: AWS adds an extra 5.5M IPv4 addresses
#3low whistle I imagine they paid a pretty penny for those /12s. A thought comes to me: If IPv6 adoption continues to drag along, and AWS/Azure/GCP continue to expand their IP blocks like this, how quickly are we in danger of the cloud providers effectively being the Internet?
I guess there's a large pool of IP addresses used by residential ISPs that could be recycled relatively easily.
When I lived in Ireland I only got a public IPv6, my IPv4 was behind CG-NAT. The nerd in me wasn't a fan of that on paper, but in reality I didn't have any issues with it.
I could see ISPs making a quick buck by switching to CG-NAT on IPv4 so they can sell off their IPv4 blocks.
Those IPs being recycled for servers/services doesn't seem too risky, given that they're not typically hosting anything.
Re: AWS adds an extra 5.5M IPv4 addresses
#4low whistle I imagine they paid a pretty penny for those /12s. A thought comes to me: If IPv6 adoption continues to drag along, and AWS/Azure/GCP continue to expand their IP blocks like this, how quickly are we in danger of the cloud providers effectively being the Internet?
Having just realized my internet provider, cox, does not actually support ipv6 for the 2 million plus subscribers in my state I think it is safe to say that ipv6 is dead and will never take the place of ipv4 in our lifetimes.
Don't get me wrong. They say they support it, they have lots of PR that says the support it but in fact as a subscriber they do not.
Re: AWS adds an extra 5.5M IPv4 addresses
#5low whistle I imagine they paid a pretty penny for those /12s. A thought comes to me: If IPv6 adoption continues to drag along, and AWS/Azure/GCP continue to expand their IP blocks like this, how quickly are we in danger of the cloud providers effectively being the Internet?
Having just realized my internet provider, cox, does not actually support ipv6 for the 2 million plus subscribers in my state I think it is safe to say that ipv6 is dead and will never take the place of ipv4 in our lifetimes. Don't get me wrong. They say they support it, they have lots of PR that says the support it but in fact as a subscriber they do not.
Ehn, I don't know if you can go from
"my internet provider, cox, does not actually support ipv6" to "I think it is safe to say that ipv6 is dead".
There are much more comprehensive ways to look at ipv6 adoption, e.g. https://www.google.com/intl/en/ipv6/statistics.html
Re: AWS adds an extra 5.5M IPv4 addresses
#6IPv6 will never happen without someone forcing hands of big corps and ISPs to switch to Ipv6.
Imagine all social media and streaming services, disable ipv4 within a month. These are not critical services but still will force ISPs to make the switch.
Re: AWS adds an extra 5.5M IPv4 addresses
#7low whistle I imagine they paid a pretty penny for those /12s. A thought comes to me: If IPv6 adoption continues to drag along, and AWS/Azure/GCP continue to expand their IP blocks like this, how quickly are we in danger of the cloud providers effectively being the Internet?
Having just realized my internet provider, cox, does not actually support ipv6 for the 2 million plus subscribers in my state I think it is safe to say that ipv6 is dead and will never take the place of ipv4 in our lifetimes. Don't get me wrong. They say they support it, they have lots of PR that says the support it but in fact as a subscriber they do not.
Mine had some beta program years ago. You had to find a number to call which was hidden away in a locked filing cabinet hidden away in a disused lavatory.
They were purchased recently and maybe there is hope now.
Re: AWS adds an extra 5.5M IPv4 addresses
#8low whistle I imagine they paid a pretty penny for those /12s. A thought comes to me: If IPv6 adoption continues to drag along, and AWS/Azure/GCP continue to expand their IP blocks like this, how quickly are we in danger of the cloud providers effectively being the Internet?
Having just realized my internet provider, cox, does not actually support ipv6 for the 2 million plus subscribers in my state I think it is safe to say that ipv6 is dead and will never take the place of ipv4 in our lifetimes. Don't get me wrong. They say they support it, they have lots of PR that says the support it but in fact as a subscriber they do not.
in our lifetimes. you don't think ipv6 will overtake ipv4 in the next 50-odd years? think about the year 1971 and what was thought possible then
Re: AWS adds an extra 5.5M IPv4 addresses
#9Who the heck has a couple /12s and a /13 just lying around unused?
And there are even some earlier pickups of two /10s: 252.0.0.0/10 and 44.192.0.0/10. Wow.
Re: AWS adds an extra 5.5M IPv4 addresses
#10low whistle I imagine they paid a pretty penny for those /12s. A thought comes to me: If IPv6 adoption continues to drag along, and AWS/Azure/GCP continue to expand their IP blocks like this, how quickly are we in danger of the cloud providers effectively being the Internet?
I guess there's a large pool of IP addresses used by residential ISPs that could be recycled relatively easily. When I lived in Ireland I only got a public IPv6, my IPv4 was behind CG-NAT. The nerd in me wasn't a fan of that on paper, but in reality I didn't have any issues with it. I could see ISPs making a quick buck by switching to CG-NAT on IPv4 so they can sell off their IPv4 blocks. Those IPs being recycled for…
I find the ipv6 address scary because IP geolocation gives that in the same city district. Cgnat would be better because the server would see ipv4 of the ISP.
I don't know, is there a way to not show my ipv6 and fall back on cgnat address because that looks much more secure in terms of not getting doxed and ad tracked.