TCP/IP network administration evolves in two stages. The first stage is to assemble the hardware. Then, you configure the daemons, files, and services that implement the TCP/IP protocol.This chapter explains how to configure TCP/IP on a network that implements IPv4 addressing and services.Many of the tasks in this chapter apply to both IPv4-only and IPv6-enabled networks. Where configuration tasks differ between the two addressing formats, the IPv4 configuration steps are in this chapter. The tasks in this chapter then cross reference the equivalent IPv6 tasks in Chapter 7, Enabling IPv6 on a Network (Tasks). This chapter contains the following information:Before You Configure an IPv4 Network (Task Map) Determining Host Configuration Modes Adding a Subnet to a Network (Task Map) Configuring Systems on the Local Network Network Configuration Task Map Packet Forwarding and Routing on IPv4 Networks Monitoring and Modifying Transport Layer Services In Solaris Express, Developer Edition 2/07 and subsequent releases, you can configure and manage routing through the Service Management Facility (SMF) as an alternative to using the routeadm command. For instructions, refer to the procedures and examples in Packet Forwarding and Routing on IPv4 Networksand the routeadm1M man page. Before you configure TCP/IP, complete the tasks that are listed in the following table. Task Description For Instructions 1. Design the network topology. Determine the physical layout of the network. Network Topology Overview. 2. Obtain a network number from your ISP or Regional Internet Registry (RIR). Get a registered network number, which enables systems at your site to communicate externally. Designing Your IPv4 Addressing Scheme. 3. Plan the IPv4 addressing scheme for the network. If applicable, include subnet addressing. Use the network number as the basis for your addressing plan. Designing Your IPv4 Addressing Scheme. 4. Assemble the network hardware depending on the network topology. Assure that the hardware is functioning properly. Set up the systems, network media, routers, switches, hubs and bridges that you outlined in the network topology design. The hardware manuals and Network Topology Overview. 5. Assign IPv4 addresses and host names to all systems in the network. Assign the IPv4 addresses during Solaris OS installation or post installation, in the appropriate files. Designing Your IPv4 Addressing Scheme and How to Change the IPv4 Address and Other Network Configuration Parameters 6. Run configuration software that is required by network interfaces and routers, if applicable. Configure routers and multihomed hosts. Planning for Routers on Your Network and Configuring an IPv4 Router for information on routers. 7. Determine which name service or directory service your network uses: NIS, LDAP, DNS, or local files. Configure your selected name service and/or directory service. System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP). 8. Select domain names for your network, if applicable. Choose a domain name for your network and register it with the InterNIC. System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) As a network administrator, you configure TCP/IP to run on hosts and routers (if applicable). You can configure these systems to obtain configuration information from files on the local system or from files that are located on other systems on the network. You need the following configuration information: Host name of each system IP address of each system Domain name to which each system belongs Default router IPv4 netmask in use on each system's network A system that obtains TCP/IP configuration information from local files operates in local files mode. A system that obtains TCP/IP configuration information from a remote network server operates in network client mode.To run in local files mode, a system must have local copies of the TCP/IP configuration files. These files are described in TCP/IP Configuration Files. The system should have its own disk, though this recommendation is not strictly necessary.Most servers should run in local files mode. This requirement includes the following servers:Network configuration servers NFS servers Name servers that supply NIS, LDAP, or DNS services Mail servers Additionally, routers should run in local files mode. Systems that function exclusively as print servers do not need to run in local files mode. Whether individual hosts should run in local files mode depends on the size of your network.If you are running a very small network, the amount of work that is involved in maintaining these files on individual hosts is manageable. If your network serves hundreds of hosts, the task becomes difficult, even with the network divided into a number of administrative subdomains. Thus, for large networks, using local files mode is usually less efficient. However, because routers and servers must be self-sufficient, they should be configured in local files mode.Network configuration servers are the servers that supply the TCP/IP configuration information to hosts that are configured in network client mode. These servers support three booting protocols: RARP – Reverse Address Resolution Protocol (RARP) maps Ethernet addresses (48 bits) to IPv4 addresses (32 bits), which is the reverse of ARP. When you run RARP on a network configuration server, hosts that are running in network client mode obtain their IP addresses and TCP/IP configuration files from the server. The in.rarpd daemon enables RARP services. Refer to the in.rarpd1M man page for details. TFTP – The Trivial File Transfer Protocol (TFTP) is an application that transfers files between remote systems. The in.tftpd daemon executes TFTP services, enabling file transfer between network configuration servers and their network clients. Refer to the in.tftpd1M man page for details. Bootparams – The Bootparams protocol supplies parameters for booting that are required by clients that boot off the network. The rpc.bootparamd daemon executes these services. Refer to the bootparamd1M man page for details. Network configuration servers can also function as NFS file servers.If you are configuring any hosts as network clients, then you must also configure at least one system on your network as a network configuration server. If your network is subnetted, then you must have at least one network configuration server for each subnet with network clients. Any host that obtains its configuration information from a network configuration server operates in network client mode. Systems that are configured as network clients do not require local copies of the TCP/IP configuration files. Network client mode simplifies administration of large networks. Network client mode minimizes the number of configuration tasks that you perform on individual hosts. Network client mode assures that all systems on the network adhere to the same configuration standards.You can configure network client mode on all types of computers. For example, you can configure network client mode on standalone systems. Configurations are not limited to either an all-local-files mode or an all-network-client mode. Routers and servers should always be configured in local mode. For hosts, you can use any combination of local files and network client mode. Figure 5–1 shows the hosts of a fictitious network with the network number 192.9.200. The network has one network configuration server, which is called sahara. Hosts tenere and nubian have their own disks and run in local files mode. Host faiyum also has a disk, but this system operates in network client mode. Finally, the system timbuktu is configured as a router. The system includes two network interfaces. The first interface is named timbuktu. This interface belongs to network 192.9.200. The second interface is named timbuktu-201. This interface belongs to network 192.9.201. Both networks are in the organizational domain deserts.worldwide.com. The domain uses local files as its name service.

Diagram shows a sample network with one network server that serves four hosts.

