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

76
NOTE:
You must also configure a static route to network 6.6.6.0/24 on the DNS server. The configuration
procedure is not shown.
Verifying the configuration
# Execute the ping ipv6 SecPathC.com command on SecPath A. The ping operation is successful and the
output displays that the resolved address is 2000:0:404:402::. This address is translated from the IPv4
address of SecPath C by using the DNS64 prefix.
[SecPathA] ping ipv6 SecPathC.com
Trying DNS resolve, press CTRL_C to break
Trying DNS server (2000:0:303:305::)
PING SecPathC.com (2000:0:404:402::):
56 data bytes, press CTRL_C to break
Reply from 2000:0:404:402::
bytes=56 Sequence=1 hop limit=254 time = 2 ms
Reply from 2000:0:404:402::
bytes=56 Sequence=2 hop limit=254 time = 2 ms
Reply from 2000:0:404:402::
bytes=56 Sequence=3 hop limit=254 time = 1 ms
Reply from 2000:0:404:402::
bytes=56 Sequence=4 hop limit=254 time = 1 ms
Reply from 2000:0:404:402::
bytes=56 Sequence=5 hop limit=254 time = 2 ms
--- SecPathC.com ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 1/1/2 ms
# Execute the display session table verbose command on SecPath B to display the established sessions.
[SecPathB] display session table verbose
Initiator:
Source IP/Port : 0006::0002/2628
Dest IP/Port : 2000:0:0303:0305::/53
VPN-Instance/VLAN ID/VLL ID:
Responder:
Source IP/Port : 3.3.3.5/53
Dest IP/Port : 6.6.6.10/12298
VPN-Instance/VLAN ID/VLL ID:
Pro: UDP(17) App: DNS State: UDP-READY
Start time: 2010-12-21 17:00:06 TTL: 52s
Root Zone(in):
Zone(out): Management
Received packet(s)(Init): 1 packet(s) 77 byte(s)
Received packet(s)(Reply): 2 packet(s) 183 byte(s)
Initiator: