 |
» |
|
|
|
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 IPv6
features available with TOUR 2.0. Additionally, overview information
about features available in TOUR 2.0 but not new to TOUR 2.0 (first
introduced in base (default) HP-UX 11i v2) are included. HP-UX
11i v2 IPv6 Transport Features Available with TOUR 2.0 | |
This section describes HP-UX 11i v2 IPv6 transport features
available with TOUR 2.0 (not available in base (default) HP-UX 11i
v2). 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. IPoIB (IP over InfiniBand)
Link Support: TOUR 2.0 provides transport support for
InfiniBand links that support IPoIB. The TOUR 2.0 transport software
support is required for HP InfiniBand links to run IPoIB. The HP-UX networking utilities ifconfig, netstat, lanadmin, lanscan, arp, rtradvd and ndp have all been enhanced to be capable of handling IPoIB-related
data. (Note that rarp has not been enhanced for handling IPoIB.) IPoIB-support only applies on HP-UX 11i v2 (for both IPv4
and IPv6). IPoIB-supported links are not supported on HP-UX 11i
v1. For more information on InfiniBand and the IPoIB protocol,
refer to the HP-UX
InfiniBand Support Guide available at http://www.docs.hp.com/hpux/netcom/index.html#InfiniBand. Multicast Listener Discovery
(MLD) Support (Host Portion Only): 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 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: TOUR 2.0 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 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 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 base (default) HP-UX
11i v2. 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 additional 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 base
(default) HP-UX 11i v2. 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 v2 IPv6 Transport Features Available since HP-UX 11i v2 (not
new to TOUR 2.0 release) | |
In TOUR 2.0 and prior to TOUR 2.0 (base (default) HP-UX 11i
v2) IPv6 transport supports the following features: | | | |  | NOTE: This section focuses on HP-UX 11i v2 IPv6 transport features,
but be aware that IPv6 is also supported on the following HP-UX
11i v2 components: Internet Services, DCE, DLPI, FDDI, SAM-NNC,
Libc, Commands, Desktop (CDE), X11R6-based applications, C2 Audit,
EMS, Online Diagnostics, SNMP, nettl, IPSec, Kerberos Client, Service
Guard, Glance, HP-UX Secure Shell, Apache, and JVM. Refer to product-specific documentation
for more information. | | | | |
IPv6/IPv4 Dual Stack support:
HP-UX 11i v2 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. 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 network 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. Fully supports Ethernet Links and FDDI links. MC/ServiceGuard Enablement
for IPv6 support. IPv6 Stateless Address Autoconfiguration. 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. The 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 IPv6 and IPv4 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. For example: 15.15.15.15 hpindon
3ffe:1111::1234 hpindon hpindon6 |
Name Service Switch: /etc/nsswitch.conf is
a configuration file for the name service switch. The ipnodes entity specifies which name services resolve IPv6 addresses
and host names. Refer to the nsswitch.conf(4) man page for more information.
|
Printable version
