HP-UX IPv6 Transport Administrator Guide HP-UX 11i v3 (5992-6426, May 2013)

Tunneling can be used in a variety of ways:
• Router-to-Router: IPv6/IPv4 dual stack routers interconnected by an IPv4 infrastructure
can tunnel IPv6 packets between themselves. In this case, the tunnel spans one
segment of the end-to-end path that the IPv6 packet takes.
• Host-to-Router: IPv6/IPv4 dual stack hosts can tunnel IPv6 packets to an intermediary
IPv6/IPv4 router that is reachable over an IPv4 infrastructure. This type of tunnel
spans the first segment of the packet’s end-to-end path.
• Host-to-Host: IPv6/IPv4 (dual stack hosts that are interconnected by an IPv4
infrastructure can tunnel IPv6 packets between themselves. In this case, the tunnel
spans the entire end-to-end path that the packet takes.
• Router-to-Host: IPv6/IPv4 routers can tunnel IPv6 packets to their final destination
IPv6/IPv4 host. This tunnel spans only the last segment of the end-to-end path.
The HP-UX 11i v3 IPv6/IPv4 dual stack node can perform the role of the router. It can
also continue to perform the role of the host, as it has since the first offering of HP-UX
IPv6 transport.
Configured Tunneling
Configured Tunnels are point-to-point tunnels; tunnel configuration must be done on both
ends of the tunnel. The tunnel endpoint is determined from the configuration information.
RFC 4213 specifies tunnels as IPv6 interfaces and requires them to be configured with
at least (on primary interfaces) link-local addresses. To conform to RFC 4213, tunnels
are implemented as IPv6 pseudo-interfaces.
In HP-UX 11i v3 tunnels can be configured (ephemerally) using ifconfig and
permanently by editing /etc/rc.config.d/netconf-ipv6. In general, the following
tunnel parameters are relevant in HP-UX 11i v3:
— Tunnel interface name: This is a local identifier name for each tunnel configured. (It
need not be the same on both ends of the configured tunnel.) For IP6-in-IP and “6to4”
tunnels this would be iptu<#> (e.g. iptu0, iptu1). For IP6-in-IP6 and IP-in-IP6 tunnels
it would be ip6tu<#> (e.g. ip6tu0, ipt6u1).
— Tunnel Type: Type of tunnel. Supported tunnels are: “ip6inip”, “6to4” , “ip6inip6”,
and “ipinip6”.
— Tunnel entry-point node (local) address: This is the tunnel source address. For tunnel
types "ip6inip" and "ip6inip6", it should be a link-local IPv6 address. Example:
fe80::1. For tunnel type "ip6inip", if the link-local address is not specified, it will be
automatically configured based on the source address in the encapsulating (outer)
header. For tunnel type "ipinip6", it should be an IPv4 address. For tunnel type
"6to4", it should be a “6to4” address derived from the source address in the
encapsulating (outer) header. For example if the source address in the encapsulating
(outer) header is 15.13.136.204, the “6to4” prefix should be 2002:0f0d:88cc::,
which can be combined to an interface identifier "1" to form the “6to4” address
2002:0f0d:88cc::1.
Migrating from IPv4 to IPv6 55