HP-UX IPv6 Transport Administrator Guide HP-UX 11i v3 HP Part Number: 5992-6426 Published: May 2013 Edition: 4
© Copyright 2009, 2013 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents About This Document .................................................................................................................7 Intended Audience...................................................................................................7 New and Changed Documentation in This Edition........................................................7 Publishing History.....................................................................................................7 What Is in This Document.
Stateless Autoconfiguration......................................................................................23 Configuring a Primary Interface (Required)............................................................24 Configuring Secondary Interfaces........................................................................24 Configuring Route Information.............................................................................24 Manual Configuration.......................................................
Flowchart 6 Procedures..................................................................................44 4 IPv6 Addressing and Concepts................................................................................................46 Where to Get IPv6 Addresses..................................................................................46 IPv6 Address Formats..............................................................................................46 Address Scope.................................
Contacting Your HP Representative............................................................................64 A IPv6 ndd Tunable Parameters..................................................................................................67 Supported IPv6-related ndd parameters.....................................................................67 Index......................................................................................................................................
About This Document This document describes how to install, configure, and troubleshoot HP-UX 11i v3 IPv6 transport software. The document printing date and part number indicate the document’s current edition. The printing date will change when a new edition is printed. Minor changes may be made at reprint without changing the printing date. The document part number will change when extensive changes are made. Document updates may be issued between editions to correct errors or document product changes.
What Is in This Document This manual provides information for administering HP-UX 11i v3 IPv6 transport software. HP-UX 11i v3 IPv6 transport software uses the next generation Internet Protocol (IPv6) to connect HP-UX Servers and Workstations with other systems running IPv4 or IPv6 over IEEE 802.3, Ethernet, or FDDI Local Area Networks. An IPv6 for HP-UX 11i v3 network can extend over routers into a Wide Area Network (WAN).
Related Documents HP Documentation Additional information about HP-UX 11i v3 IPv6 can be found within docs.hp.com in the networking and communications collection under IPv6 at: http://www.docs.hp.com/hpux/netcom/index.html#IPv6 Other documents in this collection (besides this guide) include: HP-UX IPv6 Porting Guide HP-UX IPv6 Transition Mechanisms (White Paper) Related RFCs As well, the IETF (Internet Engineering Task Force) RFCs listed below can be located at: http://www.ietf.org/rfc.
Table 3 IPv6 RFCs Supported (continued) RFCs Description RFC 3484 Default Address Selection for Internet Protocol version 6 (IPv6) RFC 3493 Basic Socket Interface Extensions for IPv6 RFC 3542 Advanced Sockets API for IPv6 RFC 3678 Socket Interface Extensions for Multicast Source Filters RFC 3810 Multicast Listener Discovery Version 2 (MLDv2) RFC 4193 Unique Local IPv6 Unicast Addresses RFC 4213 Basic Transition Mechanisms for IPv6 Hosts and Routers RFC 4291 IP Version 6 Addressing Architect
1 Features Overview This chapter summarizes the features for HP-UX 11i v3 and an overview of HP-UX 11i v3 IPv6 transport functionality. IPv6 Transport 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.
Following lists the new features in different versions of the IPv6Upgrade bundle: • • • IPv6 Transport Features Available with B.11.31.0907 Version of HP-UX 11i v3 ◦ “Support for RFC 3542 (Advanced Sockets API for IPv6)” (page 13) ◦ “Configurable Policy Table Support” (page 13) ◦ “Anycast Address Support” (page 13) IPv6 Transport Features Available with B.11.31.
NOTE: The HP-UX 11i v3 IPv6Upgrade depot contains the following prerequisite patches: • PHNE_37899 Transport patch • PHNE_37257 STREAMS patch • PHCO_38048 libc patch • PHNE_38153 inetd patch If your HP-UX 11i v3 system already contains patches that are later than the prerequisite patches, the prerequisite patches will not be installed. The subsequent sections discuss the IPv6 features in various versions of the IPv6Upgrade bundle.
architecture from RFC 2983 (Transition Mechanisms for IPv6 Hosts and Routers ) to RFC 4213. Support for RFC 3484 (Default Address Selection for Internet Protocol version 6 (IPv6)) A typical IPv6 host can be assigned multiple addresses with different characteristics, such as link local address, global address, temporary address, unique local address, special purpose addresses for IPv4-IPv6 transition. Additionally, if the host is dual-stack, it is also configured with IPv4 addresses.
Support for IPv6 over VLAN The B.11.31.0809 release of IPv6 provides support for IPv6 over virtual LAN (VLAN). For information on VLAN configuration, see VLAN Administrator's Guide at http:// www.docs.hp.com. Ability to Disable Autoconfiguration Based on Router Advertisements Starting with this release of IPv6, HP provides the ability to disable autoconfiguration based on the contents of the received router advertisements using the ip6_nd_autoconf tunable in the ndd command.
collectors to correlate multiple activities with different addresses to the same node. RFC 4941 defines privacy extensions for stateless address autoconfiguration to address this concern. RFC 4941 defines a mechanism to generate global scoped addresses with randomized interface identifiers that change over a period of time. The interface identifiers changing over a period of time make it more difficult for information collectors to associate different addresses to the same node.
protocols instead of being dropped. A "Destination Unreachable" error message is sent, when forwarding the error message would have sent the message to an address on the same tunnel from which the message was received. 0 Suppresses ICMPv6 errors from being reported, for compatibility with previous versions of IPv6. By default, ndd sets the value of the ip6_icmp6_extended_errors tunable to 0. When the IPv6Upgrade bundle is installed, the bundle sets the value of the tunable to 1.
ip_igmp_v3_unsolicited_interval Specifies the IGMPv3 unsolicited report interval. ip_igmp_qri Specifies the IGMP query response interval. ip_igmp_status Displays a report of the IGMP state. ip_ipc_mcast_maxsrc Specifies the maximum source addresses in the application filter. ip6_ill_no_dest_unreach Disables sending of ICMPv6 destination unreachable message. ip6_nd_use_temp_address Controls the generation of IPv6 temporary addresses as defined in RFC 4941.
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).
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.
• 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.
Distributed File System Limitations NIS, and NFS are currently not supported over IPv6. HP SMH Limitation HP SMHhas not been enhanced to support the tunneling enhancements available with HP-UX 11i v3. 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.
2 Configuration This chapter summarizes the steps to configure LAN interfaces, assign IPv6 addresses, optionally enabling IPv6 tunneling through IPv4 networks, and assigning host names to IPv6 addresses. The first interface configured on a physical LAN interface is called the primary interface. Additional interfaces configured on the same physical device are called secondary interfaces. You must configure an IPv6 primary interface to use IPv6 over that interface.
automatically assigned a link-local IPv6 address by the system when the interface is configured (marked “up”). This link-local IPv6 address is generated by prepending a fixed local address prefix (fe80::) to a token derived from the MAC address. (The address is verified to be unique.) This allows each IPv6 interface to have at least one source address that can be used by Neighbor Discovery.
Manual Configuration The following section describes the manual configuration process for HP-UX 11i v2 IPv6. Configuring a Primary Interface To configure an IPv6 link-local address for a primary interface, edit the IPV6_INTERFACE[0] statement in the /etc/rc.config.d/netconf-ipv6file to specify the interface name and the interface state, either up or down. The interface name must be the name of the physical interface card, as reported by lanscan.
Configuring a Default IPv6 Route In the absence of router advertisements, you can add the default IPv6 router information to the /etc/rc.config.d/netconf-ipv6 file. The routing configuration parameters have an index value, [x], that groups the routing parameters together.
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.
In this example, the TUN_LOCAL_ADDRESS[1] was not specified since the “6to4” address for this value can be automatically configured based on the TUN_ENCAP_SRC_ADDRESS[1] value. For example, if the TUN_ENCAP_SRC_ADDRESS is 15.13.1.2, the “6to4” prefix is 2002:0f0d:0102, which can be combined with an interface identifier of “1” to form the “6to4” address 2002:0f0d:0102::1. The TUN_REMOTE_ADDRESS[1] parameter must not be specified since“6to4” is an automatic point-to-multipoint tunnel.
autoconfiguration using prefixes received in router advertisements. The default is "private", and when set to "private" the interface will autoconfigure addresses using prefixes received in router advertisements. For more information, refer to the relevant commented text in the /etc/rc.config.d/netconf-ipv6 file that is included with HP-UX 11i v3 IPv6.
To configure a secondary interface with an anycast address, enter: ifconfig lan0:2 inet6 2001:db8::6 anycast To add a default IPv6 route, enter: route inet6 add net default 2001:db8::1 To create an IP6-in-IP tunnel, enter: ifconfig iptu0 inet6 tunnel ip6inip tsrc 192.1.1.1 tdst 192.2.2.2 up To create a “6to4” tunnel, enter: ifconfig iptu0 inet6 tunnel 6to4 2002:f0e:8cc::1 tsrc 15.13.1.
Following is a sample ip6addrpol.conf file to configure higher precedence for IPv4 addresses over IPv6: # Prefix/Prefixlen ::1/128 ::ffff:0.0.0.0/96 2002::/16 ::/0 Precedence 50 60 30 40 Label 0 4 2 1 For more information, see the /etc/rc.config.d/ip6addrpol.conf configuration file. Activating the ip6addrpol.conf File You can activate the ip6addrpol.conf configuration in either of the following ways: • Rebooting the system. • Executing the ip6addrpol command with the -c option.
This subsection describes how to edit the /etc/hosts file to add an IPv6 address and host name for the network interface you are configuring. NOTE: If using the name service DNS over IPv6, add the IP address and host name to the appropriate databases on the name server system. Refer to BIND v9.2.0 (or later) documentation on http://www.docs.hp.com for more information on DNS over IPv6. The /etc/hosts file associates IP host addresses with mnemonic host names and alias names.
Thus, if DNS has not been set up as the definitive source, and files (/etc/hosts) may need to be used for address and host name resolution, HP recommends adding the following entry to /etc/nsswitch.conf: ipnodes: files Or if /etc/hosts is to be the primary Name Service, the entry would be set as follows: ipnodes: files [NOTFOUND=continue] dns NOTE: You can not specify NIS or NIS+ on the ipnodes entry. Manually editing nsswitch.conf If the current system has no nsswitch.
3 Troubleshooting This chapter provides guidelines for troubleshooting HP-UX 11i v3 IPv6 transport. It contains a troubleshooting overview and diagnostic flowcharts. Troubleshooting Overview Troubleshooting problems on HP-UX 11i v3 IPv6 transport, can involve a variety of hardware and software components. The problem impacting your system might originate in another part of the network. Because HP-UX 11i v2 IPv6 supports an IPv6/IPv4 Dual Stack, test IPv4 connectivity before testing IPv6 connectivity.
Flowchart 1: Transport Level Testing using Internet Services Figure 1 Flowchart 1 Flowchart 1 Procedures A. Execute: telnet to remote host. Try to connect using telnet to a remote host. B. Succeeds? If telnet succeeds, stop. The system connects using TCP over IPv6 through the Transport Layer (OSI Layer 4). C. Connection Refused? Trying to connect to a remote system where HP-UX 11i v2 IPv6 is not installed can cause this message. D.
E. If connection is established, Ensure IPv6 installed on remote node. If telnet still fails, examine the etc/inetd.conf file on the remote system.
Flowchart 2 Procedures A. ping successful? A message is printed on stdout for each ping packet returned by the remote host. If packets are being returned, your system has network level connectivity to the remote host. B. Execute ping to remote IPv6 address. Using ping, send a message to the IPv6 address of the remote host. For example, ping -f inet6 2001:db8::1234 C. Network unreachable? If so, examine the status of the local LAN interface first. If not, proceed to F. D.
Flowchart 3: Name Service Test Figure 3 Flowchart 3 Flowchart 3 Procedures A. 38 Check /etc/hosts and /etc/nsswitch.conf files. If needed, add a missing host name or IPv6 address. If the IPv6 address for the host is in /etc/hosts, ensure that you have an /etc/nsswitch.conf file entry with an appropriate ipnodes policy.
and start again with Flowchart 3. B. Using DNS? If your name and IPv6 address resolution policy use DNS as the primary resolver, go to C. Otherwise, proceed to E. C. Can you add a Host Name to the DNS Server? Are you a DNS administrator? If so, continue on to D, otherwise proceed to F. D. Add Entry to DNS Server. Refer to the BIND 9.2.0 information in the HP-UX IP Address and Client Management Administrator’s Guide for details (available at http://docs.hp.com). Then retry Flowchart 2. E.
Flowchart 4: Interface Test Figure 4 Flowchart 4 Flowchart 4 Procedures A. Execute: ifconfig inet6. Execute ifconfig on the interface you want to test. For example, to view LAN interface lan0, enter: ifconfig lan0 inet6 B. 40 ifconfig successful? ifconfig succeeds when the output shows an Internet address and the flags: UP, RUNNING, MULTICAST, ONLINK. If successful, go to E, if not continue to C.
C. Any error message returned? If ifconfig fails and displays an error message, go to Flowchart 5. Flowchart 5 shows what to do based on the error message. Otherwise continue to D. D. Correct ifconfig with non-default flag settings. If ifconfig returns an unexpected flag setting, re-execute the command with the proper setting. For more information, refer to the ifconfig(1M) man page. Start again with Flowchart 4. E. Execute: netstat -inf -inet6.
Flowchart 5: Interface Test continued Figure 5 Flowchart 5 Flowchart 5 Procedures A. 42 Is error message “No such interface name”? If not, go to F. If so, the interface name passed to ifconfig does not exist on the system. Using lanscan, verify the spelling and names of the interfaces on the system.
If the system contains more than one LAN card, make sure the correct number of LAN cards was configured into the kernel and that an ifconfig command was executed for each interface. B. Execute: lanscan. E xecute lanscan to display information about the LAN cards in your system. C. Was correct interface name used? Configure interface using ifconfig with the correct interface name. After reconfiguring using the correct interface name, start again with Flowchart 4. D.
Flowchart 6: Router Remote Loopback Test Figure 6 Flowchart 6 Flowchart 6 Procedures A. 44 Execute: ping from known good host through gateway to known good host on remote network. T his tests router connectivity to the remote network. For more information on ping, refer to the ping(1M) man page.
B. ping successful? If ping -f inet6 succeeded, return to Flowchart 2. If ping -f inet6 failed, the problem may exist in the routing table for the problem host. Continue to C. C. Execute: netstat -rnf inet6. To display gateway routing information in numerical form, execute:netstat -rnf inet6 D. Direct route to remote or default route to gateway? If the route exists, go to F. If not, continue to E to add a new route. E. Add route entry on local system.
4 IPv6 Addressing and Concepts This chapter introduces network addressing concepts for IPv6. It contains sections on Obtaining IPv6 Addresses, IPv6 Address Formats, Neighbor Discovery, Stateless Address Autoconfiguration and some basic general Networking Terminology.
Where is an IPv6 address and is a decimal value specifying how many of the leftmost contiguous bits of the address compose the subnet prefix. In Figure 8, prefix length 48 specifies that the leftmost 48 bits of the IPv6 address compose the subnet prefix. Figure 8 Example Prefix Length 48 Address Scope Link-local An IPv6 addres s used on a single link.
The IPv6 Neighbor Discovery Protocol (ndp) uses ICMPv6. An IPv6-only utility, ndp and the Neighbor Discovery Protocol encompass the functionality of the IPv4 Address Resolution Protocol (ARP) and the arp utility. ndp also provides some of the address-configuration functionality found in protocols BOOTP and DHCP. A network device connecting to a network for the first time can learn all parameters necessary to function, solely through Neighbor Discovery information.
Figure 9 Primary Interface Address Autoconfiguration If you mark an interface “up” without assigning a primary address, the system derives a link-local address by performing the following 4 steps: 1. Taking the LAN card’s 48-bit link-level address (“MAC address” 8:0:9:78:f3:39) 0000 1000 0000 0000 0000 1001 0111 1000 1111 0011 0011 1001 2.
Figure 10 Secondary Interface Autoconfiguration From an IPv6 Router 1. 2. 3. 4. Primary interface comes up with the link-local address autoconfigured. Host multicasts Router Solicitation. IPv6 Router sends Router Advertisement to host. Host autoconfigures secondary interface (lan0:1) by prepending prefix (2001:db8:0:13::/64) sent by router to interface identifier ( a00:9ff:fe78:f339). Refer to RFC 2461 “Neighbor Discovery for IP Version 6 (IPv6)” for details.
connectivity through the overwritten autoconfigured IP address is temporarily lost. At a later time, when the host receives the next router advertisement, the host will bring up another secondary interface with a different IP index number, but with the same IP address, and network connectivity through that IP address is restored. Normally, a user can avoid this by checking used IP index numbers.
Host A host is any node that is not a router. Network Interface Name A network interface name is a communication device through which messages can be sent and received. An IPv6 address is associated with an interface name. Find the interface name(s) for a network interface by running the lanscan command and looking at the “Net-Interface Name PPA” field.
5 IPv6 Software and Interface Technology The topics discussed in this section concern IPv6 deployment and migration. Name and Address Lookup for IPv6 It is generally recommended to add IPv6 addresses (known as AAAA records) to a DNS Name Server only when the following conditions are true: • The IPv6 address is assigned to the interface on the node. • The address is configured on the interface. • The interface is on a link which connects to the IPv6 infrastructure.
Migrating Name and IPv6 Address Lookup Most sites test IPv6 on a development subnetwork before deploying it on a larger scale. These sites typically add IPv6 address and host names to the /etc/hosts files on IPv6 hosts, then change their hosts lookup policy to search files. HP recommends that you maintain at least a minimal /etc/hosts file that includes important addresses like gateways, root servers, and your host’s own IP address.
Tunneling can be used in a variety of ways: • Router-to-Router: IPv6/IPv4 dual stack routers interconnected by an IPv4 infrastructure can tunnel IPv6 packets between themselves. In this case, the tunnel spans one segment of the end-to-end path that the IPv6 packet takes. • Host-to-Router: IPv6/IPv4 dual stack hosts can tunnel IPv6 packets to an intermediary IPv6/IPv4 router that is reachable over an IPv4 infrastructure. This type of tunnel spans the first segment of the packet’s end-to-end path.
— Tunnel exit-point node (remote) address: This is the tunnel destination address. For “ip6inip” it will be a link-local IPv6 address configured (automatically if not specified) from the destination address in the encapsulating (outer) header. For “6to4” this value must never be specified, since it will always be automatically determined based on routing information.
On Host A: — Using ifconfig (ephemeral), enter: ifconfig iptu0 inet6 tunnel ip6inip fe80::1 fe80::2 tsrc 192.168.1.1 tdst 10.13.2.2 up — Editing /etc/rc.config.d/netconf-ipv6 (permanent), add: TUN_INTERFACE_NAME[0]=”iptu0” TUN_TYPE[0]=”ip6inip” TUN_LOCAL_ADDRESS[0]=”fe80::1” TUN_REMOTE_ADDRESS[0]=”fe80::2” TUN_ENCAP_SRC_ADDRESS[0]=”192.168.1.1” TUN_ENCAP_DST_ADDRESS[0]=”10.13.2.
On Remote Host: — Using ifconfig (ephemeral), enter: ifconfig ip6tu0 inet6 tunnel ip6inip6 fe80::2 fe80::1 tsrc 2001:db8:3::1 tdst 2001:db8:2::1 up — Editing /etc/rc.config.
NOTE: Refer to the ifconfig(1m) man page and the /etc/rc.config.d/netfconf-ipv6 file for more detailed information on tunneling parameters. “6to4” - Connecting IPv6 Domains over IPv4 Clouds “6to4” is an automatic tunneling mechanism that can be used to provide connectivity between isolated IPv6 domains or hosts across an IPv4 infrastructure and with native IPv6 domains via relay routers.
an IPv4 protocol type of 41, the same protocol type set when IPv6 packets tunnel inside IPv4 frames. “6to4” Topology Example “6to4” topology consists of: one or more “6to4” hosts in a “6to4” domain; at least one “6to4” router in the domain that has at least one IPv4 connection to the Internet; and a “6to4” relay router that is used to connect to a native IPv6 domain. Nodes can perform the role of the “6to4” router. Host configuration continues to be supported, as was the case in base (default) HP-UX 11i v2.
a default route to the "6to4" router. All non-local "6to4" addressed packets and native IPv6 packets are sent to the "6to4" router. "6to4" router: An IPv6/IPv4 border router that forwards "6to4" addressed traffic between "6to4" hosts within a site and other "6to4" routers or to "6to4" relay routers across IPv4 internet. "6to4" routers need to have at least one public IPv4 address and the "6to4" prefix is derived from the public IPv4 address.
“6to4” End-Node View Example Figure 14 shows two IPv6 subnetworks. The end nodes have their routers’ globally unique IPv4 addresses embedded in their network prefixes. The routers have “6to4” addresses and corresponding globally unique IPv4 addresses. From the IPv6 end-node view, each host’s subnetwork is connected to the other’s through a "6to4" router. All IPv4 tunneling is transparent to the IPv6 end nodes.
6 Utilities HP-UX 11i v3 IPv6 transport, for the most part uses IPv6-enhanced IPv4 network utilities. This section summarizes the utilities required for administration of HP-UX 11i v3 IPv6 transport. Configuration Utilities This section describes configuration utilities available to configure HP-UX 11i v3 IPv6 transport. The ifconfig “inet6” Address Family Use ifconfig to assign an IPv6 address to an interface and configure parameters, such as the network prefix. (In IPv6, prefix replaces netmask.
• ping(1M) verifies network connectivity through the Network Layer and reports round-trip time of communication time between hosts. • traceroute(1M) traces the path between hosts at the Network Layer. • The network interface management (nwmgr(1M)) is a command for LAN and RDMA interfaces. IPv6 Additions to Network Tracing and Logging Use nettl to trace traffic through IPv6 Subsystems, or use nettladm. Table 4 below lists the subsystems available for IPv6 packet tracing.
If you have a service contract with HP, document the problem as a Service Request (SR) and forward it to your HP representative. Include the following information where applicable: • A characterization of the problem. Describe the events and symptoms leading up to the problem. Attempt to describe the source of the problem.
• Record the troubleshooting flowchart number and step number where you are unable to resolve the problem. • Save all network log files. Make sure that ERROR and DISASTER log classes are enabled when STREAMS subsystem log files are collected in/var/adm/ nettl.LOG000.
A IPv6 ndd Tunable Parameters The following IPv6 tunable parameters allow advanced fine-tuning of HP-UX 11i v2 IPv6 performance.
Table 6 Supported IPv6 ndd parameters (continued) Parameter Description ip6_enable_rfc4291 Enables the RFC 4291 functionality. ip6_mld_version Controls the MLD protocol version used by the system. ip6_addr_sel_enable Enables or disables RFC 3484. ip6_icmp6_extended_errors Specifies whether to report additional ICMPv6 error messages as defined in RFC 4443. ip_igmp_version Controls the IGMP protocol version used by the system.
Table 6 Supported IPv6 ndd parameters (continued) Parameter Description ip6_ire_reachable_interval Controls the ND REACHABLE_TIME ip6_max_random_factor Controls the ND MAX_RANDOM_FACTOR ip6_min_random_factor Controls the ND MIN_RANDOM_FACTOR ip6_nd_advertise_count Controls the ND MAX_NEIGHBOR_ADVERTISEMENT ip6_nd_anycast_delay Controls the ND MAX_ANYCAST_DELAY_TIME ip6_nd_dad_solicit_count Controls the number of duplicate address ip6_nd_multicast_solicit_count Controls the ND MAX_MULTICAST_SOL
Index Symbols /etc/hosts, 21, 31, 38, 53, 54 6to4, 20, 27, 54, 55, 59, 60, 62 6to4 configured tunnel, 27, 30 A activating configuration changes, 29 address autoconfiguration, 20, 23, 48 address formats, 46 address scope, 47 address type, 47 addressing, 31, 46 anycast address, 47 autoconfiguration, 20, 23, 48 automatic tunneling, 20 C configuration, 21, 23 configuration (manual), 50 configured tunnel, 27 configured tunneling, 19, 55 Contacting HP, 64 D default router information, 26 deployment, 53 deploym
nsswitch.conf(4), 21, 32, 38, 53 P ping(1M), 21, 37, 44, 64 prefix, 46 prefix length, 46 R removing an interface, 51 RFCs, 9 route(1M), 21, 23, 29, 45, 63 router, 51 router advertisement, 28 Router Advertisement Daemon, 19 router configuration, 24 rtradvd, 19, 28 rtradvd.
