Nodes With Multiple Network Interfaces
If a node contains more than one network interface, you must create additional /etc/hostname.interface files for the additional network interfaces.
IPv4 Behavior
For example, consider the system timbuktu, which is shown in Figure 4-1. This system has two network interfaces. This system also functions as a router. The primary network interface le0 is connected to network 192.9.200. The IP address of the system is 192.9.200.70. The host name for the system is timbuktu. The Solaris installation program creates the /etc/hostname.le0 file for the primary network interface. The installation program also enters the timbuktu host name in the file.
The second network interface is le1. This interface is connected to network 192.9.201. Although this interface is physically installed on the timbuktu system, the interface must have a separate IP address. Therefore, you have to create manually the /etc/hostname.le1 file for this interface. The entry in the file is the name of the router, timbuktu-201.
IPv6 Behavior
If IPv6 is to be configured, only the interfaces for /etc/hostname6.le0 and /etc/hostname6.le1 must exist. Each interface address is configured automatically when the system is started.
IPv6 Daemons
This section describes the following IPv6 daemons:
in.ndpd - Daemon for IPv6 autoconfiguration
in.ripngd - Network routing daemon for IPv6
inetd - Internet services daemon
in.ndpd Daemon
This daemon implements router discovery and auto-address configuration for IPv6. The following table shows the supported options.
Table 16-2 in.ndpd Daemon Options
Option | Description |
|---|---|
-d | Turns on debugging for all events |
-D | Turns on specific debugging |
-f | File to read configuration from (instead of default file) |
-I | Prints related information for each interface |
-n | Does not loop back router advertisements |
-r | Ignores received packets |
-v | Verbose mode (reports various types of diagnostic messages) |
-t | Turns on packet tracing |
Parameters control the actions in.ndpd. Those parameters are set in the /etc/inet/ndpd.conf configuration file and the /var/inet/ndpd_state.interface startup file (if the parameters exist).
When the /etc/inet/ndpd.conf file exists, the file is parsed and used to configure a node as a router. The following table lists the valid keywords that might appear in this file. When a host is booted, routers might not be immediately available, or advertised packets by the router might be dropped and might not reach the host. The /var/inet/ndpd_state.interface file is a state file. This file is updated periodically by each node. When the node fails and is restarted, the node can configure its interfaces in the absence of routers. This file contains the interface address, the time that the file is updated, and how long the file is valid. This file also contains other parameters that are "learned" from previous router advertisements.
Note - You do not need to alter the contents of the state files. The in.ndpd daemon automatically maintains the state files.
Table 16-3 /etc/inet/ndpd.conf Keywords
Keywords | Description |
|---|---|
ifdefault | Specifies router behavior for all interfaces. Use the following syntax to set router parameters and corresponding values: ifdefault [variable value] |
prefixdefault | Specifies the default behavior for prefix advertisements. Use the following syntax to set router parameters and corresponding values: prefixdefault [variable value] |
if | Sets per-interface parameters. Use the following syntax: if interface [variable value] |
prefix | Advertises per-interface prefix information. Use the following syntax: prefix prefix/length interface [variable value] |
Note - The ifdefault/prefixdefault entries must precede the if and prefix entries in the configuration file.
See the in.ndpd(1M) man page and see also the ndpd.conf(4) man page for a list of configuration variables and allowable values.
Example--/etc/inet/ndpd.conf File
The following example provides a template of commented lines and also shows an example of how the keywords and configuration variables are used.
# ifdefault [variable value]* # prefixdefault [variable value]* # if ifname [variable value]* # prefix prefix/length ifname # # Per interface configuration variables # #DupAddrDetectTransmits #AdvSendAdvertisements #MaxRtrAdvInterval #MinRtrAdvInterval #AdvManagedFlag #AdvOtherConfigFlag #AdvLinkMTU #AdvReachableTime #AdvRetransTimer #AdvCurHopLimit #AdvDefaultLifetime # # Per Prefix: AdvPrefixList configuration variables # # #AdvValidLifetime #AdvOnLinkFlag #AdvPreferredLifetime #AdvAutonomousFlag #AdvValidExpiration #AdvPreferredExpiration ifdefault AdvReachableTime 30000 AdvRetransTimer 2000 prefixdefault AdvValidLifetime 240m AdvPreferredLifetime 120m if qe0 AdvSendAdvertisements 1 prefix 2:0:0:56::/64 qe0 prefix fec0:0:0:56::/64 qe0 if qe1 AdvSendAdvertisements 1 prefix 2:0:0:55::/64 qe1 prefix fec0:0:0:56::/64 qe1 if qe2 AdvSendAdvertisements 1 prefix 2:0:0:54::/64 qe2 prefix fec0:0:0:54::/64 qe2 |
in.ripngd Daemon
The in.ripngd daemon implements the RIP next-generation routing protocol for IPv6 routers. RIP next generation defines the IPv6 equivalent of RIP. RIP is a widely used IPv4 routing protocol that is based on the Bellman-Ford distance vector algorithm. The following table shows the supported options.
Table 16-4 in.ripngd Daemon Options
Option | Description |
-p n | n specifies the alternate port number that is used to send/receive RIPNG packets. |
-q | Suppresses routing information. |
-s | Forces routing information whether the daemon is acting as a router. |
-P | Suppresses use of poison reverse. |
-S | If in.ripngd does not act as a router, the daemon enters only a default route for each router. |