H3C Technologies H3C S10500 Series Switches - Manual (Page 178)

167
DAD transmits 0
default site prefix length 48
# By comparison, it is found that the host acquires the address prefix 2001::/64 and automatically
generates the address 2001::5efe:2.1.1.2. Meanwhile, “uses Router Discovery” is displayed, indicating
that the router discovery function is enabled on the host. At this time, ping the IPv6 address of the tunnel
interface of the switch. If the address is successfully pinged, an ISATAP tunnel is established.
C:\>ping 2001::5efe:1.1.1.1
Pinging 2001::5efe:1.1.1.1 with 32 bytes of data:
Reply from 2001::5efe:1.1.1.1: time=1ms
Reply from 2001::5efe:1.1.1.1: time=1ms
Reply from 2001::5efe:1.1.1.1: time=1ms
Reply from 2001::5efe:1.1.1.1: time=1ms
Ping statistics for 2001::5efe:1.1.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms
Verification
The ISATAP host can access the host in the IPV6 network.
Configuring an IPv4 over IPv4 tunnel
Configuration prerequisites
Configure IP addresses for interfaces (such as the VLAN interface, and loopback interface) on the device
to ensure normal communication. One of the interfaces will be used as the source interface of the tunnel.
Configuration guidelines
Follow these guidelines when you configure an IPv4 over IPv4 tunnel:
• To encapsulate and forward IPv4 packets whose destination address does not belong to the subnet
where the receiving tunnel interface resides, configure a static route or dynamic routing for
forwarding those packets through this tunnel interface. If you configure a static route to that
destination IPv4 address, specify this tunnel interface as the outbound interface, or the peer tunnel
interface address as the next hop. A similar configuration is required at the other tunnel end. If you
configure dynamic routing at both ends, enable the dynamic routing protocol on both tunnel
interfaces. For the detailed configuration, see Layer 3—IP Routing Configuration Guide.
• The IPv4 address of the local tunnel interface cannot be on the same subnet as the destination
address of the tunnel.
• The destination address of a route with a tunnel interface as the egress interface must not be on the
same subnet as the destination address of the tunnel.
• Two or more tunnel interfaces using the same encapsulation protocol must have different source and
destination addresses.