If you are changing from a network that does not use a subnet to a network that does use a subnet, perform the tasks in the following task map.The information in this section applies to IPv4 subnets only. For information on planning IPv6 subnets, refer to Preparing the Network Topology for IPv6 Support and Creating a Numbering Scheme for Subnets. Task Description For Instructions 1. Determine if your network topology requires subnets. Decide on the new subnet topology, including where to locate routers and hosts on the subnets. Planning for Routers on Your Network, What Is Subnetting?, and Network Classes 2. Assign the IP addresses with the new subnet number to the systems to become members of the subnet. Configure IP addresses that use the new subnet number, either during Solaris OS installation or later, in the /etc/hostname.interface file. Deciding on an IP Addressing Format for Your Network 3. Configure the network mask of the subnet on all prospective systems in the subnet. Modify the /etc/inet/netmasks file, if you are manually configuring network clients. Or, supply the netmask to the Solaris installation program. netmasks Database and Creating the Network Mask for IPv4 Addresses 4. Edit the network databases with the new IP addresses of all systems in the subnet. Modify /etc/inet/hosts on all hosts to reflect the new host addresses. hosts Database 5. Reboot all systems. Task Description For Instructions Configure a host for local files mode Involves editing the nodename, hostname, hosts, defaultdomain, defaultrouter, and netmasks files How to Configure a Host for Local Files Mode Set up a network configuration server Involves turning on the in.tftp daemon, and editing the hosts, ethers, and bootparams files How to Set Up a Network Configuration Server Configure a host for network client mode Involves creating the hostname file, editing the hosts file, and deleting the nodename and defaultdomain files, if they exist How to Configure Hosts for Network Client Mode Specify a routing strategy for the network client Involves determining whether to use static routing or dynamic routing on the host. How to Enable Static Routing on a Single-Interface Host and How to Enable Dynamic Routing on a Single-Interface Host. Modify the existing network configuration Involves changing the host name, IP address, and other parameters that were set at installation or configured at a later time. How to Change the IPv4 Address and Other Network Configuration Parameters Network software installation occurs along with the installation of the operating system software. At that time, certain IP configuration parameters must be stored in appropriate files so that they can be read at boot time. The network configuration process involves creating or editing the network configuration files. How configuration information is made available to a system's kernel is conditional. The availability depends on whether these files are stored locally (local files mode) or acquired from the network configuration server (network client mode).The parameters that are supplied during network configuration follow: The IP address of each network interface on every system. The host names of each system on the network. You can type the host name in a local file or a name service database. The NIS, LDAP, or DNS domain name in which the system resides, if applicable. The default router addresses. You supply this information if you have a simple network topology with only one router attached to each network. You also supply this information if your routers do not run routing protocols such as the Router Discovery Server Protocol (RDISC) or the Router Information Protocol (RIP). For more information on default routers, refer to Packet Forwarding and Routing on IPv4 Networks See Table 5–1 for a list of routing protocols supported in the Solaris OS. Subnet mask (required only for networks with subnets). If the Solaris installation program detects more one interface on the system, you can optionally configure the additional interfaces during installation. For complete instructions, see Solaris Express Installation Guide: Basic Installations.This chapter contains information on creating and editing local configuration files. See System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) for information on working with name service databases.Use this procedure for configuring TCP/IP on a host that runs in local files mode. Assume the Primary Administrator role, or become superuser The Primary Administrator role includes the Primary Administrator profile. To create the role and assign the role to a user, see Chapter 2, Working With the Solaris Management Console (Tasks), in System Administration Guide: Basic Administration. Change to the /etc directory. Verify that the correct host name is set in the /etc/nodename file.When you specify the host name of a system during Solaris installation, that host name is entered into the /etc/nodename file. Make sure that the node name entry is the correct host name for the system. Verify that an /etc/hostname.interface file exists for each network interface on the system.For file syntax and basic information about the /etc/hostname.interface file, refer to Basics for Administering Physical Interfaces.The Solaris installation program requires you to configure at least one interface during installation. The first interface that you configure automatically becomes the primary network interface. The installation program creates an /etc/hostname.interface file for the primary network interface and any other interfaces that you optionally configure at installation time. If you configured additional interfaces during installation, verify that each interface has a corresponding /etc/hostname.interface file. You do not need to configure more than one interface during Solaris installation. However, if you later want to add more interfaces to the system, you must manually configure them.For steps for manually configuring interfaces, refer to How to Configure a Physical Interface After System Installation, for releases starting with Solaris 10 1/06. Verify that the entries in the /etc/inet/hosts file are current.The Solaris installation program creates entries for the primary network interface, loopback address, and, if applicable, any additional interfaces that were configured during installation.Make sure that the existing entries in /etc/inet/hosts are current. (Optional) Add the IP addresses and corresponding names for any network interfaces that were added to the local host after installation. (Optional) Add the IP address or addresses of the file server, if the /usr file system is NFS mounted. Type the host's fully qualified domain name in the /etc/defaultdomain file. For example, suppose host tenere was part of the domain deserts.worldwide.com. Therefore, you would type deserts.worldwide.com in /etc/defaultdomain. See /etc/defaultdomain File for more information. Type the router's name in the /etc/defaultrouter file. See /etc/defaultrouter File for information about this file. Type the name of the default router and its IP addresses in the /etc/inet/hosts file. Additional routing options are available, as discussed in How to Configure Hosts for Network Client Mode. You can apply these options to a local files mode configuration. Add the network mask for your network, if applicable:If the host gets its IP address from a DHCP server, you do not have to specify the network mask. If you have set up a NIS server on the same network as this client, you can add netmask information into the appropriate database on the server. For all other conditions, do the following: Type the network number and the netmask in the /etc/inet/netmasks file.Use the following format:network-number netmaskFor example, for the Class C network number 192.168.83, you would type:192.168.83.0 255.255.255.0For CIDR addresses, convert the network prefix into the equivalent dotted decimal representation. Network prefixes and their dotted decimal equivalents can be found in Table 2–3. For example, use the following to express the CIDR network prefix 192.168.3.0/22.192.168.3.0 255.255.252.0 Change the lookup order for netmasks in /etc/nsswitch.conf, so that local files are searched first:netmasks: files nis Reboot the system. Information for setting up installation servers and boot servers is found in Solaris Express Installation Guide: Basic Installations. Assume the Primary Administrator role, or become superuser.The Primary Administrator role includes the Primary Administrator profile. To create the role and assign the role to a user, see Chapter 2, Working With the Solaris Management Console (Tasks), in System Administration Guide: Basic Administration. Change to the root (/) directory of the prospective network configuration server. Turn on the in.tftpd daemon by creating the directory /tftpboot: # mkdir /tftpbootThis command configures the system as a TFTP, bootparams, and RARP server. Create a symbolic link to the directory.# ln -s /tftpboot/. /tftpboot/tftpboot Enable the tftp line in the /etc/inetd.conf file. Check that the entry reads as follows:tftp dgram udp6 wait root /usr/sbin/in.tftpd in.tftpd -s /tftpbootThis line prevents in.tftpd from retrieving any file other than the files that are located in /tftpboot. Edit the hosts database.Add the host names and IP addresses for every client on the network. Edit the ethers database.Create entries for every host on the network that runs in network client mode. Edit the bootparams database.See bootparams Database. Use the wildcard entry or create an entry for every host that runs in network client mode. Convert the /etc/inetd.conf entry into a Service Management Facility (SMF) service manifest, and enable the resulting service:# /usr/sbin/inetconv Verify that in.tftpd is working correctly.# svcs network/tftp/udp6You should receive output resembling the following:STATE STIME FMRI online 18:22:21 svc:/network/tftp/udp6:default The in.tftpd daemon is managed by the Service Management Facility. Administrative actions on in.tftpd, such as enabling, disabling, or restarting, can be performed using the svcadm command. Responsibility for initiating and restarting this service is delegated to inetd. Use the inetadm command to make configuration changes and to view configuration information for in.tftpd. You can query the service's status by using the svcs command. For an overview of the Service Management Facility, refer to Chapter 14, Managing Services (Overview), in System Administration Guide: Basic Administration. Network clients receive their configuration information from network configuration servers. Therefore, before you configure a host as a network client you must ensure that at least one network configuration server is set up for the network. Do the following procedure on each host to be configured in network client mode. Assume the Primary Administrator role, or become superuser.The Primary Administrator role includes the Primary Administrator profile. To create the role and assign the role to a user, see Chapter 2, Working With the Solaris Management Console (Tasks), in System Administration Guide: Basic Administration. Search the /etc directory for the nodename file. If such a file exists, delete it.Eliminating /etc/nodename causes the system to use the hostconfig program to obtain the host name, domain name, and router addresses from the network configuration server. See Configuring Systems on the Local Network . Create the /etc/hostname.interface file, if it does not exist. Ensure that the file is empty. An empty /etc/hostname.interface file causes the system to acquire the IPv4 address from the network configuration server. Ensure that the /etc/inet/hosts file contains only the localhost name and IP address of the loopback network interface. # cat /etc/inet/hosts # Internet host table # 127.0.0.1 localhostThe IPv4 loopback interface has the IP address 127.0.0.1.For more information, see Loopback Address. The file should not contain the IP address and host name for the local host (primary network interface). Check for the existence of an /etc/defaultdomain file.If such a file exists, delete it.The hostconfig program automatically sets the domain name. To override the domain name that is set by hostconfig, type the substitute domain name in the /etc/defaultdomain file. Ensure that the search paths in the client's /etc/nsswitch.conf file reflect the name service requirements for your network. This procedure explains how to modify the IPv4 address, host name, and other network parameters on a previously installed system. Use the procedure for modifying the IP address of a server or networked standalone system. The procedure does not apply to network clients or appliances. The steps create a configuration that persists across reboots. The instructions apply specifically to changing the IPv4 address of the primary network interface. To add another interface to the system, refer to How to Configure a Physical Interface After System Installation. In almost all cases, the following steps use traditional IPv4 dotted decimal notation to specify the IPv4 address and subnet mask. Alternatively, you can use CIDR notation to specify the IPv4 address in all the applicable files in this procedure. For an introduction to CIDR notation, see IPv4 Addresses in CIDR Format. Assume the Primary Administrator role, or become superuser.The Primary Administrator role includes the Primary Administrator profile. To create the role and assign the role to a user, see Chapter 2, Working With the Solaris Management Console (Tasks), in System Administration Guide: Basic Administration. If the system's host name must change, modify the host name entry in the /etc/nodename file. Modify the IP address and, if applicable, the host name in the /etc/inet/hosts file or equivalent hosts database. Modify the IP address in the /etc/hostname.interface file for the primary network interface.You can use any of the following as the entry for the primary network interface in the /etc/hostnameinterface file:IPv4 address, expressed in traditional dotted decimal formatUse the following syntax:IPv4 address (Optional) subnet maskHere is an example:# vi hostname.eri0 10.0.2.5 netmask + 255.0.0.0The netmask entry is optional. If you do not specify it, the default netmask is assumed. IPv4 address, expressed in CIDR notation, if appropriate for your network configuration.IPv4 address/network prefixHere is an example:# vi hostname.eri0 10.0.2.5/8The CIDR prefix designates the appropriate netmask for the IPv4 address. For example, the /8 above indicates the netmask 255.0.0.0. Host name.To use the system's host name in the /etc/hostname.interface file, be sure that the host name and associated IPv4 address are also in the hosts database. If the subnet mask has changed, modify the subnet entries in the following files:/etc/netmasks (Optional) /etc/hostname.interface If the subnet address has changed, change the IP address of the default router in /etc/defaultrouter to that of the new subnet's default router. Reboot the system.# reboot -- -r This example shows how to change the following network parameters of a system that is moved to another subnet:IP address for the primary network interface eri0 changes from 10.0.0.14 to 192.168.55.14. Host name changes from myhost to mynewhostname. Netmask changes from 255.0.0.0 to 255.255.255.0. Default router address changes to 192.168.55.200. Check the system's current status:# hostname myhost # ifconfig -a lo0: flags=1000849 <UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 eri0: flags=1000843 <UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 10.0.0.14 netmask ff000000 broadcast 10.255.255.255 ether 8:0:20:c1:8b:c3 Next, change the system's host name and the IP address of eri0 in the appropriate files:# vi /etc/nodename mynewhostname # vi /etc/inet/hosts # # Internet host table # 127.0.0.1 localhost 192.168.55.14 mynewhostname loghost # vi /etc/hostname.eri0 192.168.55.14 netmask + 255.255.255.0Finally, change the netmask and the IP address of the default router.# vi /etc/netmasks. . . 192.168.55.0 255.255.255.0 # vi /etc/defaultrouter 192.168.55.200 #moved system to 192.168.55 net #After making these changes, reboot the system.# reboot -- -rVerify that the configuration you just set is maintained after the reboot:# hostname mynewhostname # ifconfig -a lo0: flags=1000849 <UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 eri0: flags=1000843 <UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 192.168.55.14 netmask ffffff00 broadcast 10.255.255.255 ether 8:0:20:c1:8b:c3 This example shows how to change a host's name, IP address of the primary network interface, and subnet mask for the current session only. If you reboot, the system reverts to its previous IP address and subnet mask. The IP address for the primary network interface eri0 changes from 10.0.0.14 to 192.168.34.100.# ifconfig -alo0: flags=1000849 <UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 eri0: flags=1000843 <UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 10.0.0.14 netmask ff000000 broadcast 10.255.255.255 ether 8:0:20:c1:8b:c3 # ifconfig eri0 192.168.34.100 netmask 255.255.255.0 broadcast + up # vi /etc/nodename mynewhostname # ifconfig -a lo0: flags=1000849 <UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 eri0: flags=1000843 <UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 192.168.34.100 netmask ffffff00 broadcast 10.255.255.255 ether 8:0:20:c1:8b:c3 # hostname mynewhostname This example shows how to change a host name and IP address for the current session only, using CIDR notation. If you reboot, the system reverts to its previous IP address and subnet mask. The IP address for the primary network interface, eri0, changes from 10.0.0.14 to 192.168.6.25/27.# ifconfig -a lo0: flags=1000849 <UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 eri0: flags=1000843 <UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 10.0.0.14 netmask ff000000 broadcast 10.255.255.255 ether 8:0:20:c1:8b:c3 # ifconfig eri0 192.168.6.25/27 broadcast + up # vi /etc/nodename mynewhostname # ifconfig -a lo0: flags=1000849 <UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 eri0: flags=1000843 <UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 192.168.06.25 netmask ffffffe0 broadcast 10.255.255.255 ether 8:0:20:c1:8b:c3 # hostname mynewhostnameWhen you use CIDR notation for the IPv4 address, you do not have to specify the netmask. ifconfig uses the network prefix designation to determine the netmask. For example, for the 192.168.6.0/27 network, ifconfig sets the netmask ffffffe0. If you had used the more common /24 prefix designation, the resulting netmask is ffffff00. Using the /24 prefix designation is the equivalent of specifying the netmask 255.255.255.0 to ifconfig when configuring a new IP address. To change the IP address of an interface other than the primary network interface, refer to System Administration Guide: Basic Administration and How to Configure a Physical Interface After System Installation. This section contains procedures and examples that show how to configure forwarding and routing for routers and hosts on IPv4 networks.Packet forwarding is the basic method for sharing information across systems on a network. Packets are transferred between a source interface and a destination interface, usually on two different systems. When you issue a command or send a message to a nonlocal interface, your system forwards those packets onto the local network. The interface with the destination IP address that is specified in the packet headers then retrieves the packets from the local network. If the destination address is not on the local network, the packets are then forwarded to the next adjacent network, or hop. By default, packet forwarding is automatically configured when you install the Solaris OS.Routing is the process by which systems decide where to send a packet. Routing protocols on a system “discover” the other systems on the local network. When the source system and the destination system are on the same local network, the path that packets travel between them is called a direct route. If a packet must travel at least one hop beyond its source system, the path between the source system and destination system is called an indirect route. The routing protocols learn the path to a destination interface and retain data about known routes in the system's routing table. Routers are specially configured systems with multiple physical interfaces that connect the router to more than one local network. Therefore, the router can forward packets beyond the home LAN, regardless of whether the router runs a routing protocol. For more information about how routers forward packets, refer to Planning for Routers on Your Network. Routing protocols handle routing activity on a system and, by exchanging routing information with other hosts, maintain known routes to remote networks. Both routers and hosts can run routing protocols. The routing protocols on the host communicate with routing daemons on other routers and hosts. These protocols assist the host in determining where to forward packets. When network interfaces are enabled, the system automatically communicates with the routing daemons. These daemons monitor routers on the network and advertise the routers' addresses to the hosts on the local network. Some routing protocols, though not all, also maintain statistics that you can use to measure routing performance. Unlike packet forwarding, you must explicitly configure routing on a Solaris system. This section contains tasks for administering packet forwarding and routing on IPv4 routers and hosts. For information about routing on an IPv6-enabled network, refer to Configuring an IPv6 Router.Routing protocols are classified as interior gateway protocols (IGPs), exterior gateway protocols (EGPs), or a combination of both. Interior gateway protocols exchange routing information between routers on networks under common administrative control. In the network topology shown in Figure 5–2, the routers run an IGP for exchanging routing information. Exterior gateway protocols enable the router that connects the local internetwork to an external network to exchange information with another router on the external network. For example, the router that connects a corporate network to an ISP runs an EGP to exchange routing information with its router counterpart at the ISP. Border Gateway Protocol (BGP) is a popular EGP that is used for carrying routing information between different organizations and IGPs.The following table provides information about the Solaris routing protocols and the location of each protocol's associated documentation. Protocol Associated Daemon Description For Instructions Routing Information Protocol (RIP) in.routed IGP that routes IPv4 packets and maintains a routing table How to Configure an IPv4 Router Internet Control Message Protocol (ICMP) Router Discovery in.routed Used by hosts to discover the presence of a router on the network How to Enable Static Routing on a Single-Interface Host and How to Enable Dynamic Routing on a Single-Interface Host Routing Information Protocol, next generation (RIPng) Protocol in.ripngd IGP that routes IPv6 packets and maintains a routing table How to Configure an IPv6-Enabled Router Neighbor Discovery (ND) Protocol in.ndpd Advertises the presence of an IPv6 router and discovers the presence of IPv6 hosts on a network Configuring an IPv6 Interface Sites with multiple routers and networks typically administer their network topology as a single routing domain, or autonomous system (AS) . The following figure shows a typical network topology that would be considered a small AS. This topology is referenced in the examples throughout this section.

