On a SunOS machine, in.routed will automatically be started if there is no /etc/defaultrouter file and in.rdisc failed to find any Router Discovery compliant routers on the local network. in.routed will automatically START on routers if there is no /etc/defaultrouter file, EVEN if in.rdisc is running. in.routed supports RIPv1 only.

You should not need to do anything, other than possibly DELETING an /etc/defaultrouter file, in ORDER to get in.routed to run. You can force in.routed to BRING up standard network routes by putting entries for them into the file /etc/gateways. The standard format for that file is: net gateway metric passive or: net gateway metric active remote-network-ip, gateway-ip and hop-count.

On a SunOS machine, in.routed will automatically be started if there is no /etc/defaultrouter file and in.rdisc failed to find any Router Discovery compliant routers on the local network. in.routed will automatically start on routers if there is no /etc/defaultrouter file, even if in.rdisc is running. in.routed supports RIPv1 only.

You should not need to do anything, other than possibly deleting an /etc/defaultrouter file, in order to get in.routed to run. You can force in.routed to bring up standard network routes by putting entries for them into the file /etc/gateways. The standard format for that file is: net gateway metric passive or: net gateway metric active remote-network-ip, gateway-ip and hop-count.