Manual

Environment Guide
Version 9.02.00
66
© Copyright Kofax, Inc. All information is subject to change without notice.
ipv6 nat v6v4 source fd96:eb5f:7508:5760:204:23ff:feac:4172 172.20.148.53
ipv6 nat prefix FD96::/96
!
Cisco router 28xx configuration using dynamic IPv4-mapped NAT-PT:
This configuration allows each IPv6 only host to talk with any of the IPv4 only hosts by:
1. Defining the pool/range of IPv4 addresses as IPv4 “proxy” addresses for IPv6 hosts (in the example
below 172.20.148.53 172.20.148.62 with the prefix length 24, which corresponds with IPv4 mask
255.255.255.0)
2. Configuring the NAT-PT prefix to be “v4-mapped” – it means that each IPv6 address
FD96::AABB:CCDD would be translated to IPv4 address determined by last 32 bits AABB:CCDD. With
our example, in order to reach LS1‟s address 172.20.148.6 KCS core would send the IPv6 packet to
the destination address FD96::AC14:9406
! Global settings
!
Ipv6 unicast-routing
no ipv6 cef
!
! Interface related settings
!
! IPv4 interface
interface GigabitEthernet0/0
ip address 172.20.148.35 255.255.255.0
duplex auto
speed auto
ipv6 nat
!
! IPv6 interface
interface GigabitEthernet0/1
no ip address
duplex auto
speed auto
ipv6 address FD96:EB5F:7508:5760::/64 eui-64
ipv6 nat
no ipv6 redirects
!
! NAT-PT configuration
ipv6 nat v6v4 source list nat_traffic pool ipv6_2_ipv4
ipv6 nat v6v4 pool ipv6_2_ipv4 172.20.148.53 172.20.148.62 prefix-length 24
ipv6 nat prefix FD96::/96 v4-mapped nat_traffic
!
ipv6 access-list nat_traffic
permit ipv6 any FD96::/96
!
KCS core and LS1 configuration using NAT-PT:
1. Given the LS1 is properly setup to listen on particular IPv4 address (like 172.20.148.6 in the example
above) there is no need to configure anything as for NAT-PT
2. In the KCS core simply configure the corresponding “proxy” IPv6 address of the LS1, instead of its IPv4
address
Common Cisco NAT-PT pitfalls:
1. NAT-PT translation is not supported in Cisco Express Forwarding (CEF).
The CEF must be disabled by the command no ipv6 cef (see examples above).