> Date: Thu, 03 Feb 2011 13:33:33 +0000 > From: Phil Mayers <[email protected]> > Sender: [email protected] > > On 02/02/11 19:50, Vlad Ion wrote: > > hmm... so NAT64 supported just in 10.4 not in 10.3 as well? > > > > @ Phil - I can tell you how well both NAT-PT and NAT64 will work on J-series > > in about a month when I will be done testing them... even tho it doesn't > > match exactly the profile of M7i > > Interesting; I didn't realise the low-end devices also supported NAT-PT. > We have some J-series on support. > > What's the basic config syntax? I have just spent an hour looking at the > awful Juniper documentation, and can't decipher it.
Just to make things clear as mud, NAT64 is a mechanism that does address and protocol translation or NAT-PT, but it is probably best not to call it that as "NAT-PT" was an old technique that was defined in an RFC and was officially abandoned by the IETF. NAT64 is an externally similar technique that is based on a new I-D and internally very different from the old NAT-PT. It might even work. It was used at Internet2 Joint Techs this week using a Juniper router, and it generally worked. The only real issue was web pages with embedded literal IPv4 addresses. NAT64 can't properly deal with these. It was vastly easier to use and to set up than NAT-PT or other techniques we have tried in the past. Everyone confused, now? If so, my work here is done. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [email protected] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
