Isn’t essentially the entire US on CG-NAT for IPv4 on mobile data?
I’ve also had DOCSIS connections, i.e., fixed lines, with only CG-NAT in Europe years ago.
Isn’t essentially the entire US on CG-NAT for IPv4 on mobile data?
I’ve also had DOCSIS connections, i.e., fixed lines, with only CG-NAT in Europe years ago.
My current endpoint lacks IPv6, so I use Cloudflare so IPv6 clients can get to it. Verizon’s IPv6 is noticeably faster than their IPv4 CG-NAT.
T-Mobile, for one, has had their handsets IPv6-only for a few years, so if your Android/iOS does a DNS lookup and gets an AAAA record back, it will skip CG-NAT. T-Mobile presenting at NANOG in 2018 on IPv6:
* https://www.youtube.com/watch?v=d6oBCYHzrTA
And Rocky Mountain IPv6 Taskforce in 2017:
* https://www.youtube.com/watch?v=nNMNglk_CvE
Further data:
> Chances are if you use the Internet on your smartphone, you are connecting via IPv6. According to the Internet Society’s 2018 State of IPv6 Deployment,[1] 80% of smartphones in the US on the major cellular network operators use IPv6 and major mobile networks are driving IPv6 adoption with Verizon Wireless at 84%, Sprint at 70%, T-Mobile USA at 93%, and AT&T Wireless at 57%. Plus, some mobile networks are taking the step to run IPv6-only to simplify network operations and reduce costs.
* https://www.arin.net/blog/2020/01/16/mobile-edge-of-the-inte...
Though some folks aren't happy with the implementation:
> But from my own experience, neither T-Mobile nor AT&T allows inbound traffic to the phone's IPv6 address. This negates some of the advantages of having a globally routable IPv6 address.
I think this has also already happened. You don't really notice it as a user, because the phone itself can act as a 4-to-6 translator (similar to how DS-Lite in DOCSIS transports CG-NATted v4 traffic in v6) for both native apps doing incompatible things with literal v4 addresses and tethering clients.
Basically only one single ISP don't use CGNAT...
Would be interesting if Cloudflare could give this info!