Technical data

ServerIron ADX NAT64 Configuration Guide 11

53-1002444-02

Advanced stateful NAT64 configuration

DRAFT: BROCADE CONFIDENTIAL

NOTE

If the ServerIron ADX runs out of stateful NAT64 NAT pool ports or session entries, new connection

requests are dropped silently.

NOTE

You must reload the ServerIron ADX whenever the IPv4 NAT address pool configuration is changed.

Advanced stateful NAT64 configuration

An advanced stateful NAT64 configuration includes one or more optional features in addition to the

basic configurations.

The steps used for advanced stateful NAT64 configuration include the following:

• “Configuring stateful NAT64 with route injection” on page 11

• “NAT64 sticky session configuration” on page 15

• “Enabling connection logging” on page 16

• “Configuring HTTP client IP address insertion” on page 16

• “Configuring NAT64 packet fragmentation options” on page 17

Configuring stateful NAT64 with route injection

The NAT64 gateway uses route injection to advertise IPv6 and IPv4 address translations to the

appropriate networks. Using static route injection, you can make these translations available as

destinations in the routing tables of the IPv6 and IPv4 networks in which they reside. Route

distribution is then performed using any of the routing protocols supported by the ServerIron ADX:

OSPF, IS-IS, and BGP (IPv4 and IPv6).

• Synthesized NAT64 IPv6 addresses that represent IPv4-only resources to the IPv6 network can

be injected into the routing table for the IPv6 network.

• IPv4 addresses (selected from the IPv4 NAT address pool) that represent IPv6 clients to the

IPv4 network can be injected into the routing table for the IPv4 network.

NAT64 route injection requires that the ServerIron ADX have a routing adjacency relationship with a

router for the protocols for which you want to support route distribution.

• For the IPv4 NAT address pool, the nat64 pool command has the inject-static-route option

which injects a route to the subnet into the local routing table. This route is then advertised as

the destination for traffic bound for the subnet by the routing protocol that is configured on the

ServerIron ADX.

• Starting with ServerIron ADX release 12.4.00, configuring the inject-static-route option with the

nat64 ipv6-prefix command allows the configured IPv6 routing protocol to advertise the subnet

defined by the IPv6 prefix to the adjacent IPv6 neighbor and thereby make it available in the

routing tables of the IPv6 network, The next hop to the subnet is advertised to the IPv6 network

as the adjacent router. In all prior releases of the ServerIron ADX, you are required specify an

IPv6 interface on the ServerIron ADX (Ethernet or VE) that is directly connected to the adjacent

router.