H3C Technologies H3C SecPath F1000-E - Manual (Page 196)

11
[DeviceB] natpt v6bound dynamic prefix 3001:: address-group 1
Step2 Configure Device A on the IPv4 side
# Configure a static route to subnet 9.0.0.0/24.
system-view
[DeviceA] ip route-static 9.0.0.0 24 8.0.0.1
Step3 Configure Device C on the IPv6 side
# Enable IPv6.
system-view
[DeviceC] ipv6
# Configure a static route to the subnet with the NAT-PT prefix.
[DeviceC] ipv6 route-static 3001:: 16 2001::1
Verification
If you carry out the ping ipv6 3001::0800:0002 command on Device C after completing the
configurations above, response packets can be received.
At this time, you can see on Device B the established NAT-PT session.
[DeviceB] display natpt session all
NATPT Session Info:
No IPV6Source IPV4Source Pro
IPV6Destination IPV4Destination
1 2001::0002 ^43984 9.0.0.19 ^12288 ICMP
3001::0800:0002 ^ 0 8.0.0.2 ^ 0
Configuring Static Mappings on the IPv4 Side and the IPv6
Side
Network requirements
As shown in Figure 4 , Device C with IPv6 address 2001::2/64 on an IPv6 network can communicate
with Device A with IPv4 address 8.0.0.2/24 on an IPv4 network.
To meet the preceding requirement, you need to configure Device B that is deployed between the IPv4
network and IPv6 network as a NAT-PT device, and configure static mappings on the IPv4 side and IPv6
side on Device B, so that Device A and Device C can communicate with each other.
Figure 4 Network diagram for NAT-PT (static mappings)
Configuration procedure
Step1 Configure Device B