briffle a year ago

yes, with the increased latency of having to travel to the NAT64 server first. This can also cause you to not use the nearest CDN, etc.

  • bigfatkitten a year ago

    The NAT64 server for those users is in the same place the CGNAT used to be.

orangeboats a year ago

There are already cases of Internet connectivity issues due to overloaded CGNAT. I know for a while I could only visit IPv6 websites, IPv4 technically works but the amount of packet drops meant that my IPv4 internet speed was only about 15KB/s!

It's the whole reason why I discovered a DNS server that synthesizes AAAA records, for websites that actually support IPv6 through their CDN. [0]

> As you said though, those users can reach v4 websites.

Therefore, the question is: Can those users really reach IPv4 websites?

Mind you, I don't expect the CGNAT-overloading issue to relieve over time -- unless we deploy IPv6 everywhere ;)

[0]: https://gitlab.com/miyurusankalpa/IPv6-dns-server

electronbeam a year ago

Its easier to get good latency and bandwidth over v6 than natted v4

  • commandersaki a year ago

    What is the latency or bandwidth bottleneck in nat v4?

    • namibj a year ago

      Taking the detour to the NAT.

      • commandersaki a year ago

        NAT registers in the microseconds for packet processing time, that isn’t even comparable to Internet path jitter.

      • mort96 a year ago

        You mean that the packets go through a router? They would do that regardless though?