3 ms·
Interesting... What were the errors and what was the workaround? Do they have some sort of 6to4 router that wasn't working?
by russellbeattie 9y ago
Interesting... What were the errors and what was the workaround? Do they have some sort of 6to4 router that wasn't working?
- andrewf 9y agoThat'd be an interesting take on Carrier-grade NAT. The approach I'm familiar gives phones a non-routable IPv4 address to get to the carrier's NAT gateway, but I can imagine shenanigans with some combination of 6to4, phone settings and/or DNS. Anyone seen such a setup in the wild? I'm interested in the errors OP saw.. was it just niche non-HTTP(S) access which broke, or all websites without an AAAA record?
- zokier 9y agoHave you seen 464XLAT?
- cesarb 9y agoIf the errors were "from some, but not all, apps", my first guess would be that these particular apps either don't understand IPv6 addresses, or ask the DNS only for IPv4 addresses. Both causes would stop NAT64/DNS64 or similar from working. The other apps which kept working probably can use IPv6 just fine, even if their servers are IPv4-only. The "workaround for him" was probably adding him back to the CGNAT, so that the outdated apps could see and use an IPv4 address. That kind of workaround won't be there forever; if they're starting to move phones to IPv6-only (with NAT64/DNS64 or similar), they are probably planning to turn off the CGNAT sooner or later.