Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP-UX IPv6 Transport Administrator's Guide for TOUR 2.0: HP-UX 11i v1 > Chapter 1 Features Overview

IPv6 Transport (bundled as part of TOUR 2.0)

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

IPv6 is the next generation Internet Protocol. The IPv6 protocol is also referred to as "IPng" (IP next generation). It provides the infrastructure for the next wave of Internet devices, such as PDAs, mobile phones and appliances. It also provides greater connectivity for existing devices such as laptop computers.

IPv6 was designed by the Internet Engineering Task Force (IETF) to improve upon the scalability, security, ease of configuration, and network management capabilities of IPv4.

The following sections highlight new IPv6 features available with TOUR 2.0. Additionally, overview information is included about features available in TOUR 2.0, which have been available since TOUR 1.0 and/or IPv6NCF11i.

HP-UX 11i v1 IPv6 Transport Features New with TOUR 2.0

This section describes new IPv6 transport features available with TOUR 2.0.

netstat Enhanced to Support the Display of 64-bit MIB Counters:

netstat in TOUR 2.0 has been enhanced (for IPv4 and IPv6) to support the display of 64-bit MIB (Management Information Base) counters. Thus, some of the netstat fields have the potential to display widened output. This can cause a wraparound effect on 80-character displays.

IPv6 Transition Mechanism Enhancements:

