5 ms·
An Introduction to NAT64
- slindsey 6y agoSuch a pet peeve of mine. Define it, at least on the page. From wikipedia. > NAT64 is an IPv6 transition mechanism that facilitates communication between IPv6 and IPv4 hosts by using a form of network address translation (NAT). The NAT64 gateway is a translator between IPv4 and IPv6 protocols, for which function it needs at least one IPv4 address and an IPv6 network segment comprising a 32-bit address space.
- zamadatix 6y agoIt's a follow up to the second part and covered in the first minute of the video as review anyways.
- andrewshadura 6y agoFun fact: I wrote the initial version of that page. I taught networking lessons at a university, IPv6 transition mechanisms were one of the topics we covered, and this one didn't have an article, so I wrote it. It was quite funny when one of the students realised it was who wrote it when they went to Wikipedia wanting to learn more :)
- kgersen 6y agosound is too low.
- telmich 6y agothanks for the feedback, I'll tune the sound quality for the next episode
- xmichael0 6y agoI see no reason to use NAT64 over NAT. Am I wrong here?
- mrkurt 6y agoThey're different things. NAT64 is useful for bridging between ipv6 and ipv4 networks, it's just a way of encoding ipv4 addresses in ipv6 addresses. It's more straightforward than ipv4 nat because there's no port rewriting.
- MayeulC 6y agoNAT64 is useful to allow IPv4 services to work in an IPv6-only environment. It's nice to only have one stack to administrate, and IPv6 is generally more flexible, but you often need to fall back to IPv4. NAT64 is more and more used instead of CGNAT (well, it's still CGNAT to an extent), but I don't really see one being advantageous over the other. Only that there are only IPv6 semantics when using NAT64, so stuff like roaming, privacy extensions, etc. works, and you don't have to rely on dual-stack. I think the big advantage to NAT64 is identifying the pain points (incompatible equipment, applications, etc) in an IPv6-only world. And it really is a clear transition path to IPv6.
- xmichael0 6y agoThank you for your comprehensive and thoughtful answer. I agree with everything you said, except for the idea that we are transitioning, we will always live in a hybrid ipv4 ipv6 world (;
- andrewshadura 6y agoBack in the day I wrote tnat64, a simple tsocks-like wrapper to redirect IPv4-only applications to a NAT64 gateway. It even worked with Skype to a degree: it'd log in and then repeatedly reconnect every minute or so.
- fmitga 6y agoOooh, I actually have a use for this. Any interest in open sourcing it?
- andrewshadura 6y agoIt has been open source since the very beginning: https://github.com/andrewshadura/tnat64 https://github.com/andrewshadura/tnat64 https://tracker.debian.org/pkg/tnat64 https://tracker.debian.org/pkg/tnat64
- moonbug 6y agoTypically paired with 464xlat in an IPv6-only environment, for programs that are hard-coded for IPv4. An excellent `just-works` example is https://github.com/toreanderson/clatd https://github.com/toreanderson/clatd
- sigio 6y agoAnother video on NAT64 by ungleich: https://www.youtube.com/watch?v=IoYKNE4kSrA https://www.youtube.com/watch?v=IoYKNE4kSrA on their implementation using p4