Hacker News new | ask | show | jobs
by tcoff91 1581 days ago
NAT64 and DNS64 are not the same thing as 464XLAT.

It's been a number of years since I had to work on this at a previous company, but my recollection is that Android relies 464XLAT to make sure that all android apps will work properly on ipv6-only mobile networks that use carrier grade NAT.

Apple on the other hand demands that your app actually natively works with ipv6. I didn't have access to an ipv6 network when I was working on solving this issue in our networking libraries, so I used this https://www.jool.mx/en/ to set up NAT64 and I used bind9 to do DNS64 in order to create an ipv6 network for testing ipv6 functionality.
1 comments
cmeacham98 1581 days ago
> NAT64 and DNS64 are not the same thing as 464XLAT.

Correct, that's my point. What my parent poster is describing is 464XLAT, not DNS64 and/or NAT64.

link
detaro 1581 days ago
No, the iOS requirement is for DNS64/NAT64. The server can be IPv4, the app has to work with an IPv6 address provided by DNS64. If 464XLAT were the deployed, the app could continue to speak IPv4, but it can't. Nothing to poster you replied to said contradicted that, so I'm not sure where you got it from that they speak about 464XLAT?
link
cmeacham98 1580 days ago
Maybe I misinterpreted the original poster's comment, my understanding was they were referring to IPv6-only carrier networks.

In the US (unsure about other countries but they may work the same), the IPv6-only carrier networks mostly (all?) use 464XLAT and not DNS64.

My comments are intentionally devoid of talking about what Apple's requirements are because I don't know then and as far as I know the other posters are correct there.

link