Setting up routing

Running a routing daemon on a non-routing host

By running a routing daemon on a non-routing host, you can make it update its routing tables based on broadcasts from routers.

If the router is running the routed daemon, routed listens for broadcasts from other routers and gateways and continually updates its routing tables based on the information in those broadcasts. It also broadcasts its own routing tables so that other machines can use them for updating their own routing tables.

Because routed on a router both broadcasts its own routing table and listens for broadcasts from other routers, it is known as an ``active'' routed.

By default, the routed daemon on a host with a single network interface is ``passive'' or ``quiet''. It listens for broadcast routing table information from local routers so that it can update its own table, but it does not supply routing information.

Even if the local routers on a subnet use routed, you can choose not to run routed on the non-routing hosts if the routes to the usual destinations do not change.

NOTE: The routing protocol used by non-routing hosts must match that used by the routers if routes are not statically defined on the hosts or the hosts do not use router discovery.

If hosts are configured to run routed, you can configure either routed or gated to run on the routers.