News for hackers. Stuff that matters.
Re:AWS to start charging for IPv4 usage, but critical servic... by ramshanker on Friday November 10, 2023 @11:43AM (#38221034)
One day will come, when network admins will be so happy to finally turn off IPv4 on their stack. When router manufacturers will feel happy to support only IPv6. It is definitely coming within my lifetime.

So, these intermediate steps are just cooking the final dish.

Peace. ;)

Re:AWS to start charging for IPv4 usage, but critical servic... by flumpcakes on Friday November 10, 2023 @11:53AM (#38221165)
I don't think that will ever happen... Too many big businesses squatting on their IPv4 allocations to ever want to spend the money to implement IPv6. They don't need to worry about allocation running out or charging for IPs because they've got theirs.

They would need to be forced to move by customers, probably through an ISP being IPv6 only. And that probably won't ever happen as the customers of those ISPs would drop them for one that does support IPv4 because they expect access to the same big businesses mentioned earlier.

I think the whole thing has lots of inertia to not move to IPv6 and there's no incentive to force it.

Re:AWS to start charging for IPv4 usage, but critical servic... by _trampeltier on Friday November 10, 2023 @12:02PM (#38221309)
Not just that, there are other networks too on IPv4. In industry automation, IPv6 is no thing at all yet.
Re:AWS to start charging for IPv4 usage, but critical servic... by SamuelAdams on Friday November 10, 2023 @12:33PM (#38221763)
Once GitHub works with ipv6 I’ll start to take it seriously.
Re:AWS to start charging for IPv4 usage, but critical servic... by blueflow on Friday November 10, 2023 @01:19PM (#38222441)
Once my IPv6 worked i stopped taking GitHub seriously.
Re:AWS to start charging for IPv4 usage, but critical servic... by Aerbil313 on Sunday November 12, 2023 @09:27AM (#38240320)
Once my IPv6 works I’ll start taking IPv6 seriously.

Shame on you Turk Telekom and Turkcell. Still don’t support IPv6.

Re:AWS to start charging for IPv4 usage, but critical servic... by throw555chip on Friday November 10, 2023 @01:57PM (#38222938)
IPv6 is a privacy nightmare, no privacy technology designed to fix IPv6, fixes it.
Re:AWS to start charging for IPv4 usage, but critical servic... by jjjjmoney on Friday November 10, 2023 @01:57PM (#38222945)
How is it any worse than IPv4?
Re:AWS to start charging for IPv4 usage, but critical servic... by TheNewsIsHere on Saturday November 11, 2023 @09:45AM (#38230711)
I can’t know for sure what the parent comment was alluding to, but I would assume the idea is that because IPv6 isn’t built around an assumption of NAT, that it’s less private because you don’t have an intermediary router (potentially) concealing traffic origins as a network design feature.

That’s the only thing about IPv6 that I’ve heard of that I think is a reasonable argument regarding a degradation in privacy.

With that said, NAT was a fix for issues that weren’t about privacy, and NAT itself was not designed to give you privacy. It used to be that IPv4 connections were always direct in the same way IPv6 connections were designed to be direct.

In that regard you could make the argument that IPv6 is a regression, but that regression is effectively answering for an architectural shortcoming in IPv4 that we’ve tried hard to fix but that can only go so far.

Edit to add: NAT also doesn’t protect anyone’s privacy anymore than their ISP is willing to protect it anyway, for what it’s worth.