ROUTED(8) BSD System Manager's Manual ROUTED(8)NAMErouted - network routing daemon emulator
SYNOPSISrouted [-qst] [logfile]
DESCRIPTION
Routed is a script that builds a gated(8) configuration file based on the
specified flags and invokes gated(8) to emulate the historic routed com-
mand. Routed is invoked at boot time to manage the network forwarding
tables.
The routed process waits for a signal or for gated(8) to terminate, then
removes the temporary configuration file before exiting. On receipt of a
HUP or TERM signal, routed will terminate gated(8) and exit. It is also
possible to manage gated(8) with the gdc(8) interface.
The following flags are supported:
-q Specifies ``quiet'' mode.
-s Specifies ``supplier'' mode.
-t Enables packet tracing. RIP and router discovery ICMP packets will
be traced. Tracing occurs to stderr or the specified logfile.
When a logfile is specified, gated(8) is instructed to log changes to the
routing tables and other events in the specified log file. When the -t
flag is specified, RIP and router discovery ICMP packets sent and re-
ceived will also be logged.
Routed has three modes of operation:
automatic If IP forwarding is enabled gated(8) will be configured for
supplier mode. Otherwise, gated(8) will be configured for
quiet mode. The mode is determined at startup by querying the
net.inet.ip.forwarding kernel variable with sysctl(8).
quiet This mode is appropriate for single and multi-homed hosts. In
this mode gated(8) will not supply routing information, in-
stead it will listen for RIP packets and participate as a
router discovery client.
supplier This mode is appropriate for systems acting as a router and
forwarding packets between two network interfaces. Gated(8)
will supply RIP routing information and participate as a
router discovery server.
Differences when invoking gated(8) via this interface and the historic
version of routed are:
o RIP packets are not sent out point-to-point (i.e. SLIP and PPP) in-
terfaces.
o Gated(8) participates as a router discovery client or server, depend-
ing on the mode in which it is operating. When acting as a router
discovery client, the ``default'' route created to point to the
router in use is preferred over a route learned via RIP.
o When acting as a host, gated(8) is configured to listen for broadcast
RIPv1 packets and broadcast or multicast RIPv2 packets. When acting
as a router, gated(8) is configured to broadcast RIPv2 packets that
are compatible with RIPv1 clients.
o The tracing options work somewhat differently and -d is not support-
ed.
o The -g option to originate a ``default'' route is not supported.
o The USR1 and USR2 signals are not available to toggle tracing. See
the gdc(8) command for information on how to toggle tracing with
gated(8).
o The INT signal is not available to flush the routing table.
o The /etc/gateways file is not supported, routed will not start gat-
ed(8) it if is present.
o Gated(8) monitors changes in interface configuration.
o Gated(8) monitors changes to the kernel forwarding table with the
route(8) command. Static routes added in this manner override RIP
routes and the ``default'' generated on a router discovery client,
but are never supplied in RIP advertisements.
o Gated(8) monitors ICMP redirects and times them out after three min-
utes.
SEE ALSOudp(4), icmp(4), XNSrouted(8), gated(8), gdc(8), htable(8),
sysctl(8).
BSDI BSD/OS June 24, 1996 2