TOUR 2.0 provides several IPv6 transition mechanism changes from those previously offered. 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 now supported in TOUR 2.0 (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 IPv6 bundled as part of TOUR 2.0, requires specific changes from tunnel configurations on previous HP-UX IPv6 releases. For detailed information, including specific configuration instructions, refer to relevant sections of Chapter 3 “Configuration” of this guide.

SAM has not been enhanced to support the new tunneling enhancements available with TOUR 2.0. TOUR 2.0 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 overcome this problem, RFC 2893 specifies tunnels as IPv6 interfaces and requires them to be configured with at least (on primary interfaces) link-local addresses.

    As a result, the process for configuring tunnels using the ifconfig and route commands and the /etc/rc.config.d/netconf-ipv6 file is different than it was in previous HP-UX 11i v1 IPv6 releases (TOUR 1.0 and IPv6NCF11i).

  • HP-UX server can be configured as a router in a point-to-point configured tunnel: You can configure tunneling between the following network nodes: host->router; host->host; router-> host; and router->router. In TOUR 2.0, the HP-UX server can perform the role of the router in the tunnel configuration. Prior to TOUR 2.0 (in TOUR 1.0 for HP-UX 11i v1 and in base (default) HP-UX 11i v2), the HP-UX server could only perform the host role.

  • HP-UX server can be configured as a “6to4” router: Starting with TOUR 2.0, the HP-UX server can perform the role of a router in a “6to4” configuration. Prior to TOUR 2.0, the HP-UX server was only able to perform the role of a host in a “6to4” configuration.

  • IP6-in-IP6 and IP-in-IP6 Support: Starting with TOUR 2.0, two new tunneling types are supported, IP6-in-IP6 and IP-in-IP6. IP6-in-IP6 tunnel configuration allows transmission of IPv6 packets encapsulated in an IPv6 header. IP-in-IP6 tunnel configuration allows transmission of IPv4 packets encapsulated in an IPv6 header.

    IP6-in-IP tunnel configuration allows transmission of IPv6 packets encapsulated in an IPv4 header. IP6-in-IP represents the tunneling scenario where isolated IPv6 domains are communicating across IPv4 networks. IP6-in-IP tunneling is not new in TOUR 2.0, it has been supported in TOUR 1.0 and IPv6NCF11i.

  • Automatic Tunneling using IPv4-compatible addresses is no longer supported: Automatic Tunneling using the special IPv6 address type known as “IPv4-compatible address”, is no longer supported with TOUR 2.0. The IETF is in the process of deprecating this mechanism in favor of the generic automatic tunneling mechanism known as “6to4.”

HP-UX 11i v1 IPv6 Transport Features Available since TOUR 1.0

Since TOUR 1.0, the following IPv6 transport features have been available:

  • Host MLD Support: The host part of Multicast Listener Discovery (MLD) protocol for IPv6 based on RFC 2710 “Multicast Listener Discovery (MLD) for IPv6”, is supported. MLD is automatically enabled when an IPv6 interface is initialized. The Management Information Base for MLD, based on RFC 3019, is also supported.

    RFC 2710 specifies the protocol used by an IPv6 router to discover the presence of multicast listeners (that is, nodes wishing to receive multicast packets) on its directly attached links, and to discover specifically, which multicast addresses are of interest to those neighboring nodes. This protocol is referred to as Multicast Listener Discovery or MLD. MLD is derived from version 2 of IPv4’s Internet Group Management Protocol, IGMPv2. One important difference to note is that MLD uses ICMPv6 (IP Protocol 58) message types, rather than IGMP (IP Protocol 2) message types.

    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 new 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.

  • FDDI Link Support.

  • MC/ServiceGuard Enablement for IPv6 support.

Additional HP-UX 11i v1 IPv6 Transport Features

The following IPv6 transport features are also available as part of TOUR 2.0 (these were in TOUR 1.0 and have been available since the first HP-UX 11i v1 IPv6 product, IPv6NCF11i, was offered):

  • IPv6/IPv4 Dual Stack: HP-UX 11i v1 IPv6 supports both IPv4 and IPv6 applications. Programmers can write IPv6 applications that communicate with both IPv6 and IPv4 peers. Existing IPv4 applications do not need to be modified.

  • Tunneling: IPv6 tunneling enables IPv6/IPv4 hosts and routers to connect with other IPv6/IPv4 hosts and routers over the existing IPv4 network. IPv6 tunneling encapsulates IPv6 datagrams within IPv4 packets. The encapsulated packets travel across an IPv4 infrastructure until they reach their destination host or router. The IPv6-aware host or router decapsulates the IPv6 datagrams, forwarding them as needed. IPv6 tunneling eases IPv6 deployment by maintaining compatibility with the large existing base of IPv4 hosts and routers.

  • Full Ethernet Link Support.

  • IPv6 Stateless Address Autoconfiguration.

  • IPv6 Neighbor Discovery.

  • TCP/UDP over IPv6, PMTUv6, ICMPv6, IPv6 MIBs and Sockets APIs.

  • Network Configuration and Troubleshooting Utilities for both IPv4 and IPv6: ifconfig, netstat, ping, route, ndd, ndp (neighbor-discovery command for IPv6 only) and traceroute. There have also been enhancements to nettl and netfmt for IPv6 tracing and formatting.

  • New netconf-ipv6 file stores IPv6 settings. The /etc/rc.config.d/netconf-ipv6 configuration file stores IPv6 configuration information similar to IPv4’s /etc/rc.config.d/netconf file.

  • The /etc/hosts file now supports IPv4 and IPv6 addresses. The /etc/hosts file contains IP addresses and corresponding host names. The file can contain IPv4 and IPv6 addresses for the same host. Lookup policies are identical to IPv4.

  • Name Service Switch: /etc/nsswitch.conf is a configuration file for the name service switch. A new entity, ipnodes, specifies which name services resolve IPv6 addresses and host names. Refer to the nsswitch.conf(4) man page for more information.

  • The following IPv6-capable Internet Services are included with HP-UX 11i v1 IPv6 bundled as part of TOUR 2.0:

    • inetd, Internet Services Daemon

    • telnet

    • r- commands (rlogin, remsh, rexec, rwho)

    • name and address resolution resolver routine

    • inetd.sec over IPv6

    The following Internet Services have been IPv6-enhanced (but are not included as part of HP-UX 11i v1 IPv6 in TOUR 2.0):

    • WU-FTPD 2.6.1

    • Sendmail 8.11.1

    • BIND 9.2.0

    • DHCPv6

    • RIPng

    • IS-IS (Intermediate System-Intermediate System) routing protocol

    These IPv6-enhanced products are available separately at http://www.software.hp.com. Download these web releases if you want to use FTP, Sendmail, or DNS server to handle IPv6 addresses.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2004 Hewlett-Packard Development Company, L.P.