Technical data

ServerIron ADX NAT64 Configuration Guide 15
53-1002288-02
HTTP client IP address insertion
2
DRAFT: BROCADE CONFIDENTIAL
FIGURE 7 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:7000::1/64
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 pool nat64-zone1 192.0.2.1 192.0.2.10 prefix-length
24 port-pool-range 1 inject-static-route
ServerIron ADX(config)# nat64 ipv6-prefix 2001:db8:8000::0/96 inject-static-route
ve 7
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.
HTTP client IP address insertion
When IP addresses are translated, the resource will not be able to get the original client IP address.
If client IP address insertion is enabled, the client IP address will be inserted as an HTTP header.
The header will be inserted as the last header in the HTTP request.
For example, where the original HTTP request is:
GET /abc/index.html HTTP 1/0\r\n
Host: foo.com\r\n
…
Connection: Keep-Alive\r\n
\r\n
Upstream IPv6
Router
Downstream IPV4
Router
IPv6-only Client
ServerIron ADX
with NAT64
NAT64 Prex:
2001:db8:8000::0/96
NAT64 IPv4 address pool
192.0.2.1 - 192.0.2.10
IPv4-only Server
port 1
port 2
port 3
OSPF Area 1 OSPF Area 0