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

The following sections provides basic examples for configuring an IP6-in-IP tunnel and a
“6to4” tunnel. For more information including additional optional tunnel parameters not
mentioned in these examples, refer to the /etc/rc.config.d/netconf-ipv6 file
and the ifconfig(1M) man page that ship with HP-UX 11i v3.
For more information on the tunneling mechanisms supported in HP-UX 11i v3, refer to
the section on “Tunneling” (page 54), in Chapter 5: IPv6 Software and Interface
Technology,, later in this Guide.
NOTE: HP SMH has not been enhanced to support the tunneling enhancements available
with HP-UX 11i v3.
Creating an IP6-in-IP Point-to-Point Configured Tunnel
If you regularly expect to exchange data between isolated IPv6 networks over an IPv4
network, you may want to create a configured IP6-in-IP tunnel. IP6-in-IP tunnels can be
set up as host->host; host->router; router->host or router->router. In HP-UX 11i v3 the
HP-UX 11i v3 node can perform the role of a host or router.
A sample netconf-ipv6 file entry, for configuring the HP-UX 11i v3 IPv6 node is as
follows:
TUN_INTERFACE_NAME[0]=”iptu0”
TUN_TYPE[0]=”ip6inip”
TUN_LOCAL_ADDRESS[0]=””
TUN_REMOTE_ADDRESS[0]=””
TUN_ENCAP_SRC_ADDRESS[0]=”15.1.1.1”
TUN_ENCAP_DST_ADDRESS[0]=”15.2.2.2”
TUN_INTERFACE_STATE[0]=”up”
This example minimizes the number of variables that need to be specified. For example,
TUN_LOCAL_ADDRESS[0] was not specified since the IPv6 link-local address for this
value can be automatically configured based on the TUN_ENCAP_SRC_ADDRESS[0]
value. Similarly, the IPv6 link-local TUN_REMOTE_ADDRESS can be automatically
configured based on the TUN_ENCAP_DST_ADDRESS.
Creating a “6to4” Point-to-Multipoint Configured Tunnel
“6to4” offers a point-to-multipoint router-to-router tunneling mechanism for traffic going
between IPv6 domains over an IPv4 network. One of the advantages of “6to4” over
configured tunneling is that the source router can talk to any other “6to4” router without
the need for any manual configuration on the destination router. Thus, “6to4” tunnels
do not suffer the scalability problem that configured tunnels do.
A sample netconf-ipv6 file entry to configure a “6to4” tunnel is as follows:
TUN_INTERFACE_NAME[1]=”iptu1”
TUN_TYPE[1]=”6to4”
TUN_ENCAP_SRC_ADDRESS[1]=”15.13.1.2”
TUN_INTERFACE_STATE[1]=”up”
Manual Configuration 27