Cloud giant AWS will start charging customers for public IPv4 addresses from next year, claiming it is forced to do this because of the increasing scarcity of these and to encourage the use of IPv6 instead.
The update will come into effect on February 1, 2024, when AWS customers will see a charge of $0.005 (half a cent) per IP address per hour for all public IPv4 addresses. … These charges will apply to all AWS services including EC2, Relational Database Service (RDS) database instances, Elastic Kubernetes Service (EKS) nodes, and will apply across all AWS regions, the company said.
I’m going on professional year 24 of clients requiring that IPv6 be deactivated on every device in their network. Whee.
My current ISP still does not offer IPv6 🤦 🤦 🤦
Verizon, my ISP, offers IPv6 in my area but the implementation is broken and it ends up being an order of magnitude slower than simply using IPv4 and HE as an IPv6 tunnel broker.
AT&T is the same. And the last time I looked they don’t give you enough address space to host your own subnet. You get a /64 instead of a /56. And it’s slower than ipv4.
Every few months I try it out, complain and then switch it off.
I’m on ATT. I can get a /60 from their V6 router. I use /64s with each of my VLANs. I use a true bridge mode that bypasses their gateway device only using it for eap authentication. My router handles the connection. It works great honestly. Not sure what you mean by it being slower than V4. The V6 is equally as fast if not faster, here in Dallas. The routes are great on both V4 and V6, it takes on average 4 hops for me to reach the rest of the Internet. It’s about 1-3ms RTT to city-local addresses over ICMP echo. Very stable, too.
Interesting. In NC here. Not sure if there’s a difference regionally. I was seeing that kind of RTT on ipv4, but ipv6 was slower. I’ll need to give it another try. The last time I did was at my last place where I had the BGW210. I have the BGW320 now and haven’t tried on that. Maybe that, or changes in their routing since then will make a difference.
deleted by creator
You’d think IPv4 would be the one that requires CGNAT not IPV6… Bizarre…
deleted by creator
What’s their rationale? Is there one?
Their network admins are old and don’t want to learn new stuff, or their networking equipment is old and they don’t want to replace it.
IPv6 existed when I was a kid. It is not even remotely new.
I know, but it wasn’t commonly used until IPv4 depletion became a more serious issue.
I must’ve said this at least 10 years ago: the more people move to IPv6, the more IPv4 are left free, so the less reason for moving to IPv6.
The “migration” could easily take several more decades.
We were talking about it when I was in undergrad.
Yeah, but for all we know you went to college thousands of years in the future, Time Lord.
That is why I think IPv6 is a non-starter. ;)
Compliance.
“Compliance with regulations.”
The same goes for my place of work. It’s going to be shit loads of fun when we are forcibly transitioned. I hope before that time I will be doing web development work and kissing my professional career in infrastructure good bye.
Yeah, my company totally blocks ipv6 when the VPN is on. Not sure why they’re so backward for a tech company.
Is there really any problem with that on the internal though?