We're Sorry, Full Content Access is for Members Only...

If you like to keep on reading, Become a Member Now! Here is why:

  • Learn any CCNA, CCNP and CCIE R&S Topic. Explained As Simple As Possible.
  • Try for Just $1. The Best Dollar You've Ever Spent on Your Cisco Career!
  • Full Access to our 644 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

497 Sign Ups in the last 30 days

satisfaction-guaranteed
100% Satisfaction Guaranteed!
You may cancel your monthly membership at any time.
No Questions Asked!

Tags:


Forum Replies

  1. Hi Rene,

    I’m trying to configure nat64 but apparently the ios I’m using does not recognize these commands. just to confirm it is it because of the IOS version or do i need to enable anything?

    the ios i’m using is : BOOTLDR: 7200 Software (C7200-ADVIPSERVICESK9-M), Version 15.1(4)M5,

  2. Hi Rene, correction:

    R2(config)#interface GigabitEthernet 2

    your diagram shows FastEhternet interfaces but in the configuration you are saying GigabitEthernet.

  3. There is very limited support for NAT64 on cisco devices. As far as I can tell it is limited to Cisco IOS XE Release 3.5S or better.
    So you certainly can’t run this on GNS3.

    I think that NAT64 is not actually very useful outside of a LAB. In practice you need DNS entries for both the real and mapped addresses which is more of a pain than running dual stack.

    Stuart.

  4. Hello Stuart

    For the most part you are correct that NAT64 has a limited usage in real world applications. However, there are cases where it is necessary. Also, it is supported by Cisco IOS-XE 15.1(3)S4 as well as Cisco ASA 9.1 and later.

    Running two protocols in parallel always requires more management overhead, and if it can be avoided at all, it is good to do so. Unfortunately, it’s not always possible.

    I hope this has been helpful!

    Laz

  5. Hello sales2161

    Well, it all depends on your point of view. :stuck_out_tongue:

    When we talk about NAT in IPv4, we traditionally talk about “real” and “fake”, public and private, routeable and non-routable addresses because we are translating for the purpose of conserving addresses. So there is a meaning to these terms. However, NAT in a more general sense is a translation from one IP address range to another, regardless of whether the addresses are private, public, routable or not. You could translate from 10.10.10.0/24 to 172.16.0.0/24 for example. In such a case, which is

    ... Continue reading in our forum

18 more replies! Ask a question or join the discussion by visiting our Community Forum