Sun Microsystems Sun Workstation 100U System Manager's Manual page 241

ROUTED(8C)
MAINTENANCE COMMANDS ROUTED (8C)
FILES
history of recent messages sent and received which are related to the changed route.
In addition to the facilities described above, routed supports the notion of "distant" passive and
active gateways. When routed
is started up, it reads the file
I
etcl gateways to find gateways which
may not be identified using the SIOGIFCONF ioctl. Gateways specified in this manner should be
marked passive if they are not expected to exchange routing information, while gateways marked
active should be willing to exchange routing information (that
is,
they should have a routed pro-
cess funning on the machine). Passive gateways are maintained in the routing tables forever and
information regarding their existence is included in any routing information transmitted. Active
gateways are treated equally to network interfaces. Routing information is distributed to the
gateway and if no routing information is received for a period of the time, the associated route is
deleted.
The
I
etcl gateways is comprised of a series of lines, each in the following format:
<
net
I
ho.t
>
name1 lateway name! metric value
<
pas.lve
I
active
>
The net or ho.t keyword indicates if the route is to a network or specific host.
Name1 is the name of the destination network or host. This may be a symbolic name located in
I
etcl networks or
I
etcl hosts, or an Internet address specified in "dot" notation; see inet(3N).
Name! is the name or address of the gateway to which messages should be forwarded.
Value is a metric indicating the hop count to the destination host or network.
The keyword pas.lve or active indicates if the gateway should be treated as passive or active (as
described above).
/etc/gateways for distant gateways
SEE ALSO
BUGS
86
Internet Transport Protocols, XSIS 028112, Xerox System Integration Standard. (Sun 800-1066-
01)
udp(4P)
The kernel's routing tables may not correspond to those of routed for short periods of time while
processes utilizing existing routes exit; the only remedy for this is to place the routing process in
the kernel.
Routed should listen to intelligent interfaces, such
3.8
an IMP, and to error protocols, such
3.8
ICMP, to gather more information.
Last change: 28 October 1983
Sun Release 1.1