Technical data
34 ServerIron ADX NAT64 Configuration Guide
53-1002288-02
Configuring NAT64 for IPv4-only client to IPv6 resource
3
DRAFT: BROCADE CONFIDENTIAL
IPv4-only client to IPv6 resource sample configuration
The example in Figure 12 is a NAT46 configuration that uses the DNS Dynamic Learning method to
populate its translation map.
FIGURE 12 NAT64 stateless example
The following commands are required on a ServerIron ADX to enable the NAT46 stateless
configuration shown in Figure 12.
ServerIron ADX(config) nat64 dns-dynamic-learning
ServerIron ADX(config) nat64 ipv4-prefix 100.1.1.0/24
ServerIron ADX(config) nat64 ipv6-prefix 2001:db8:: stateless
ServerIron ADX(config) ip dns 192.168.13.50
ServerIron ADX(config-if-1000-6) ip address 192.168.13.12
ServerIron ADX(config-if-1000-6) ipv6 address 2001:db8:ddd.1
Configuration Options:
The following options can be added to your configuration as described.
Avoiding IPv6-side fragmentation
To avoid generation of fragments due to increased IP header size with IPv6 when IPv4 sends a
full-sized packet (1500 bytes), increase the global IP MTU or the MTU on the IPv6 side interface. If
this is not configured, a full-sized IPv4 packet will generate two IPv6 fragments.
Global MTU Configuration
ServerIron ADX(config) ip global-mtu 1520
IPv6-side MTU Configuration
ServerIron ADX(config) interface ve 10
IPv6
ServerIron ADX
with NAT46
DNS 64 Server
IPv4-only Client
IPv4
IPv6 + IPv4
NAT64 IPv6 Prex: 2001:db8::
NAT64 IPv4 Prex: 100.1.1.0/24
IPv6 address:
2001:dba:f.5e
IPv6-only Server
IPv4 address:
192.0.2.1
IPv6 address: 2001:db8:ddd:1
IPv4 address: 192.168.13.12
IPv4 address:
192.168.13.50