Administering IPv6 (Task)

This chapter shows you how to enable IPv6 and IPv6 routers. This chapter also shows you how to configure IPv6 addresses for DNS, NIS, and NIS+. You also learn how to create tunnels between routers. This chapter also shows you how to run IPv6 additions to commands that display diagnostics. Finally, this chapter shows you how to display IPv6 name service information.

This chapter contains the following information:

• "Enabling IPv6 Nodes"

• "Enabling IPv6 Nodes Task Map"

• "Monitoring IPv6"

• "Monitoring IPv6 Task Map"

• "Configuring IPv6 Over IPv4 Tunnels"

• "Displaying IPv6 Name Service Information"

• "Displaying IPv6 Name Service Information Task Map"

Enabling IPv6 Nodes

This section provides procedures that you might need to configure IPv6 nodes on your network.

Note - The term node in this context refers either to a Solaris server or client workstation.

Enabling IPv6 Nodes Task Map

Table 15-1 Enabling IPv6 Nodes Task Map

Note - You can enable IPv6 on a system when you install the Solaris software. If you answered yes to enable IPv6 during the installation process, you can omit the following procedures to enable IPv6.

How to Enable IPv6 on a Node

1. Become superuser on the system where you want to enable IPv6.

2. On a command line, type the following for each interface.

   # touch /etc/hostname6.interface

   Interface

   Interface name, such as le0, le1.

3. Reboot.

   ---

   Note - The reboot process sends out router discovery packets. The router responds with a prefix. The response enables the node to configure the interfaces with an IP address. Rebooting also restarts key network daemons in IPv6 mode.

   ---

4. On a command line, display the IPv6 addresses.

   # ifconfig -a

5. Add the IPv6 address to the appropriate name service as follows:

   • For NIS and NIS+, see "How to Add IPv6 Addresses to NIS and NIS+".

   • For DNS, see "How to Add IPv6 Addresses to DNS".

How to Configure a Solaris IPv6 Router

1. Become superuser on the system that acts as a router.

2. Edit the file /etc/inet/ndpd.conf with subnet prefixes by adding one or more of the following entries.

   See the in.ndpd(1M) man page for a list of variables and allowable values. For more information about the ndpd.conf file, see the ndpd.conf(4) man page.

   1. Add entries that specify router behavior for all interfaces.

      ifdefault variable value

   2. Add entries that specify the default behavior of prefix advertisement.

      prefixdefault variable value

   3. Add sets per interface parameter entries.

      if interface variable value

   4. Add advertisements for each entry for interface prefix information.

      prefix prefix/length interface variable value

3. Reboot the system.

Note - Neighbor discovery (in.ndpd) relays the subnet address prefixes of the hosts to the hosts. Also, the next generation RIP routing protocol (in.ripngd) runs automatically.

Example--ndpd.conf Router Configuration File

# Send router advertisements out all NICs
ifdefault AdvSendAdvertisements on
# Advertise a global prefix and a 
# site local prefix on three interfaces.
# 0x9255 = 146.85
prefix 2:0:0:9255::0/64	 	hme0
prefix fec0:0:0:9255::0/64 	hme0
# 0x9256 = 146.86
prefix 2:0:0:9256::0/64 	hme1
prefix fec0:0:0:9256::0/64	hme1
# 0x9259 = 146.89
prefix 2:0:0:9259::0/64		hme2
prefix fec0:0:0:9259::0/64	hme2

How to Add IPv6 Addresses to NIS and NIS+

A new table has been added for NIS+ named ipnodes.org_dir. The table contains both IPv4 and IPv6 addresses for a host. The existing hosts.org_dir table, which contains only IPv4 addresses for a host, remains the same to facilitate existing applications. Both the hosts.org_dir and ipnodes.org_dir tables must be consistent with the IPv4 addresses. See "IPv6 Extensions to Solaris Name Services" for an overview.

Administration of the new ipnodes.org_dir table is similar to administering the hosts.org_dir. The same tools and utilities that are used in administering the previous NIS+ tables are valid for ipnodes.org_dir. See System Administration Guide: Naming and Directory Services for details on how to manipulate the NIS+ table.

The following procedure merges the entries from /etc/inet/ipnodes into the ipnodes.org_dir table (in verbose mode). The NIS+ table was probably created by nistbladm(1), nissetup(1M), or nisserver(1M).

• On a command line, type the following command:

  % nisaddent -mv -f /etc/inet/ipnodes ipnodes

Use the following procedure to display the ipnodes.org_dir table.

• On a command line, type the following command:

  % nisaddent -d ipnodes

Two new maps have been added for NIS: ipnodes.byname and ipnodes.byaddr. These maps contain both IPv4 and IPv6 host name and address associations. The hosts.byname and hosts.byaddr maps, which contain only IPv4 host name and address associations, remain the same to facilitate existing applications. Administration of the new maps is similar to the maintenance of the hosts.byname and hosts.byaddr older maps. Again, it is important that when you update the hosts maps with IPv4 addresses that the new ipnode maps are also updated with the same information.

Note - Tools that are aware of IPv6 use the new NIS maps and the new NIS+ tables.