HP-UX IPv6 Transport Administrator's Guide for TOUR 2.0 (April 2004, rev 2)

Conﬁguration

Manual Conﬁguration

Chapter 3 25

— Automatic tunneling using the IPv4-compatible address is not

supported.

The following sections provides basic examples for conﬁguring 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 ﬁle and the

ifconfig(1M) man page that ship with HP-UX 11i v2 TOUR 2.0.

For more information on the tunneling mechanisms supported in TOUR

2.0 refer to the section on “Tunneling” on page 72, in Chapter 7, IPv6

Software and Interface Technology,, later in this Guide.

NOTE SAM has not been enhanced to support the tunneling enhancements

available with TOUR 2.0.

Creating an IP6-in-IP Point-to-Point Conﬁgured Tunnel

If you regularly expect to exchange data between isolated IPv6 networks

over an IPv4 network, you may want to create a conﬁgured IP6-in-IP

tunnel. IP6-in-IP tunnels can be set up as host->host; host->router;

router->host or router->router. In TOUR 2.0 the HP-UX 11i v2 node, can

perform the role of a host or router.

A sample netconf-ipv6 ﬁle entry, for conﬁguring the HP-UX 11i v2 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

speciﬁed. For example, TUN_LOCAL_ADDRESS[0] was not speciﬁed

since the IPv6 link-local address for this value can be automatically

conﬁgured based on the TUN_ENCAP_SRC_ADDRESS[0] value.

Similarly, the IPv6 link-local TUN_REMOTE_ADDRESS can be

automatically conﬁgured based on the TUN_ENCAP_DST_ADDRESS.