[c-nsp] OT: NAT64 kills what protocols?

TJ trejrco at gmail.com
Tue Jan 27 17:32:37 EST 2015

I haven't tried it to prove this, or bothered to look (to be honest) but I
didn't recall TFTP acting that "poorly behanved" way like (original/active)
FTP does.  Regardless, it seems to me like that entire class of problem
would be a relatively easy "application layer gateway" fix ...

FWLIW, I know the only real example from switching my (Android) phone to
IPv6-only was that Skype broke ... until 464XLAT support was enabled (now
included by default, so even that is all good!).


On Tue Jan 27 2015 at 5:20:20 PM Scott Voll <svoll.voip at gmail.com> wrote:

> OK I "think I know" that NAT64 kills TFTP because the ipv4 address is in
> bedded in the body of the packet.
> What other protocols will not go through a NAT64 translation?
> in wireshark, how do I see an IP in the body of the packet?  I have a
> couple other applications that are having issues so I'm trying to figure
> out why.
> Thanks
> scott
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/

More information about the cisco-nsp mailing list