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

95
[RouterA-Tunnel0] source GigabitEthernet 0/2
[RouterA-Tunnel0] tunnel-protocol ipv6-ipv4 6to4
[RouterA-Tunnel0] quit
# Configure a static route whose destination address is 2002::/16 and next-hop is the tunnel
interface.
[RouterA] ipv6 route-static 2002:: 16 tunnel 0
• Configure Router B:
# Enable IPv6.
system-view
[RouterB] ipv6
# Configure an IPv6 address for GigabitEthernet 0/2.
[RouterB] interface GigabitEthernet 0/2
[RouterB-GigabitEthernet0/2] ip address 5.1.1.1 24
[RouterB-GigabitEthernet0/2] quit
# Configure an IPv6 address for GigabitEthernet 0/1.
[RouterB] interface GigabitEthernet 0/1
[RouterB-GigabitEthernet0/1] ipv6 address 2002:0501:0101:1::1/64
[RouterB-GigabitEthernet0/1] quit
# Configure a 6to4 tunnel.
[RouterB] interface tunnel 0
[RouterB-Tunnel0] ipv6 address 2002:0501:0101::1/64
[RouterB-Tunnel0] source GigabitEthernet 0/2
[RouterB-Tunnel0] tunnel-protocol ipv6-ipv4 6to4
[RouterB-Tunnel0] quit
# Configure a static route whose destination address is 2002::/16 and next-hop is the tunnel
interface.
[RouterB] ipv6 route-static 2002:: 16 tunnel 0
Verifying the configuration
After the above configuration, ping either host from the other, and the ping operation succeeds.
D:\>ping6 -s 2002:201:101:1::2 2002:501:101:1::2
Pinging 2002:501:101:1::2
from 2002:201:101:1::2 with 32 bytes of data:
Reply from 2002:501:101:1::2: bytes=32 time=13ms
Reply from 2002:501:101:1::2: bytes=32 time=1ms
Reply from 2002:501:101:1::2: bytes=32 time=1ms
Reply from 2002:501:101:1::2: bytes=32 time<1ms
Ping statistics for 2002:501:101:1::2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 13ms, Average = 3ms