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

For more MLD information refer to RFC 2710, “Multicast Listener Discovery (MLD)
for IPv6”.
• Router Advertisement: Router Functionality as specified in RFC 2461 “Neighbor
Discovery for IP Version 6 (IPv6)”, is implemented with a daemon, rtradvd, and
an accompanying configuration file, /etc/rtradvd.conf. The rtradvd daemon
listens to router solicitation and sends router advertisement messages on demand
or periodically (as described in RFC 2461). These advertisements allow any listening
host to configure their addresses and some other parameters automatically without
manual intervention. They can also choose a default router based on these
advertisements
Router advertisement is configured on a per interface basis. Refer to the
rtradvd.conf(4) man page for more information.
• IPv6 Transition Mechanism Enhancements: HP-UX 11i v3 provides several IPv6
transition mechanism changes from those previously offered in base (default) HP-UX
11i v2. Highlights of these changes are provided below. There have been no changes
to the dual stack mechanism, but several important changes to the tunneling
mechanisms. The following RFCs are supported (the IETF documents listed below
are available at http://www.ietf.org):
RFC 2473 - Packet Tunneling in IPv6
RFC 2893 - Transition Mechanisms for IPv6 Hosts and Routers
RFC 3056 - Connection of IPv6 Domains via IPv4 Clouds
IMPORTANT: As a result of supporting RFC 2893, tunnel configuration on HP-UX
11i v3, requires specific changes from tunnel configurations on base (default) HP-UX
11i v2. For detailed information, including specific configuration instructions, refer
to relevant sections of Chapter 2: “Configuration”, of this guide.
HP SMH has not been enhanced to support the tunneling enhancements. HP-UX 11i
v3 tunneling configuration must be done by editing the
/etc/rc.config.d/netconf-ipv6 file or by using the ifconfig command.
◦ Configured tunneling is point-to-point with addresses assigned to tunnel endpoints:
In conformance with RFC 2893 (which obsoletes RFC 1933) configured tunnels
are pseudo-interfaces with associated addresses. Previously, when conforming
to RFC 1933, tunnels were implemented using special routing entries. The RFC
1933 implementation did not allow addresses to be associated with tunnels and
hence, routing protocol daemons were not able to operate over tunnels. To
IPv6 Transport 19