Technical data

32 ServerIron ADX NAT64 Configuration Guide
53-1002444-02
Stateless NAT64 static mapping configuration
3
DRAFT: BROCADE CONFIDENTIAL
Stateless NAT64 static mapping with route injection
Route injection can be used to make the addresses assigned to IPv4 and IPv6 translations
available as destinations in the routing tables of the respective IPv4 and IPv6 networks. Once these
routes are injected into the respective routing tables, route distribution is then performed using any
one of the routing protocols supported by ServerIron ADX: OSPF, IS-IS, and BGP (IPv6 to IPv4).
NAT64 route injection requires that the ServerIron ADX have a routing adjacency relationship with a
router for the protocols with which you support route distribution.
• IPv4 route injection: For resources that are mapped to an IPv4 address, the IPv4 subnet is
defined by the IPv4 prefix specified with the nat64 ipv4-prefix command. This command has
the inject-static-route option which directs the ServerIron ADX to inject a static route to each of
the IPv4 addresses within the defined IPv4 subnet that have an IPv6 address mapped to them.
This mapping can be either performed using DNS dynamic mapping or though creation of a
static entry using the nat64 map command. This destination is advertised to the adjacent
neighbor and made available in routing tables of the IPv4 network.
• 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.
Figure 10 shows a typical IPv6-only client to IPv4 resource topology configured with router
adjacency relationships on both the IPv6 and IPv4 sides of the NAT64 gateway. In this
configuration, routes defined by the IPv6 prefix and IPv4 prefix are advertised to the adjacent
routers and distributed to the respective networks using the routing protocol configured.
FIGURE 10 Stateless NAT64 route injection
.
To accomplish this redistribution, you must configure the routing protocol on your ServerIron ADX
with the redistribute static command.
NOTE
For details about how to configure routing protocols on a ServerIron ADX, refer to the following
chapters in the ServerIron ADX Switch and Router Guide: “Configuring OSPF”, “Configuring IPv6
Dynamic Routing”, “Configuring IS-IS (IPv4)”, “Configuring IPv6 IS-IS”, “Configuring BGP4 (IPv4)”,
and “Configuring BGP4+”.
NAT64 GatewayIPv6 Client
IPv4
IPv6 Prefix: 2001:db8:8000::/96
IPv4 Prefix: 200.1.1.0/24
IPv6 address:
2001:db8:100::cccc
IPv4 Server
IPv4 address:
200.1.1.100