AWS adds an extra 5.5M IPv4 addresses
131–140 of 283 posts
Re: AWS adds an extra 5.5M IPv4 addresses
#132Earlier quoted context omitted.
I've worked in the cloud hosting industry for a decade and a half. The entire time, we were warned about the IPv4 shortage and how we needed to switch to IPv6 soon(tm). Well, things haven't changed. Everyone is dragging their feet on IPv6 adoption from hosting providers, ISPs, hardware manufacturers, and software developers. I predicted this years ago and always said that it would require a government mandate to move…
NAT is ramping up on client side. Many home-internet connections are now NATted twice - in CPE, then again in CGN. On the server side, in contrast, NAT is winding down. 15 years ago, it was common to have either DMZ-style NAT, or on AWS you had to have NAT (they call it EIP). Nowadays, having a CDN or could-native load-balancer in front of your server is increasingly common. And behind those, that server just don't n…
Luckily i had created a reverse ssh tunnel on a vps before leaving.
Re: AWS adds an extra 5.5M IPv4 addresses
#133Earlier quoted context omitted.
I know few universities that still use static ipv4 for computer pools. The admins claim easy for us to monitor for misuse.
This is correct use of IP space. With a routeable IP on every computer, no one would be a second class (consume-only) user of the Internet.
So practically a globally addressable IP or not makes no impact on ability to be routable publicly
Re: AWS adds an extra 5.5M IPv4 addresses
#134Earlier quoted context omitted.
Well, if that organisation didn't have a use for those addresses... I don't see what the big deal is.
I have 127.0.0.0/8 for sale! Give me 100 million euros and it's all yours! What do you mean some people are actually using those addresses and i don't own them? RFC makes it very clear local link means my own machine and i pretty much own my own machine, thank you. Do you see how ridiculous is this situation now?
Re: AWS adds an extra 5.5M IPv4 addresses
#135IPv6 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.
This. I honestly think the FCC will have to mandate it's adoption and give a hard date for the termination of IPv4 for it to work. Both will need to occur.
Re: AWS adds an extra 5.5M IPv4 addresses
#136IPv6 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.
The funny thing is social media and streaming is already there: facebook.com has IPv6 address 2a03:2880:f119:8083:face:b00c:0:25de instagram.com has IPv6 address 2406:da00:ff00::23ae:4dc1 snapchat.com has IPv6 address 2001:4860:4802:36::15 netflix.com has IPv6 address 2600:1f14:62a:de82:822d:a423:9e4c:da8d youtube.com has IPv6 address 2404:6800:4006:810::200e The holdouts are somewhere else. Imagine if cloudflare and…
Re: AWS adds an extra 5.5M IPv4 addresses
#137low 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?
Between cloudflare and AWS/Azure/Google most of the Internet is an oligopoly right now.
Interesting how nobody else replied to this part of your comment.
Re: AWS adds an extra 5.5M IPv4 addresses
#138Earlier quoted context omitted.
NAT is ramping up on client side. Many home-internet connections are now NATted twice - in CPE, then again in CGN. On the server side, in contrast, NAT is winding down. 15 years ago, it was common to have either DMZ-style NAT, or on AWS you had to have NAT (they call it EIP). Nowadays, having a CDN or could-native load-balancer in front of your server is increasingly common. And behind those, that server just don't n…
Yesterday i spend 2 hours trying to figure out why i couldn't ping my home router, only to find out this is probably the reason. Luckily i had created a reverse ssh tunnel on a vps before leaving.
Re: AWS adds an extra 5.5M IPv4 addresses
#139Earlier quoted context omitted.
Well, if that organisation didn't have a use for those addresses... I don't see what the big deal is.
That organization did not own those addresses. In the most generous interpretation of the situation, they were administrative custodians to the good usage of those addresses. Reselling them to a for-profit company was definitely not what was intended by anyone and directly contradicts their mission as custodians. Those addresses were that of the global radioamateur community and no one else's. That's why i made a com…
These did not belong to amateur radio, TAPR, the ARRL or anyone but this organization.
Re: AWS adds an extra 5.5M IPv4 addresses
#140IPv6 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.
I actually think that what will really drive IPv6 adoption is if the price of IPv4 space continues its upward trajectory unabated. The price has about doubled at auction in the last year. How are those two things related? 1. There are a ton of owners sitting on inefficiently used IP space. Any company (not doing cloud hosting or network transit) that's holding a /8 is almost certainly using it very inefficiently, but…
...or the opposite: large cloud providers own a lot of valuable IPv4 space. They might want to increase the value of their investment.
Encouraging switching to pure-IPv6 connectivity would be a big loss for them.