AWS to start charging for IPv4 usage, but critical services don't support IPv6

Re:AWS to start charging for IPv4 usage, but critical servic... by hristov on Friday November 10, 2023 @12:47PM (#38221979)

I remember having to do a lot of port forwarding to get certain things to work behind a nat. Certainly doable but beyond the competence of a non-expert.

[ Parent | on HN ]

Re:AWS to start charging for IPv4 usage, but critical servic... by supriyo-biswas on Friday November 10, 2023 @12:50PM (#38222017)

And that's entirely out of your control if your ISP is doing the NATing.

[ Parent | on HN ]

Re:AWS to start charging for IPv4 usage, but critical servic... by jjjjmoney on Friday November 10, 2023 @12:52PM (#38222041)

Not even your ISP - it could be university, business, shared internet for apartments, etc.

[ Parent | on HN ]

Re:AWS to start charging for IPv4 usage, but critical servic... by saltminer on Friday November 10, 2023 @01:51PM (#38222861)

And sometimes, entire nations. Qatar used to share a single IPv4 address, which I found out when news articles started reporting that the entire country could no longer edit Wikipedia without an account, which at the time, was also restricted if your IP was banned from anonymous edits. If you didn't create an account prior to the ban, you were completely blocked from editing.

https://en.wikipedia.org/wiki/User:82.148.97.69

https://techcrunch.com/2007/01/01/wikipedia-bans-qatar/

[ Parent | on HN ]

Re:AWS to start charging for IPv4 usage, but critical servic... by jjjjmoney on Friday November 10, 2023 @12:56PM (#38222113)

This isn't entirely about static port-forwarding. As others have pointed out, STUN, VoIP, PASV, etc rely on deterministic NAT behavior to work. That is not always guaranteed, and often out of your control.

[ Parent | on HN ]