What is NAT and NAT64?
What is NAT and NAT64?
Product and Release Support Network Address Translation (NAT) is a mechanism for concealing a set of host addresses on a private network behind a pool of public addresses. NAT64 is a related technology that allows IPv6-only clients to contact IPv4 servers using Unicast UDP, TCP, or ICMP.
How does NAT64 work?
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 creates a mapping between the IPv6 and the IPv4 addresses, which may be manually configured or determined automatically. …
What are limitations of stateful NAT64?
The following limitations apply to stateful NAT64:
- Translation of IPv4 options is not supported.
- Translation of IPv6 routing headers is not supported.
- Translation of hop-by-hop extension headers of IPv6 packets is not supported.
- Translation of ESP and EH headers of IPv6 packets is not supported.
How to configure NAT64?
To configure the NAT64 pool:
- Configure an IPv4 transport address for the pool at the [edit services nat pool pool-name ] hierarchy level. Configure the NAT pool port to be automatically assigned.
- Configure a NAT rule to translate the packets from the IPv6 network.
Can you Nat IPv6 to IPv4?
IPv4-Mapped Operation. You can send traffic from your IPv6 network to an IPv4 network without configuring the IPv6 destination address mapping. A packet that arrives at an interface is checked to discover if it has a NAT-PT prefix that was configured with the ipv6 nat prefix v4-mapped command.
Why IPv4 IP address assignment is a stateful configuration?
Stateful NAT64 translates the packets and forwards them as IPv4 packets through the IPv4 network. The process is reversed for traffic that is generated by hosts connected to the IPv4 network and destined for an IPv6 receiver.
How do you configure NAT64 on Palo Alto firewalls IPv6 to IPv4 translation?
Steps
- Bind 9 was used as the DNS64 server for this setup. The following configuration needs to be added to the /etc/bind/named.
- Assign the 64:ff9b::/96 network to the interface assigned to ‘Untrust’ zone.
- Configure the NAT64 rule as follows:
- On the client, open a browser and try to navigate to a website.
Why is IPv6 not used?
Adoption of IPv6 has been delayed in part due to network address translation (NAT), which takes private IP addresses and turns them into public IP addresses.
How does stateful NAT64 translate IPv6 address?
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.
What are the components of a stateful NAT64 configuration?
A stateful NAT64 configuration on the Citrix ADC appliance has the following components: NAT64 rule — An entry consisting of an ACL6 rule and a netprofile, which consists of a pool of Citrix ADC owned SNIP Addresses. NAT64 IPv6 Prefix — A global IPv6 prefix of length 96 bits (128-32=96) configured on the appliance.
When to use the WKP prefix in stateful NAT64?
During a stateful translation, if no stateful prefix is configured (either on the interface or globally), the WKP prefix is used to translate the IPv4 host addresses. The packet flow of IPv4-initiated packets for Stateful NAT64 is as follows:
What does stateful NAT64 mean in Citrix ADC?
The stateful NAT64 feature enables communication between IPv6 clients and IPv4 servers through IPv6 to IPv4 packet translation, and vice versa, while maintaining session information on the Citrix ADC appliance. A stateful NAT64 configuration on the Citrix ADC appliance has the following components: