Technical data

ServerIron ADX NAT64 Configuration Guide 37
53-1002288-02
Configuring Packet fragmentation with IPv4-only client to IPv6 resource
3
DRAFT: BROCADE CONFIDENTIAL
For a description of NAT64 route injection see “Route injection NAT46” on page 35.
FIGURE 14 NAT64 route injection example
ServerIron ADX(config)# vlan 1
ServerIron ADX(config-vlan-1)# interface ethernet 1 to 2
ServerIron ADX(config-vlan-1)# interface ve 7
ServerIron ADX(config-vlan-1)# exit
ServerIron ADX(config)# interface ve 7
ServerIron ADX(config-vif-7)# ipv6 address 2001:db8:8000::1
ServerIron ADX(config-vif-7)# exit
ServerIron ADX(config)# router ospf
ServerIron ADX(config-ospf-router)# redistribute static
ServerIron ADX(config-ospf-router)# area 0
ServerIron ADX(config-ospf-router)# exit
ServerIron ADX(config)# ipv6 router ospf
ServerIron ADX(config-ospf6-router)# redistribute static
ServerIron ADX(config-ospf6-router)# area 1
ServerIron ADX(config-ospf6-router)# exit
ServerIron ADX(config)# nat64 ipv4 prefix 100.1.1.0/24 inject-static-route
ServerIron ADX(config)# nat64 ipv6-prefix 2001:db8:8000::0/96 inject-static-route
ve 7 stateless
ServerIron ADX(config)# nat64 map 100.1.1.100 2001:db8:8000::100
NOTE
While this example describes NAT46 route injection for the OSPF protocol, you can also use this
feature with BGP and IS-IS. Only the routing protocol configurations will differ.
Configuring Packet fragmentation with IPv4-only client to IPv6
resource
Packets from the IPv4 client to the IPv6 server can be too large and need to be split into two IPv6
packets. The following describes the criteria for judging that packets are too large:
Regular packets – IP total length greater than 1480 bytes
Fragmented packets – IP total length greater than 1480 + 8 bytes
Upstream IPv4
Router
IPv4
Downstream IPv6
Router
IPv4-only Client
ServerIron ADX
with NAT64
NAT64 IPv6 Prex:
2001:db8:8000::0/96
NAT64 IPv4 Prex
100.1.1.0/24
IPv6-only Server
port 1
port 2
port 3
OSPF Area 0
OSPF Area 1