Technology

37353 readers

293 users here now

Rumors, happenings, and innovations in the technology sphere. If it's technological news or discussion of technology, it probably belongs here.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

[email protected]

153

AWS: IPv4 addresses cost too much, so you’re going to pay (www.theregister.com)

submitted 11 months ago by [email protected] to c/[email protected]

75 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 5 points 11 months ago (1 children)

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.

[–] [email protected] 3 points 11 months ago* (last edited 11 months ago) (1 children)

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.

[–] [email protected] 2 points 11 months ago

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.