Drag and Drop

Drag and Drop
Drag and drop the steps in the NAT process for IPv4-initiated packers from the left into the correct sequence on the right.
Select and Place:


cisco-exams

One thought on “Drag and Drop

  1. The question is to class step by step how a packet that arrives, this is what I am thinking about:
    This classification on the answer corresponds to what I said.
    So read this and you will understand it:

    The packet flow of IPv4-initiated packets for Stateful NAT64 is as follows:

    The destination address is routed to a NAT Virtual Interface (NVI).

    A virtual interface is created when Stateful NAT64 is configured. For Stateful NAT64 translation to work, all packets must get routed to the NVI. When you configure an address pool, a route is automatically added to all IPv4 addresses in the pool. This route automatically points to the NVI.

    The IPv4-initiated packet hits static or dynamic binding.

    Dynamic address bindings are created by the Stateful NAT64 translator when you configure dynamic Stateful NAT64. A binding is dynamically created between an IPv6 and an IPv4 address pool. Dynamic binding is triggered by the IPv6-to-IPv4 traffic and the address is dynamically allocated. Based on your configuration, you can have static or dynamic binding.

    The IPv4-initiated packet is protocol-translated and the destination IP address of the packet is set to IPv6 based on static or dynamic binding. The Stateful NAT64 translator translates the source IP address to IPv6 by using the Stateful NAT64 prefix (if a stateful prefix is configured) or the Well Known Prefix (WKP) (if a stateful prefix is not configured).

    A session is created based on the translation information.

    All subsequent IPv4-initiated packets are translated based on the previously created session.

Leave a Reply

Your email address will not be published. Required fields are marked *


The reCAPTCHA verification period has expired. Please reload the page.