this post was submitted on 31 Jul 2023
122 points (100.0% liked)

Technology

37603 readers
526 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

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
 

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.

all 33 comments
sorted by: hot top controversial new old
[–] flip@lemmy.nbsp.one 94 points 1 year ago (1 children)

Hopefully this will push IPv6 adoption further. It is a clusterfuck how long IPv6 exists and how often one has to still fall back to IPv4.

[–] housepanther@lemmy.goblackcat.com 19 points 1 year ago (2 children)

This is my thought. It's about time greater adoption of IPv6 happens. As much as I don't like corporations getting greedier, in this case however, Amazon is doing us a favor by spurring IPv6 adoption on.

[–] dan@upvote.au 14 points 1 year ago* (last edited 1 year ago) (2 children)

IPv6 is already relatively widespread in the USA (and many other countries) on the client-side, especially on mobile networks.

  • T-Mobile's network is almost entirely IPv6-only, using 464XLAT for connectivity to legacy IPv4-only servers.
  • The majority of traffic to Facebook (around 62%) is via IPv6. https://www.facebook.com/ipv6
  • As of June 2022, 73% of Comcast and 72% of AT&T customers had IPv6 connectivity. https://www.worldipv6launch.org/measurements/
  • People that play online games often try to use IPv6 to avoid NAT, as it reduces latency.

The main issue is that a lot of sites aren't available over IPv6. Hopefully Amazon helps push that along.

[–] housepanther@lemmy.goblackcat.com 7 points 1 year ago (1 children)

I have IPv6 connectivity through Verizon FiOS. The trouble is that in my area it is poorly implemented and markedly slower than IPv4. I would much rather use 6 but not at a performance penalty.

[–] dan@upvote.au 5 points 1 year ago* (last edited 1 year ago) (1 children)

Ahh, that sucks. Sorry to hear. A proper IPv6 network should be faster than IPv4, since there's no NAT and no complex routing rules.

Agreed! Also smaller packet sizes.

[–] magnus@lemmy.ahall.se 5 points 1 year ago* (last edited 1 year ago) (1 children)

In Sweden we have just one ISP for non-commercial customers providing native IPv6 adresses (Bahnhof) on fiber connections, and even then we can't get a static prefix from them.

Not quite sure on the mobile ISPs though.

[–] LaggyKar@programming.dev 2 points 1 year ago (1 children)

At least Tele2 supports IPv6 on mobile, not sure about others

[–] magnus@lemmy.ahall.se 1 points 1 year ago* (last edited 1 year ago)

I guess that means able to access services on the Internet over IPv6, not me being able to get a /64 and providing services myself to others.

Sort of ok for phones I guess, although not as great if someone doesn't have access to fiber and have to use a mobile link in a residential environment.

Bahnhof actually just provides NAT:ed fiber connections as well as default, but will issue a public, unique IP if asked (at no additional cost).

[–] r00ty@kbin.life 6 points 1 year ago

I suspect greed is involved. But since the new allocation of ipv4 hasn't been possible for quite some time in US and Europe. I think the price of those IPs that are assigned to providers is going to gradually rise.

And to think, I remember when I got a business ISDN account for my old office. They pretty much just gave you a free (well included in the price) /24 without even asking.

Different times.

[–] TheRealMalc@beehaw.org 18 points 1 year ago (2 children)

About 3.70/month. Not great, not terrible

[–] shanghaibebop@beehaw.org 1 points 1 year ago

But that’s as high as the meter…..

[–] jmanes@beehaw.org 17 points 1 year ago

Thank goodness. Death to IPv4.

[–] csolisr@communities.azkware.net 16 points 1 year ago (1 children)

My ISP is still incapable of resolving IPv6 addresses at all. Same goes for several other ISPs in my country that I have tried before that. As of now I need to rent a separate VPS just to have my home server be visible online on a public IPv4 address, and that is with a heavy bandwidth penalization. Can't wait for IPv6 to be generally available in my country at least!

[–] ox0r@jlai.lu 12 points 1 year ago (1 children)

"We want more money so fuck you"

[–] cnqr@beehaw.org 1 points 1 year ago

That’s not the Amazon approach. Amazon tries to make money on the volume, not on the margins.

IPv4 is starting to actually cost. To everyone.

[–] dandroid@dandroid.app 8 points 1 year ago (2 children)

If my ISP doesn't support IPv6, would I need a proxy or something to access an AWS instance with only an IPv6 address?

[–] r00ty@kbin.life 7 points 1 year ago

A tunnel. I've used these before https://tunnelbroker.net/ and https://www.sixxs.net/main/ probably 10 years ago now. They were pretty good. But of course you need something to act as a router on your network for it to set it up for the whole network. A raspberry pi would be enough or anything running linux. Of course you can probably just set it up on one machine too. I've never done that though.

You could use an IPv6 tunnel broker service. I know Hurricane Electric offers a service free of charge. I use it and it's not bad. Hurricane Electric also has an IPv6 tutorial. See (https://www.he.net)

[–] sammydee@readit.buzz 4 points 1 year ago
[–] NENathaniel@lemmy.ca 1 points 1 year ago

Can anyone explain why migration to IPv6 has been so slow? Just too cheap/lazy to migrate or does it break things or what?