Technical data

4 ServerIron ADX NAT64 Configuration Guide
53-1002288-02
Implementation Details
1
DRAFT: BROCADE CONFIDENTIAL
NAT46 gateway
The NAT46 gateway receives the IPv4 packets whose Destination IPv4 address is mapped to an
internal IPv6 resource. It then translates the IPv6 address to an IPv4 address used by the resource.
Return packets from the IPv6 resource are then mapped back to the clients IPv4 address. NAT46 is
stateless, meaning that the NAT64 device does not keep track of the connections between the IPv4
client and the IPv6 resource.
Protocol support
The Brocade implementation of NAT64 supports the following protocols:
• Generic TCP
• Generic UDP
• HTTP
• HTTPS
• ICMP
• RDP
NAT64 ICMPv6 to ICMPv4 message handling
NAT64 ICMP packet handling allows ICMPv6 messages to be translated to corresponding ICMPv4
messages on the IPv4 side and IMCPv4 messages from the IPv4 side to be translated to
corresponding ICMPv6 messages on the IPv6 side. Table 1 and Table 2 describe these translations.
TABLE 1 ICMPv6 to ICMPv4 message translation
ICMPv6 Message Type ICMPv4 Message Type
Destination Unreachable ( Type 1)
• no route (code 0)
• admin prohibited (code 1)
• not neighbor (code 2)
• address unreachable (code 3)
• port unreachable (code 4)
Destination Unreachable (Type 3)
• Host Unreachable (code 1)
• admin prohibited (code 10)
• route fail (code 5)
• host unreachable (code 1)
• port unreachable (code 3)
Packet Too Big (Type 2) Destination Unreachable (Type 3)
• fragment needed (code 4)
Time Exceeded (Type 3) Time exceeded (Type 11)
• code remains same from ICMP6
Parameter Problem (Type 4)
• next header
• any other param prob
Type - Dest Unreachable, code - protocol
unreachable
Type - param prob, code - 0
Echo request (Type 128) Echo request (Type 8)
Echo Reply (Type 129) Echo Reply (Type 0)