HP VPN Firewall Appliances VPN Configuration Guide

84
link MTU 1500 (true link MTU 65515)
current hop limit 255
reachable time 42500ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 0
default site prefix length 48
# The host acquires the address prefix 2001::/64 and has automatically generated the address
2001::5efe:2.1.1.2. The message "uses Router Discovery" indicates that the router discovery
function is enabled on the host. Ping the IPv6 address of the tunnel interface of the firewall. The
ping operation succeeds, indicating an ISATAP tunnel has been 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
Verifying the configuration
After the configuration, the ISATAP host can access the host in the IPV6 network.
Configuring an IPv4 over IPv4 tunnel
Configuration prerequisites
Configure an IP addresses for the interface (such as a VLAN interface, Ethernet interface, or loopback
interface) to be configured as the source interface of the tunnel interface.
Configuration guidelines
Follow these guidelines when you configure an IPv4 over IPv4 tunnel:
If the destination IPv4 network is not on the same subnet as the IPv4 address of the local tunnel
interface, you must configure a route destined for the destination IPv4 network through the tunnel
interface. You can configure a static route, and specify the local tunnel interface as the output
interface or specify the IPv4 address of the peer tunnel interface as the next hop. Alternatively, you
can enable a dynamic routing protocol on both tunnel interfaces to achieve the same purpose. For
detailed configurations about static routes or other routing protocols, see Network Management
Configuration Guide.
The IPv4 address of the local tunnel interface cannot be on the same subnet as the destination
address configured on the tunnel interface.