Configuring the routed daemon

Follow these steps to configure the routed daemon.

1. Remove the comment symbol (#) and modify the routed clause in the /etc/rc.tcpip shell script.
   This automatically starts the routed daemon with each system startup.

   • Specify whether you want the gateway to run in active (-s flag) or passive (-q flag) mode.
   • Specify whether you want packet tracing on or off (-t flag). Packet tracing can also be turned on after the routed daemon is already started by using the kill command to send a SIGUSR1 signal to the daemon. This signal can also be used to increment the level of tracing through four levels. In addition, packet tracing can be turned off while the routed daemon is running by using the kill command to send a SIGUSR2 signal to the daemon. For more information, see the routed daemon and the kill command.
   • Specify whether you want debugging turned on or off (-d flag). If you use this flag, specify which log file you want debugging information stored in, or choose for it to be directed to the console display.
   • Specify whether you are running the routed daemon on a gateway (-g flag).
     Note: A host that is not a gateway can run the routed daemon, but it must be run in passive mode.
2. Identify any known networks by listing them in the /etc/networks file.
   See Networks File Format for TCP/IP in the Files Reference for more information. A sample networks file is located in the /usr/samples/tcpip directory.
3. Set up routes in the /etc/gateways file to any known gateways that are not directly connected to your network.
   Refer to Gateways File Format for TCP/IP in Files Reference for detailed examples of entries in the /etc/gateways file. A sample gateways file is located in the /usr/samples/tcpip directory.