This topology diagram of an autonomous system is explained in the following context.

The figure shows an AS that is divided into three local networks, 10.0.5.0, 172.20.1.0, and 192.168.5. Four routers share packet-forwarding and routing responsibilities. The AS includes the following types of systems:Border routers connect an AS to an external network, such as the Internet. Border routers interconnect with networks external to the IGP running on the local AS. A border router can run an EGP, such as Border Gateway Protocol (BGP), to exchange information with external routers, for example, the routers at the ISP. In Figure 5–2, the border router's interfaces connect to internal network 10.0.5.0 and to a high-speed router to a service provider.For information on configuring a border router, refer to the Open Source Quagga documentation for BGP. If you plan to use BGP to connect your AS to the Internet, you should obtain an autonomous system number (ASN) from the Internet Registry for your locale. Regional registries, such as the American Registry for Internet Numbers (ARIN), offer guidelines on how to obtain an ASN. For example, the ARIN Number Resource Policy Manual contains instructions for getting an ASN for autonomous systems in the United States and Canada. Alternatively, your ISP might be able to obtain an ASN for you. Default routers maintain routing information about all the systems on the local network. These routers typically run IGPs such as RIP. In Figure 5–2, Router 1s interfaces are connected to internal network 10.0.5.0 and internal network 192.168.5. Router 1 also serves as the default router for 192.168.5. Router 1 maintains routing information for all systems on 192.168.5 and routes to other routers, such as the border router. Router 2s interfaces connect to internal network 10.0.5.0 and internal network 172.20.1. For an example of configuring a default router, refer to Example 5–4. Packet-forwarding routers forward packets but do not run routing protocols. This type of router receives packets from one of its interfaces that is connected to a single network. These packets are then forwarded through another interface on the router to another local network. In Figure 5–2, Router 3 is a packet-forwarding router with connections to networks 172.20.1 and 192.168.5. Multihomed hosts have two or more interfaces that are connected to the same network segment. A multihomed host can forward packets, which is the default for all systems that run the Solaris OS. Figure 5–2 shows a multihomed host with both interfaces connected to network 192.168.5. For an example of configuring a multihomed host, refer to Example 5–6. Single interface hosts rely on the local routers, not only for packet forwarding but also for receiving valuable configuration information. Figure 5–2 includes Host A on the 192.168.5 network, which implements dynamic routing, and Host B on the 172.20.1 network, which implements static routing. To configure a host to run dynamic routing, refer to How to Enable Dynamic Routing on a Single-Interface Host. To configure a host to run static routing, refer to How to Enable Static Routing on a Single-Interface Host. This section contains a procedure and example for configuring an IPv4 router. To configure an IPv6-enabled router, refer to How to Configure an IPv6-Enabled Router.Because a router provides the interface between two or more networks, you must assign a unique name and IP address to each of the router's physical network interfaces. Thus, each router has a host name and an IP address that are associated with its primary network interface, in addition to a minimum of one more unique name and IP address for each additional network interface. You can also use the following procedure to configure a system with only one physical interface (by default, a host) to be a router. You might configure a single interface system as a router if the system serves as one endpoint on a PPP link, as explained in Planning a Dial-up PPP Link in System Administration Guide: Network Services. You can configure all interfaces of a router during Solaris system installation. For instructions, see Solaris Express Installation Guide: Basic Installations. The following instructions assume that you are configuring interfaces for the router after installation. After the router is physically installed on the network, configure the router to operate in local files mode, as described in How to Configure a Host for Local Files Mode. This configuration ensures that routers boot if the network configuration server is down. On the system to be configured as a router, assume the Primary Administrator role or become superuser.The Primary Administrator role includes the Primary Administrator profile. To create the role and assign the role to a user, see Chapter 2, Working With the Solaris Management Console (Tasks), in System Administration Guide: Basic Administration. Use the dladm show-link command to determine which interfaces are physically installed on the router.# dladm show-linkThe following example output from dladm show-link indicates that a qfe NIC with four interfaces and two bge interfaces are physically available on the system.qfe0 type: legacy mtu: 1500 device: qfe0 qfe1 type: legacy mtu: 1500 device: qfe1 qfe2 type: legacy mtu: 1500 device: qfe0 qfe3 type: legacy mtu: 1500 device: qfe1 bge0 type: non-vlan mtu: 1500 device: bge0 bge1 type: non-vlan mtu: 1500 device: bge1 Review which interfaces on the router were configured and plumbed during installation.# ifconfig -aThe following example output from ifconfig -a shows that the interface qfe0 was configured during installation. This interface is on the 172.16.0.0 network. The remaining interfaces on the qfe NIC, qfe1 - qfe3, and the bge interfaces have not been configured.lo0: flags=1000849 <UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 qfe0: flags=1000843 <UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 172.16.26.232 netmask ffff0000 broadcast 172.16.26.255 ether 0:3:ba:11:b1:15 Configure and plumb another interface.# ifconfig interface plumb upFor example, for qfe1, you would type:# ifconfig qfe1 plumb upInterfaces that are explicitly configured with the ifconfig command do not persist across reboots. Assign an IPv4 address and a netmask to the interface.You can configure an IPv4 routers to receive its IP address through DHCP, but this is recommended only for very experienced DHCP system administrators. # ifconfig interface IPv4-address netmask+netmaskFor example, to assign the IP address 192.168.84.3 to qfe1, do either of the following:Using traditional IPv4 notation, type the following:# ifconfig qfe1 192.168.84.3 netmask + 255.255.255.0 Using CIDR notation, type the following:# ifconfig qfe1 192.168.84.3/24The prefix /24 automatically assigns the 255.255.255.0 netmask to qfe1. For a table of CIDR prefixes and their dotted-decimal netmask equivalents, refer to Figure 2–2. (Optional) To ensure that the interface configuration persists across reboots, create an /etc/hostname.interface file for each additional physical interface .For example, you would create the /etc/hostname.qfe1 and /etc/hostname.qfe2 files. Then you would type the host name timbuktu in /etc/hostname.qfe1 file and host name timbuktu-201 in /etc/hostname.qfe1 . For more information about configuring single interfaces, refer to How to Configure a Physical Interface After System Installation.Be sure to do a configuration reboot after creating this file:# reboot -- -r Add the host name and IP address of each interface to the /etc/inet/hosts file. For example:172.16.26.232 deadsea #interface for network 172.16.0.0 192.168.200.20 timbuktu #interface for network 192.168.200 192.168.201.20 timbuktu-201 #interface for network 192.168.201 192.168.200.9 gobi 192.168.200.10 mojave 192.168.200.110 saltlake 192.168.200.12 chileanThe interfaces timbuktu and timbuktu-201 are on the same system. Notice that the network address for timbuktu-201 is different from the network interface for timbuktu. The difference exists because the physical network media for network 192.168.201 is connected to the timbuktu-201 network interface while the media for network 192.168.200 is connected to the timbuktu interface. If the router is connected to any subnetted network, add the network number and the netmask to the /etc/inet/netmasks file.For traditional IPv4 address notation, such as 192.168.83.0, you would type:192.168.83.0 255.255.255.0 For CIDR addresses, use the dotted-decimal version of the prefix in the entry in the /etc/inet/netmask file. Network prefixes and their dotted-decimal equivalents can be found in Figure 2–2. For example, you would use the following entry in /etc/netmasks to express the CIDR network prefix 192.168.3.0/22:192.168.3.0 255.255.252.0 Enable IPv4 packet forwarding on the router.Use either of the following commands to enable packet forwarding:Use the routeadm command, as follows:# routeadm -e ipv4-forwarding -u Use the following service management facility (SMF) command:# svcadm enable ipv4-forwarding At this point, the router can forward packets beyond the local network. The router also supports static routing, a process where you can manually add routes to the routing table. If you plan to use static routing on this system, then router configuration is complete. However, you need to maintain routes in the system routing table. For information on adding routes, see Configuring Routes and the route1M man page. (Optional) Start arouting protocol.The routing daemon /usr/sbin/in.routed automatically updates the routing table, a process that is known as dynamic routing. Turn on the default IPv4 routing protocols in either of the following ways:Use the routeadm command, as follows:# routeadm -e ipv4-routing -u Use the following SMF command to start a routing protocol such as RIP.# svcadm enable route:default The SMF FMRI associated with the in.routed daemon is svc:/network/routing/route. For information about the routeadm command, see the routeadm1M man page. This example shows how to upgrade a system with more than one interface to become a default router. The goal is to make Router 2, which is shown in Figure 5–2, the default router for network 172.20.1.0. Router 2 contains two wired network connections, one connection to network 172.20.1.0 and one to network 10.0.5.0. The example assumes that the router operates in local files mode, as described in How to Configure a Host for Local Files Mode. After becoming superuser or assuming an equivalent role, you would determine out the status of the system's interfaces.# dladm show-link ce0 type: legacy mtu: 1500 device: ce0 bge0 type: non-vlan mtu: 1500 device: bge0 bge1 type: non-vlan mtu: 1500 device: bge1 # ifconfig -a lo0: flags=1000849 <UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 ce0: flags=1000843 <UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 172.20.1.10 netmask ffff0000 broadcast 172.20.10.100 ether 8:0:20:c1:1b:c6 The output of dladm show-link indicates that three links are available on the system. Only the ce0 interface has been plumbed. You would begin default router configuration by physically connecting the bge0 interface to the 10.0.5.0 network. Then, you would plumb the interface and make it persist across reboots.# ifconfig bge0 plumb up # ifconfig bge0 10.0.5.10 # ifconfig -a lo0: flags=1000849 <UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 ce0: flags=1000843 <UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 172.20.1.10 netmask ffff0000 broadcast 172.255.255.255 ether 8:0:20:c1:1b:c6 bge0: flags=1000843 <UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 10.0.5.10 netmask ff000000 broadcast 10.255.255.255 ether 8:0:20:e5:95:c4 # vi /etc/hostname.bge0 10.0.5.10 255.0.0.0Reboot the system, using the reconfiguration boot command:# reboot -- -rContinue by configuring the following network databases with information about the newly plumbed interface and the network to which it is connected:# vi /etc/inet/hosts 127.0.0.1 localhost 172.20.1.10 router2 #interface for network 172.20.1 10.0.5.10 router2-out #interface for network 10.0.5 # vi /etc/inet/netmasks 172.20.1.0 255.255.0.0 10.0.5.0 255.0.0.0Finally, use SMF to enable packet forwarding and then enable the in.routed routing daemon.# svcadm enable ipv4-forwarding # svcadm enable route:defaultNow IPv4 packet forwarding and dynamic routing through RIP are enabled on Router 2. However, the default router configuration for network 172.20.1.0 is not yet complete. You would need to do the following:Modify each host on 172.10.1.10 so that the host gets its routing information from the new default router. For more information, refer to How to Enable Static Routing on a Single-Interface Host. Define a static route to the border router in the routing table of Router 2. For more details, refer to Routing Tables and Routing Types. Both routers and hosts maintain a routing table. The routing daemon on each system updates the table with all known routes. The system's kernel reads the routing table before forwarding packets to the local network. The routing table lists the IP addresses of networks that the system knows about, including the system's local, default network. The table also lists the IP address of a gateway system for each known network. The gateway is a system that can receive outgoing packets and forward them one hop beyond the local network. The following is a simple routing table for a system on an IPv4-only network:Routing Table: IPv4 Destination Gateway Flags Ref Use Interface -------------------- -------------------- ----- ----- ------ --------- default 172.20.1.10 UG 1 532 ce0 224.0.0.0 10.0.5.100 U 1 0 bge0 10.0.0.0 10.0.5.100 U 1 0 bge0 127.0.0.1 127.0.0.1 UH 1 57 lo0You can configure two types of routing on a Solaris system: static and dynamic. You can configure either or both routing types on a single system. A system that implements dynamic routing relies on routing protocols, such as RIP for IPv4 networks, and RIPng for IPv6 networks, to maintain its routing tables. A system that runs only static routing does not rely on a routing protocol for routing information and for updating the routing table. Instead, you must maintain the system's known routes manually through the route command. For complete details, refer to the route1M man page.When you configure routing for the local network or autonomous system, consider which type of routing to support on particular routers and hosts.Routing Type Best Used on Static Small networks, hosts that get their routes from a default router, and default routers that only need to know about one or two routers on the next few hops. Dynamic Larger internetworks, routers on local networks with many hosts, and hosts on large autonomous systems. Dynamic routing is the best choice for systems on most networks. Combined static and dynamic Routers that connect a staticallyrouted network and a dynamically routed network, and border routers that connect an interior autonomous system with external networks. Combining both static and dynamic routing on a system is a common practice. The AS that is shown is Figure 5–2 combines both static and dynamic routing. To implement dynamic routing for an IPv4 network, use the routeadm or svcadm command to start the in.routed routing daemon. For instructions, see How to Configure an IPv4 Router. Dynamic routing is the preferred strategy for most networks and autonomous systems. However, your network topology or a particular system on your network might require static routing. In that case, you must manually edit the system routing table to reflect the known route to the gateway. The next procedure shows how to add a static route.Two routes to the same destination does not automatically cause the system to do load balancing or failover. If you need these capabilities, use IPMP, as explained in Chapter 30, Introducing IPMP (Overview). View the current state of the routing table.Use your regular user account to run the following form of the netstat command:% netstat -rnYour output would resemble the following:Routing Table: IPv4 Destination Gateway Flags Ref Use Interface -------------------- -------------------- ----- ----- ------ --------- 192.168.5.125 192.168.5.10 U 1 5879 ipge0 224.0.0.0 198.168.5.10 U 1 0 ipge0 default 192.168.5.10 UG 1 91908 127.0.0.1 127.0.0.1 UH 1 811302 lo0 Assume the Primary Administrator role or become superuser.The Primary Administrator role includes the Primary Administrator profile. To create the role and assign the role to a user, see Chapter 2, Working With the Solaris Management Console (Tasks), in System Administration Guide: Basic Administration. (Optional) Flush the existing entries in the routing table.# route flush Add a route that persists across system reboots.# route -p add -net network-address -gateway gateway-addresspCreates a route that must persist across system reboots. If you want the route to prevail only for the current session, do not use the p option. addIndicates that you are about to add the following route. netnetwork-addressSpecifies that the route goes to the network with the address in network-address. gatewaygateway-addressIndicates that the gateway system for the specified route has the IP address gateway-address. The following example shows how to add a static route to a system. The system is Router 2, the default router for the 172.20.1.0 network that is shown in Figure 5–2. In Example 5–4, Router 2 is configured for dynamic routing. To better serve as the default router for the hosts on network 172.20.1.0, Router 2 additionally needs a static route to the AS's border router, 10.0.5.150. To view the routing table on Router 2, you would do the following:# netstat -rn Routing Table: IPv4 Destination Gateway Flags Ref Use Interface -------------------- -------------------- ----- ----- ------ --------- default 172.20.1.10 UG 1 249 ce0 224.0.0.0 172.20.1.10 U 1 0 ce0 10.0.5.0 10.0.5.20 U 1 78 bge0 127.0.0.1 127.0.0.1 UH 1 57 lo0The routing table indicates two routes that Router 2 knows about. The default route uses Router 2's 172.20.1.10 interface as its gateway. The second route, 10.0.5.0, was discovered by the in.routed daemon running on Router 2. The gateway for this route is Router 1, with the IP address 10.0.5.20. To add a second route to network 10.0.5.0, which has its gateway as the border router, you would do the following:# route -p add -net 10.0.5.0/24 -gateway 10.0.5.150/24 add net 10.0.5.0: gateway 10.0.5.150Now the routing table has a route for the border router, which has the IP address 10.0.5.150/24.# netstat -rn Routing Table: IPv4 Destination Gateway Flags Ref Use Interface -------------------- -------------------- ----- ----- ------ --------- default 172.20.1.10 UG 1 249 ce0 224.0.0.0 172.20.1.10 U 1 0 ce0 10.0.5.0 10.0.5.20 U 1 78 bge0 10.0.5.0 10.0.5.150 U 1 375 bge0 127.0.0.1 127.0.0.1 UH 1 57 lo0 In the Solaris OS, a system with more than one interface is considered a multihomed host. A multihomed host does not forward IP packets. However, you can configure a multihomed host to run routing protocols. You typically configure the following types of systems as multihomed hosts: NFS servers, particularly those servers that function as large data centers, can be attached to more than one network in order to share files among a large pool of users. These servers do not need to maintain routing tables. Database servers can have multiple network interfaces to provide resources to a large pool of users, just like NFS servers. Firewall gateways are systems that provide the connection between a company's network and public networks such as the Internet. Administrators set up firewalls as a security measure. When configured as a firewall, the host does not pass packets between the networks that are attached to the host's interfaces. However, the host can still provide standard TCP/IP services, such as ssh to authorized users.When multihomed hosts have different types of firewalls on any of their interfaces, take care to avoid unintentional disruption of the host's packets. This problem arises particularly with stateful firewalls. One solution might be to configure stateless firewalling. For more information about firewalls, refer to Firewall Systems in System Administration Guide: Security Services or the documentation for your third-party firewall. On the prospective multihomed host, assume the Primary Administrator role, or become superuser.The Primary Administrator role includes the Primary Administrator profile. To create the role and assign the role to a user, see Chapter 2, Working With the Solaris Management Console (Tasks), in System Administration Guide: Basic Administration. Configure and plumb each additional network interface that was not configured as part of the Solaris OS installation. Refer to How to Configure a Physical Interface After System Installation. Verify that IP forwarding is not enabled on the multihomed host.# routeadm The routeadm command without options reports the state of the routing daemons. The following output from routeadm shows that IPv4 forwarding is enabled: Configuration Current Current Option Configuration System State --------------------------------------------------------------- IPv4 routing disabled disabled IPv6 routing disabled disabled IPv4 forwarding enabled disabled IPv6 forwarding disabled disabled Routing services "route:default ripng:default" Turn off packet forwarding, if it is enabled on the system.Use either of the following commands:For the routeadm command, type the following:# routeadm -d ipv4-forwarding -u To use SMF, type the following:# svcadm disable ipv4-forwarding (Optional) Turn on dynamic routing for the multihomed host.Use either of the following commands to enable the in.routed daemon:For the routeadm command, type the following:# routeadm -e ipv4-routing -u To use SMF, type the following:#svcadm enable route:default The following example shows how to configure the multihomed host that is shown in Figure 5–2. In the example, the system has the host name hostc. This host has two interfaces, which are both connected to network 192.168.5.0 .To begin, you would display the status of the system's interfaces.# dladm show-link hme0 type: legacy mtu: 1500 device: hme0 qfe0 type: legacy mtu: 1500 device: qfe0 qfe1 type: legacy mtu: 1500 device: qfe1 qfe2 type: legacy mtu: 1500 device: qfe2 qfe3 type: legacy mtu: 1500 device: qfe3 # ifconfig -a # ifconfig -a lo0: flags=1000849 <UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 hme0: flags=1000843 <UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 192.168.5.82 netmask ff000000 broadcast 192.255.255.255 ether 8:0:20:c1:1b:c6 The dladm show-link command reports that hostc has two interfaces with a total of five possible links. However, only hme0 has been plumbed. To configure hostc as a multihomed host, you must add qfe0 or another link on the qfe NIC . First, you would physically connect the qfe0 interface to the 192.168.5.0 network. Then you would plumb the qfe0 interface, and make the interface persist across reboots.# ifconfig qf0 plumb up # ifconfig qfe0 192.168.5.85 # ifconfig -a lo0: flags=1000849 <UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 hme0: flags=1000843 <UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 192.168.5.82 netmask ff0000 broadcast 192.255.255.255 ether 8:0:20:c1:1b:c6 qfe0: flags=1000843 <UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 192.168.5.85 netmask ff000000 broadcast 192.255.255.255 ether 8:0:20:e1:3b:c4 # vi /etc/hostname.qfe0 192.168.5.85 255.0.0.0Reboot the system, using the reconfiguration command:# reboot -- -rNext, you would add the qfe0 interface to the hosts database:# vi /etc/inet/hosts 127.0.0.1 localhost 192.168.5.82 host3 #primary network interface for host3 192.168.5.85 host3-2 #second interfaceThen, you would check the state of packet forwarding and routing on host3:# routeadm Configuration Current Current Option Configuration System State --------------------------------------------------------------- IPv4 routing enabled enabled IPv6 routing disabled disabled IPv4 forwarding enabled enabled IPv6 forwarding disabled disabled Routing services "route:default ripng:default"The routeadm command reports that dynamic routing through the in.routed daemon and packet forwarding are currently enabled. However, you would need to disable packet forwarding:# svcadm disable ipv4-forwardingYou can also use the routeadm commands as shown in How to Create a Multihomed Host to turn off packet forwarding. When packet forwarding is disabled, host3 becomes a multihomed host. Single-interface hostsneed to implement some form of routing. If the host is to obtain its routes from one or more local default routers, then you must configure the host to use static routing. Otherwise, dynamic routing is recommended for the host. The following procedures contain the instructions for enabling both routing types.This procedure enables static routing on a single-interface host. Hosts that use static routing do not run a dynamic routing protocolsuch as RIP. Instead, the host must rely on the services of a default router for routing information. The figure IPv4 Autonomous System Topology shows several default routers and their client hosts. If you supplied the name of a default router when you installed a particular host, that host is already configured to use static routing. You can also use the following procedure to configure static routing on a multihomed host. For information about the /etc/defaultrouter file, see /etc/defaultrouter File. For information about static routing and the routing table, refer to Routing Tables and Routing Types. On the single interface host, assume the Primary Administrator role, or become superuser.The Primary Administrator role includes the Primary Administrator profile. To create the role and assign the role to a user, see Chapter 2, Working With the Solaris Management Console (Tasks), in System Administration Guide: Basic Administration. Verify whether the /etc/defaultrouter file is present on the host.# cd /etc # ls | grep defaultrouter Open a text editor to create or modify the /etc/defaultrouter file Add an entry for thedefault router.# vi /etc/defaultrouter router-IP where router-IP indicates the IP address of the default router for the host to use. Verify that routing and packet forwarding are not running on the host.# routeadm Configuration Current Current Option Configuration System State --------------------------------------------------------------- IPv4 routing disabled disabled IPv6 routing disabled disabled IPv4 forwarding disabled disabled IPv6 forwarding disabled disabled Routing services "route:default ripng:default" Add an entry for the default router in the local /etc/inet/hosts file.For information about configuring /etc/inet/hosts, refer to How to Change the IPv4 Address and Other Network Configuration Parameters. The following example shows how to configure static routing for hostb, a single-interface host on the network 172.20.1.0 that is shown in Figure 5–2. hostb needs to use Router 2 as its default router.First, you would log in to hostb as superuser, or assume an equivalent role. Then, you would determine whether the /etc/defaultrouter file is present on the host:# cd /etc # ls | grep defaultrouterNo response from grep indicates that you need to create the /etc/defaultrouter file.# vi /etc/defaultrouter 172.20.1.10The entry in the /etc/defaultrouter file is the IP address of the interface on Router 2, which is attached to the 172.20.1.0 network. Next, you verify whether the host currently enables packet forwarding or routing.# routeadm Configuration Current Current Option Configuration System State --------------------------------------------------------------- IPv4 routing disabled disabled IPv6 routing disabled disabled IPv4 forwarding enabled enabled IPv6 forwarding disabled disabled Routing services "route:default ripng:default"Packet forwarding is enabled for this particular host. You would turn it off as follows:# svcadm disable ipv4-forwardingLastly, you would make sure that the host's /etc/inet/hosts file has an entry for the new default router.# vi /etc/inet/hosts 127.0.0.1 localhost 172.20.1.18 host2 #primary network interface for host2 172.20.1.10 router2 #default router for host2 Dynamic routing is the easiest way to manage routing on a host. Hosts that use dynamic routing run the routing protocols provided by the in.routed daemon for IPv4 or in.ripngd daemon for IPv6. Use the next procedure to enable IPv4 dynamic routing on a single interface host. For more information about dynamic routing, refer to Packet Forwarding and Routing on IPv4 Networks. On the host, assume the Primary Administrator role or become superuser.The Primary Administrator role includes the Primary Administrator profile. To create the role and assign the role to a user, see Chapter 2, Working With the Solaris Management Console (Tasks), in System Administration Guide: Basic Administration. Verify whether the /etc/defaultrouter file exists.# cd /etc # ls | grep defaultrouter If /etc/defaultrouter exists, delete any entry that you find there.An empty /etc/defaultrouter file forces the host to use dynamic routing. Verify whether packet forwarding and routing are enabled on the host.# routeadm Configuration Current Current Option Configuration System State --------------------------------------------------------------- IPv4 routing disabled disabled IPv6 routing disabled disabled IPv4 forwarding enabled enabled IPv6 forwarding disabled disabled Routing services "route:default ripng:default" If packet forwarding is enabled, turn it off Use either of the following commands:For the routeadm command, type the following:# routeadm -d ipv4-forwarding -u To use SMF, type the following:# svcadm disable ipv4-forwarding Enable routing protocols on the host.Use either of the following commands:For the routeadm command, type the following:# routeadm -e ipv4-routing -u To use SMF, type the following:#svcadm enable route:default Now IPv4 dynamic routing is enabled. The host's routing table is dynamically maintained by the in.routed daemon. The following example shows how to configure dynamic routing for hosta, a single-interface host on the network 192.168.5.0 that is shown in Figure 5–2. hosta currently uses Router 1 as its default router. However, hosta now needs to run dynamic routing.First, you would log in to hosta as superuser or assume an equivalent role. Then, you would determine whether the /etc/defaultrouter file is present on the host:# cd /etc # ls | grep defaultrouter defaultrouterThe response from grep indicates that a /etc/defaultrouter file exists for hosta. # vi /etc/defaultrouter 192.168.5.10The file has the entry 192.168.5.10, which is the IP address for Router 1. You would delete this entry to enable static routing. Next, you would need to verify whether packet forwarding and routing are already enabled for the host.# routeadm Configuration Current Current Option Configuration System State --------------------------------------------------------------- IPv4 routing disabled disabled IPv6 routing disabled disabled IPv4 forwarding disabled disabled IPv6 forwarding disabled disabled Routing services "route:default ripng:default"Both routing and packet forwarding are turned off for hosta. Turn on routing to complete the configuration of dynamic routing for hosta, as follows:#svcadm enable route:default The transport layer protocols TCP, SCTP, and UDP are part of the standard Solaris OS package. These protocols typically need no intervention to run properly. However, circumstances at your site might require you to log or modify services that run over the transport layer protocols. Then, you must modify the profiles for these services by using the Service Management Facility (SMF), which is described in Chapter 14, Managing Services (Overview), in System Administration Guide: Basic Administration. The inetd daemon is responsible for starting standard Internet services when a system boots. These services include applications that use TCP, SCTP, or UDP as their transport layer protocol. You can modify existing Internet services or add new services using the SMF commands. For more information about inetd, refer to inetd Internet Services Daemon.Operations that involve the transport layer protocols include:Logging of all incoming TCP connections Adding services that run over a transport layer protocol, using SCTP as an example Configuring the TCP wrappers facility for access control For detailed information on the inetd daemon refer to the inetd1Mman page. On the local system, assume the Network Management role or become superuser.Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services. Set TCP tracing to enabled for all services managed by inetd.# inetadm -M tcp_trace=TRUE The SCTP transport protocol provides services to application layer protocols in a fashion similar to TCP. However, SCTP enables communication between two systems, either or both of which can be multihomed. The SCTP connection is called an association. In an association, an application divides the data to be transmitted into one or more message streams, or multi-streamed. An SCTP connection can go to endpoints with multiple IP addresses, which is particularly important for telephony applications. The multihoming capabilities of SCTP are a security consideration if your site uses IP Filter or IPsec. Some of these considerations are described in the sctp7P man page.By default, SCTP is included in the Solaris OS and does not require additional configuration. However, you might need to explicitly configure certain application layer services to use SCTP. Some example applications are echo and discard. The next procedure shows how to add an echo service that uses an SCTP one-to-one style socket.You can also use the following procedure to add services for the TCP and UDP transport layer protocols. The following task shows how to add an SCTP inet service that is managed by the inetd daemon to the SMF repository. The task then shows how to use the Service Management Facility (SMF) commands to add the service.For information about SMF commands, refer to SMF Command-Line Administrative Utilities in System Administration Guide: Basic Administration. For syntactical information, refer to the man pages for the SMF commands, as cited in the procedure. For detailed information about SMF refer to the smf5 man page. Before you perform the following procedure, create a manifest file for the service. The procedure uses as an example a manifest for the echo service that is called echo.sctp.xml. Log in to the local system with a user account that has write privileges for system files. Edit the /etc/services file and add a definition for the new service.Use the following syntax for the service definition.service-name |port/protocol | aliases Add the new service.Go to the directory where the service manifest is stored and type the following:# cd dir-name # svccfg import service-manifest-nameFor a complete syntax of svccfg, refer to the svccfg1M man page.Suppose you want to add a new SCTP echo service using the manifest echo.sctp.xml that is currently located in the service.dir directory. You would type the following:# cd service.dir # svccfg import echo.sctp.xml Verify that the service manifest has been added:# svcs FMRIFor the FMRI argument, use the Fault Managed Resource Identifier (FMRI) of the service manifest. For example, for the SCTP echo service, you would use the following command:# svcs svc:/network/echo:sctp_streamYour output should resemble the following: STATE STIME FMRI disabled 16:17:00 svc:/network/echo:sctp_streamFor detailed information about the svcs command, refer to the svcs1 man page.The output indicates that the new service manifest is currently disabled. List the properties of the service to determine if you must make modifications.# inetadm -l FMRIFor detailed information about the inetadm command, refer to theinetadm1M man page.For example, for the SCTP echo service, you would type the following:# inetadm -l svc:/network/echo:sctp_stream SCOPE NAME=VALUE name="echo" endpoint_type="stream" proto="sctp" isrpc=FALSE wait=FALSE exec="/usr/lib/inet/in.echod -s" . . default tcp_trace=FALSE default tcp_wrappers=FALSE Enable the new service:# inetadm -e FMRI Verify that the service is enabled:For example, for the new echo service, you would type the following:# inetadm | grep sctp_stream . . enabled online svc:/network/echo:sctp_stream The following example shows the commands to use and the file entries required to have the echo service use the SCTP transport layer protocol.$ cat /etc/services . . echo 7/tcp echo 7/udp echo 7/sctp # cd service.dir # svccfg import echo.sctp.xml # svcs network/echo* STATE STIME FMRI disabled 15:46:44 svc:/network/echo:dgram disabled 15:46:44 svc:/network/echo:stream disabled 16:17:00 svc:/network/echo:sctp_stream # inetadm -l svc:/network/echo:sctp_stream SCOPE NAME=VALUE name="echo" endpoint_type="stream" proto="sctp" isrpc=FALSE wait=FALSE exec="/usr/lib/inet/in.echod -s" user="root" default bind_addr="" default bind_fail_max=-1 default bind_fail_interval=-1 default max_con_rate=-1 default max_copies=-1 default con_rate_offline=-1 default failrate_cnt=40 default failrate_interval=60 default inherit_env=TRUE default tcp_trace=FALSE default tcp_wrappers=FALSE # inetadm -e svc:/network/echo:sctp_stream # inetadm | grep echo disabled disabled svc:/network/echo:stream disabled disabled svc:/network/echo:dgram enabled online svc:/network/echo:sctp_stream The tcpd program implements TCP wrappers. TCP wrappers add a measure of security for service daemons such as ftpd by standing between the daemon and incoming service requests. TCP wrappers log successful and unsuccessful connection attempts. Additionally, TCP wrappers can provide access control, allowing or denying the connection depending on where the request originates. You can use TCP wrappers to protect daemons such as SSH, Telnet, and FTP. The sendmail application can also use TCP wrappers, as described in Support for TCP Wrappers From Version 8.12 of sendmail in System Administration Guide: Network Services. On the local system, assume the Primary Administrator role, or become superuser.The Primary Administrator role includes the Primary Administrator profile. To create the role and assign the role to a user, see Chapter 2, Working With the Solaris Management Console (Tasks), in System Administration Guide: Basic Administration. Set TCP wrappers to enabled.# inetadm -M tcp_wrappers=TRUE Configure the TCP wrappers access control policy as described in the hosts_access(3) man page. This man page can be found in the /usr/sfw/man directory on the SFW CD-ROM, which is packaged along with the Solaris OS CD-ROM.