Configuring Internet Protocol (IP) routing

Routing daemons

Routing daemons initialize and dynamically maintain the kernel routing table by communicating with daemons on other systems to exchange routing information such as what networks are known by the machine on which the daemon is running. Routing daemons exchange information according to routing protocols. The differences between daemons are the routing protocols each supports. The daemon(s) to run on a machine depend on what protocol(s) is needed.

SCO TCP/IP supports three routing daemons:

irdd description

The routing daemon irdd implements the Internet Router Discovery (IRD) protocol. For information on this protocol see ``Internet Router Discovery (IRD) protocol''.

The SCO TCP/IP start/stop script, tcp(ADMN), starts and stops irdd when a ROUTERDAEMONx variable is set to /etc/irdd in the tcp(SFF) configuration file (/etc/default/tcp). SCO TCP/IP is shipped with a default /etc/irdd.conf configuration file. irdd can be run on both routers and nonrouters. See the reference manual pages irdd(ADMN) and irdd.conf(SFF) for more information.

routed description

The routed daemon implements version I of the Routing Information Protocol (RIP I) to exchange routing information. It uses the /etc/gateways file to initialize static routes to distant networks. The /etc/gateways file is described in the reference manual page routed(ADMN).

If you wish to run routed, you must specify the routing daemon in /etc/default/tcp, the TCP/IP default configuration file; see the tcp(SFF) manual page.

When routed starts, it reads the /etc/gateways file (if it exists) and installs the routes defined there into its routing table. It then broadcasts on each local network to find other hosts running routed. If such hosts exist, the routing daemons cooperate in maintaining a globally consistent view of routing within an autonomous system (AS). This view can be extended to include remote networks also running routed by setting up suitable entries in /etc/gateways.

gated description

The gated routing daemon:

supports any one or more of the following protocols: RIP Version 1 or 2, OSPF, EGP, BGP.
starts and stops through an entry in the TCP/IP start/stop script, tcp(ADMN) when a ROUTER_DAEMONx variable is set to /etc/gated in the tcp(SFF) configuration file (/etc/default/tcp).
typically runs on routers only.
has an operational user interface. See gdc(ADMN).
implements an SMUX peer that permits management of protocol (OSPF, BGP, RIP) variables via SNMP .

See the gated(ADMN) reference manual page for more information.

The gated(ADMN) daemon has been upgraded to gated V3 from Cornell University, resulting in the following changes:

Upgraded BGP protocol support from V1 to the V3 standard.
Added OSPF routing protocol support. OSPF is the standard interior routing protocol recommended by the Internet Engineering Task Force (IETF).
Added the new command, ospf_monitor(ADMN), which provides for querying OSPF routers.
Upgraded RIP protocol support to V2 within gated (the routed(ADMN) daemon implements RIP V1).
Added a new command, gdc, which provides a user interface for monitoring and controlling the operation of the gated facility; see gdc(ADMN).
Removed HELLO protocol support.

In addition, the gated daemon now implements the SNMP Multiplexing (SMUX) protocol, which provides support for the following Simple Network Management Protocol (SNMP) Management Information Bases (MIBs): EGP, BGP, RIPv2, and OSPF.