GATED(1M) RISC/os Reference Manual GATED(1M)
NAME
gated - gateway routing daemon
SYNOPSIS
gated [-t[i][e][r][p][u][R][H]] [logfile]
DESCRIPTION
gated is a routing daemon that handles multiple routing pro-
tocols and replaces routed(1M), and any routing daemon that
speaks the EGP and HELLO routing protocols. gated currently
handles the RIP, EGP, and HELLO routing protocols. The
gated process can be configured to perform all routing pro-
tocols or any combination of the three. The configuration
for gated is by default stored in the file /etc/gated.conf
and can be changed at compile time in the file defs.h.
COMMAND LINE TRACING OPTIONS
gated can be invoked with a number of tracing flags and/or a
log file. Tracing flags may also be specified in the confi-
guration file with the "traceflags" clause. gated forks and
detaches itself from the controlling terminal unless tracing
flags are specified without specifying a log file, in which
case all tracing output is sent to the controlling terminal.
The valid tracing flags are as follows:
-t If used alone, log all error messages, route changes
and EGP packets sent and received. Using this flag
alone turns on the i, e, r, and p trace flags
automatically. When used with another flag, the -t
has no effect and only the accompanying flags are
recognized. Note that when using other flags, the
-t flag must be used with them.
i Log all internal errors and interior routing errors.
e Log all external errors due to EGP, exterior routing
errors, and EGP state changes.
r Log all routing changes.
p Trace all EGP packets sent and received.
u Log all routing updates sent.
R Trace all RIP packets received.
H Trace all HELLO packets received.
The gated process always logs fatal errors. If no log file
is specified and no tracing flags are set, all messages are
sent to /dev/null.
Printed 11/19/92 Page 1
GATED(1M) RISC/os Reference Manual GATED(1M)
SIGNAL PROCESSING
gated catches a number of signals and performs specific
actions. Currently gated does special processing with the
SIGHUP and SIGINT signals.
When a SIGHUP is sent to the gated process and gated is
invoked with trace flags and a log file, tracing is toggled
off and the log file is closed. At this point the log file
may be moved or removed. The next SIGHUP to gated will tog-
gle the tracing on. gated reads the configuration file and
sets the tracing flags to those specified with the "tra-
ceflags" clause. If no "traceflags" clause is specified
tracing is resumed using the trace flags specified on the
command line. The log file specified in the command line is
created if necessary and the trace output is sent to that
file. The trace output is appended to an already existing
log file. This is useful for having rotating log files like
those of the syslog daemon.
Sending gated a SIGINT will cause a memory dump to be
scheduled within the next sixty seconds. The memory dump
will be written to the file /usr/tmp/gated_dump. gated will
finish processing pending routing updates before performing
the memory dump. The memory dump contains a snapshot of the
current gated status, including the interface configura-
tions, EGP neighbor status and the routing tables. If the
file /usr/tmp/gated_dump already exists, the memory dump
will be appended to the existing file.
CONFIGURATION FILE OPTIONS FOR CONTROLLING TRACING OUTPUT
traceflags traceflag [traceflag] [traceflag] ...
The clause tells the gated process what level of tracing
output is desired. This option is read during gated ini-
tialization and whenever gated receives a SIGHUP. This
option is overridden at initialization time if tracing flags
are specified on the command line. The valid tracing flags
are as follows:
internal Log all internal errors and interior routing
errors.
external Log all external errors due to EGP, exterior
routing errors, and EGP state changes.
route Log all routing changes.
egp Trace all EGP packets sent and received.
update Log all routing updates sent.
Page 2 Printed 11/19/92
GATED(1M) RISC/os Reference Manual GATED(1M)
rip Trace all RIP packets received.
hello Trace all HELLO packets received.
general A combination of "internal", "external",
"route" and "egp".
all Enable all of the above tracing flags.
If more than one "traceflags" clause is used, the tracing
flags accumulate.
CONFIGURATION FILE OPTIONS FOR HANDLING ROUTING PROTOCOLS
In this section, the numerous configuration options are
explained. Each time the gated process is started, it reads
the file /etc/gated.conf to obtain its instructions on how
routing will be managed with respect to each protocol. The
configuration options are as follows:
RIP {yes | no | supplier | pointopoint | quiet| gateway #}
This tells the gated process how to perform the RIP routing
protocol. Only one of the above RIP arguments is allowed
after the keyword "RIP". If more than one is specified,
only the first one is recognized. A list of the arguments
to the RIP clause follows:
yes Perform the RIP protocol. Process all incoming RIP
packets and supply RIP information every thirty
seconds only if there are two or more network inter-
faces.
no Do not perform the RIP protocol. Do not perform
RIP.
supplier
Perform the RIP protocol. Process all incoming RIP
packets and force the supplying of RIP information
every thirty seconds no matter how many network
interfaces are present.
pointopoint
Perform the RIP protocol. Process all incoming RIP
packets and force the supplying of RIP information
every thirty seconds no matter how many network
interfaces are present. When this argument is
specified, RIP information will not be sent out in a
broadcast packet. The RIP information will be sent
directly to the gateways listed in the "sourcerip-
gateways" option described below.
Printed 11/19/92 Page 3
GATED(1M) RISC/os Reference Manual GATED(1M)
quiet Process all incoming RIP packets, but do not supply
any RIP information no matter how many network
interfaces are present.
gateway #
Process all incoming RIP packets, supply RIP infor-
mation every thirty seconds, and announce the
default route (0.0.0.0) with a metric of #. The
metric should be specified in a value that
represents a RIP hopcount. With this option set,
all other default routes coming from other RIP gate-
ways will be ignored. The default route is only
announced when actively peering with at least one
EGP neighbor and therefore should only be used when
EGP is used.
If no "RIP" clause is specified, RIP will not be performed.
HELLO {yes | no | supplier | pointopoint | quiet| gateway #}
This tells the gated process how to perform the HELLO rout-
ing protocol. The arguments parallel the RIP arguments, but
do have some minor differences. Only one of the above HELLO
arguments is allowed after the keyword "HELLO". If more
than one is specified, only the first one is recognized. A
list of the arguments to the HELLO clause follows:
yes Perform the HELLO protocol. Process all incoming
HELLO packets and supply HELLO information every
fifteen seconds only if there are two or more net-
work interfaces.
no Do not perform the HELLO protocol. Do not perform
HELLO.
supplier
Perform the HELLO protocol. Process all incoming
HELLO packets and force the supplying of HELLO
information every fifteen seconds no matter how many
network interfaces are present.
pointopoint
Perform the HELLO protocol. Process all incoming
HELLO packets and force the supplying of HELLO
information every fifteen seconds no matter how many
network interfaces are present. When this argument
is specified, HELLO information will not be sent out
in a broadcast packet. The HELLO information will
be sent directly to the gateways listed in the
"sourcehellogateways" option described below.
Page 4 Printed 11/19/92
GATED(1M) RISC/os Reference Manual GATED(1M)
quiet Process all incoming HELLO packets, but do not sup-
ply any HELLO information despite the number of net-
work interfaces present.
gateway #
Process all incoming HELLO packets, supply HELLO
information every fifteen seconds, and announce the
default route (0.0.0.0) with a time delay of #. The
time delay should be specified in milliseconds. The
default route is only announced when actively peer-
ing with at least one of EGP neighbor, therefore
should only be used when running EGP.
If no "HELLO" clause is specified, HELLO will not be per-
formed.
EGP {yes | no}
This clause allows the processing of EGP by gated to be
turned on or off.
no Do not perform any EGP processing.
yes Perform all EGP operations.
Please note that by default, EGP processing will take place.
Therefore, if no "EGP" clause is specified, all EGP opera-
tions will take place.
autonomoussystem #
If performing the EGP protocol, this clause must be used to
specify the autonomous system number (#). If not specified,
gated will exit and give a fatal error message.
egpmaxacquire #
If performing the EGP protocol, this clause specifies the
number of EGP peers with whom gated will be performing EGP.
This number must be greater than zero and less than or equal
to the number of EGP neighbors specified or gated will exit.
egpneighbor gateway
If performing the EGP protocol, this clause specifies with
whom gated will be performing EGP. "Gateway" can be either
a symbolic name in /etc/hosts or an IP hostname in Internet
dot (a.b.c.d) notation. Dot notation is recommended to
avoid confusion. Each EGP neighbor will be acquired in the
order listed in the configuration file.
Printed 11/19/92 Page 5
GATED(1M) RISC/os Reference Manual GATED(1M)
CONFIGURATION FILE OPTIONS FOR HANDLING ROUTING INFORMATION
The following configuration file options tell gated how to
deal with both incoming and outgoing routing information.
trustedripgateways gateway [gateway] [gateway] .....
trustedhellogateways gateway [gateway] [gateway] .....
When these clauses are specified, gated will only listen to
RIP or HELLO information, respectively from these RIP or
HELLO gateways. gateway can be either a symbolic name from
/etc/hosts or an IP host address in dot notation (a.b.c.d).
Again, dot notation is recommended to eliminate confusion.
Please note that the propagation of routing information is
not restricted by this clause.
sourceripgateways gateway [gateway] [gateway] .....
sourcehellogateways gateway [gateway] [gateway] .....
gated will send RIP or HELLO information directly to the
gateways specified. If "pointopoint" is specified in the
"RIP" or "HELLO" clauses mentioned above, gated will only
send RIP or HELLO information to the specified gateways.
gated will NOT send out any information using the broadcast
address. If "pointopoint" is not specified in those clauses
and gated is supplying of RIP or HELLO information, gated
will send information to the specified gateways as well as
broadcasting it using a broadcast address.
noripoutinterface intfaddr [intfaddr] [intfaddr] .....
nohellooutinterface intfaddr [intfaddr] [intfaddr] .....
noripfrominterface intfaddr [intfaddr] [intfaddr] .....
nohellofrominterface intfaddr [intfaddr] [intfaddr] .....
The above clauses turn protocols on and off on a per inter-
face basis. "no{rip|hello}frominterface" means that no RIP
or HELLO information will be accepted coming into the listed
interfaces from another gateway. "no{rip|hello}outinterface"
means that no RIP or HELLO knowledge will be sent out of the
listed interfaces. "intfaddr" should be in dot notation
(a.b.c.d).
passiveinterfaces intfaddr [intfaddr] [intfaddr] .....
In order to dynamically determine if an interface is prop-
erly functioning, gated will time out an interface when no
RIP, HELLO or EGP packets are being received on that partic-
ular interface. PSN interfaces send a RIP or HELLO packet to
themselves to determine if the interface is properly func-
tioning as the delay between EGP packets may be longer than
the interface timeout. Interfaces that have timed out
automatically have their routes re-installed when routing
information is again received over the interface. The above
Page 6 Printed 11/19/92
GATED(1M) RISC/os Reference Manual GATED(1M)
clause stops gated from timing out the listed interfaces.
The interfaces listed will always be considered up and work-
ing. If gated is not a RIP or HELLO supplier, all inter-
faces will not be aged and the "passiveinterfaces" automati-
cally applies to all interfaces.
interfacemetric intfaddr metric#
This feature allows the specification of an interface metric
for the listed interface. On systems that support interface
metrics, this clause will override the kernel's metric. On
systems that do not have support for an interface metric,
this feature allows the specification of one. The interface
metric is added to the true metric of each route that comes
in via routing information from the listed interface. The
interface metric is also added to the true metric of any
information sent out via the listed interface. This clause
is required for each interface on which an interface metric
is desired.
reconstmetric intfaddr metric#
This is a first attempt to throw hooks for fallback routing
into gated. If the above clause is used, the metrics of the
routes contained in any RIP information coming into the
listed interface will be set to the specified "metric#".
Metric reconstitution should not be used lightly, since it
could be a major contributor in the formation of routing
loops. USE THIS WITH EXTREME CAUTION. Any route that has a
metric of infinity will not be reconstituted and left as
infinity.
fixedmetric intfaddr proto {rip|hello} metric#
This is another attempt to throw hooks for fallback routing
into gated. If the above clause is used, all routing infor-
mation sent out the specified interface will have a metric
of "metric#". For RIP, specify the metric as a RIP hopcount
from 0 to infinity. For HELLO, specify the metric as a
HELLO delay in milliseconds from 0 to infinity. Any route
that has a metric of infinity will be left as infinity.
Fixed metrics should also be USED WITH EXTREME CAUTION!
donotlisten net intf addr [addr] ... proto {rip|hello}
donotlistenhost host intf addr [addr] ... proto {rip|hello}
This clause reads as follows: keyword "donotlisten" followed
by a network number, which should be in dot notation fol-
lowed by keyword "intf". Then a list of interfaces in dot
notation precede the keyword "proto", followed by "rip" or
"hello".
Printed 11/19/92 Page 7
GATED(1M) RISC/os Reference Manual GATED(1M)
This means that any information regarding "net" coming in
via the specified protocols AND from the specified inter-
faces will be ignored. The keyword "all" may be used after
the keyword "intf" to specify all interfaces on the machine.
For example:
donotlisten 10.0.0.0 intf 128.84.253.200 proto rip
means that any RIP information about net 10.0.0.0 coming in
via interface 128.84.253.200 will be ignored. One clause is
required for each net on which this restriction is desired.
donotlisten 26.0.0.0 intf all proto rip hello
means that any RIP and HELLO information about net 26.0.0.0
coming in via any interface will be ignored.
"donotlistenhost" can be described the same way as above
except that a host address is provided instead of a network
address. Restrictions of the nature described above are
applied to the specified host route learned of by the speci-
fied routing protocol.
listen net gateway addr [addr] ... proto {rip|hello}
listenhost host gateway addr [addr] ... proto {rip|hello}
This clause reads as follows: keyword "listen" followed by a
network number which should be in dot notation followed by
keyword "gateway". Then a list of gateways in dot notation
should precede the keyword "proto", followed by "rip" or
"hello".
This means to only listen to information about network "net"
by the specified protocol(s) only from the listed "gate-
ways". For example:
listen 128.84.0.0 gateway 128.84.253.3 proto hello
means that any HELLO information about net 128.84 coming in
via gateway 128.84.253.3 will be accepted. Any other infor-
mation about 128.84 from any other gateway will be rejected.
One clause is necessary for each net to be restricted.
listenhost 26.0.0.15 gateway 128.84.253.3 proto rip
means that any information about host 26.0.0.15 must come
via RIP and from gateway 128.84.253.3. All other informa-
tion regarding this host will be ignored.
announce net intf addr [addr] ... proto type [egpmetric #]
announcehost host intf addr ... proto type [egpmetric #]
noannounce net intf addr [addr] ... proto type [egpmetric #]
Page 8 Printed 11/19/92
GATED(1M) RISC/os Reference Manual GATED(1M)
noannouncehost host intf addr ... proto type [egpmetric #]
These clauses allow restriction of the networks and hosts
announced and by which protocol. The "announce{host}" and
"noannounce{host}" clauses may not be used together on the
same interface. With the "announce{host}" clause, gated
will only announce the nets or hosts that have an associated
"announce{host}" clause with the appropriate protocol. With
the "noannounce{host}" clause, gated will announce every-
thing, EXCEPT those nets or hosts that have an associated
"noannounce{host}" clause. This allows a choice of announc-
ing only what is on the announce list or everything except
those nets on the noannounce list on a per interface basis.
The arguments are the same as in the "donotlisten" clause
except "egp" may be specified in the "proto" field. "type"
can either be "rip", "hello", "egp", or any combination of
the three. When "egp" is specified in the "proto" field, an
egp metric must be specified. This is the metric at which
gated will announce the listed net via EGP.
Please note that these are not static route entries. These
restrictions will only apply if the net or host is learned
via one of the routing protocols. If a restricted network
suddenly becomes unreachable and goes away, announcement of
this net will stop until it is learned again.
Currently, only one "announce{host}" or "noannounce{host}"
may be specified per network or host. It is not possible to
announce a network or host via HELLO out one interface and
via RIP out another.
Some examples:
announce 128.84 intf all proto rip hello egp egpmetric 0
announce 10.0.0.0 intf all proto rip
announce 0.0.0.0 intf 128.84.253.200 proto rip
announce 35.0.0.0 intf all proto rip egp egpmetric 3
With only these four "announce" clauses in the configuration
file, this gated process will only announce these four nets.
It will announce 128.84.0.0 via RIP and HELLO to all inter-
faces and announce it via EGP with a metric of 0. Net
10.0.0.0 will be announced via RIP to all interfaces. Net
0.0.0.0 (default) will be announced by RIP out interface
128.84.253.200 only. Net 35.0.0.0 will be announced via RIP
to all interfaces and announced via EGP with a metric of 3.
These are the only nets that will be broadcast by this gate-
way. Once the first "announce" clause is specified, only
the nets with "announce" clauses will be broadcast; this
includes local subnets. Once an "announce{host}" or
"noannounce{host}" has an "all" specified after an "intf",
Printed 11/19/92 Page 9
GATED(1M) RISC/os Reference Manual GATED(1M)
that clause is applied globally and the option of having per
interface restrictions is lost. If no routing announcement
restrictions are desired, "announce" clauses should not be
used. All information learned will then be propagated out.
Please note that this has no affect on the information to
which gated listens. Any net that does not have an
"announce" clause is still added to the kernel routing
tables, but it is not announced via any of the routing pro-
tocols. To stop nets from being added to the kernel the
"donotlisten" clause may be used.
announce 128.84 intf 128.59.2.1 proto rip
noannounce 128.84 intf 128.59.1.1 proto rip
The above clauses mean that on interface 128.59.2.1, only
information about 128.84.0.0 will be announced via RIP, but
on interface 128.59.1.1, all information will be announced,
except 128.84.0.0 via RIP.
noannounce 128.84 intf all proto rip hello egp
egpmetric 0
noannounce 10.0.0.0 intf all proto hello
These clauses mean that except for the two specified nets,
all nets will be propagated. Specifically, net 128.84.0.0
will not be announced on any interface via any protocols.
Knowledge of 128.84.0.0 is not sent anywhere. Net 10.0.0.0
will not be announced via HELLO to any interface. This also
implies that net 10.0.0.0 will be announced to every inter-
face via RIP. This net will also be broadcast via EGP with
a metric specified in the "defaultegpmetric" clause.
defaultegpmetric #
This is a default EGP metric to use when there are no rout-
ing restrictions. Normally, with no routing restrictions,
gated announces all networks learned via HELLO or RIP via
EGP with this specified default EGP metric. If this clause
is not used, the default EGP metric is set to 255, which
would make any EGP advertised route of this nature be
ignored. When there are no routing restrictions, any net-
work with a direct interface is announced via EGP with a
metric of 0. Note that this does not include subnets, but
only the non-subnetted network.
defaultgateway gateway proto {active|passive}
This initial default gateway is installed in the kernel
routing tables during startup and initialization. If EGP is
being used, as soon as an update is received from an EGP
neighbor, this default route is deleted. If EGP is not being
used, but RIP or HELLO are, and "active" is specified, this
Page 10 Printed 11/19/92
GATED(1M) RISC/os Reference Manual GATED(1M)
default route will be deleted and overwritten by default
learned from any other RIP or HELLO gateway. If no default
route is learned via RIP or HELLO, this default route will
be maintained in the kernel routine tables. If "passive" is
specified, the default route will be added to the kernel and
will NOT be overwritten by any other default route broad-
cast. The default route will NOT be propagated when the
"passive" option is used.
"gateway" should be an address in dot notation. "proto"
should be either "rip", "egp", or "hello". The "proto"
field initializes the protocol by which the route was
learned. Although in this case it is unused, but the field
is remains for consistency.
net netaddr gateway addr metric hopcnt {rip|egp|hello}
host hostaddr gateway addr metric hopcnt {rip|egp|hello}
The following clauses install a static route to net
"netaddr" or host "hostaddr" through gateway "addr" at a
metric of "hopcnt" learned via either RIP, HELLO, or EGP.
As usual, dot notation is recommended for the addresses.
This route will be installed in the kernel's routing table
and will never be affected by any other gateway's RIP or
HELLO announcements. The protocol by which it was learned
is important if the route is to be announced via EGP. If
the protocol is "rip" or "hello" and there are no routing
restrictions, then this route will be announced by EGP with
a metric of "defaultegpmetric". If the protocol is "egp"
and there are no routing restrictions, then this route will
be announced by EGP with a metric of "hopcnt".
egpnetsreachable net [net] [net] .....
This option was left in as a "soft restriction". It cannot
be used when the "announce" or "noannounce" clauses are
used. Normally, with no restrictions, gated announces all
routes learned from RIP and HELLO via EGP. The
"egpnetsreachable" clause restricts EGP announcement to
those nets listed in the clause. The metric used for the
HELLO and RIP learned routes is the value given in the
"defaultegpmetric" clause. If this clause does not specify
a value, the value is set to 255. With the "egpnetsreach-
able" clause, individual unique EGP metrics may not be set
for each net. The "defaultegpmetric" is used for all net-
works except those that are directly connected, which use a
metric of 0.
martiannets net [net] [net] ...
This clause appends to gated's list of "martian" networks.
"Martian" networks are those known to be invalid and should
Printed 11/19/92 Page 11
GATED(1M) RISC/os Reference Manual GATED(1M)
be ignored. When gated hears about one of these networks
through any means, it will immediately ignore it. If
"external" tracing is enabled, a message will be printed to
the trace log. Multiple occurrences of the "martiannets"
clause accumulate.
A initial list of "martian" networks is coded into gated in
the include file "rt_control.h". This list contains
127.0.0.0, 128.0.0.0, 191.253.0.0, 192.0.0.0, 223.255.255.0,
and 224.0.0.0.
NOTES ON CONFIGURATION OPTIONS
gated stores its Process ID in the file /etc/gated.pid.
If EGP is being used when supplying the default route (via
"RIP gateway" or "HELLO gateway" and all EGP neighbors are
lost, the default route will not be advertised until at
least one EGP neighbor is regained.
If routing restrictions are used, gated logs all invalid
networks using syslog at log level LOG_WARNING and facility
LOG_DAEMON. The facility may be changed at compile time by
use of the LOG_FACILITY define.
With the complexity of the current network topology and with
many back door paths to networks, the use of routing res-
trictions is recommended. With the current routing stra-
tegies, it is easy for illegal or invalid networks to
penetrate into the ARPAnet Core or the NSFnet backbone.
Using routing restrictions does take a little more mainte-
nance time and routing restrictions are not the long term
answer, but for now, in order to be good internet players,
we must use them.
GATED INTERNAL METRICS
gated stores all metrics internally as a HELLO time delay
ranging from 0 to 30000. Received RIP metrics are
translated to and from these internal time delays with the
use of the following translation tables:
Time Delay RIP metric
0- 0 0
1- 100 1
101- 148 2
149- 219 3
220- 325 4
326- 481 5
482- 713 6
714- 1057 7
1058- 1567 8
1568- 2322 9
2323- 3440 10
Page 12 Printed 11/19/92
GATED(1M) RISC/os Reference Manual GATED(1M)
3441- 5097 11
5098- 7552 12
7553-11190 13
11191-16579 14
16580-24564 15
24565-30000 16
RIP metric Time Delay
0 0
1 100
2 148
3 219
4 325
5 481
6 713
7 1057
8 1567
9 2322
10 3440
11 5097
12 7552
13 11190
14 16579
15 24564
16 30000
NOTES ON IMPLEMENTATION SPECIFICS
gated stores all metrics internally in milliseconds. The
RIP metric is mapped to a millisecond based metric and pro-
cessed. This will preserve the granularity of the HELLO
protocol time delay.
In the gated configuration file, all references to POINT-
TO-POINT interfaces must use the DESTINATION address. This
is the only change made to the configuration file syntax
from earlier versions, which used the source address of the
PTP link. Otherwise, old configuration files should be com-
patible.
All protocols have a two minute hold down. When a routing
update indicates that the route in use is being deleted,
gated will not delete the route for two minutes.
Changes can be made to the interfaces and gated will notice
them without having to restart the process. If the, net-
mask, subnetmask, broadcast address, or interface metric are
changed, the interface should be marked down with "ifcon-
fig", then marked up at least thirty seconds later. Flag
changes do not require the interface to be brought down and
back up.
Printed 11/19/92 Page 13
GATED(1M) RISC/os Reference Manual GATED(1M)
RIP propagates and listens to host routes. This was done to
handle PTP links more consistently. This version also sup-
ports the RIP_TRACE commands.
Subnet interfaces are supported. Subnet information will
only be propagated on interfaces to other subnets of the
same network. For example, if there is a gateway between
two class B networks, the subnet routes for each respective
class B net are not propagated into the other class B net.
Just the class B network number is propagated.
gated listens to host and network REDIRECTs and tries to
take an action on the REDIRECT for its own internal tables
that parallels the kernel's action. In this way, the
redirect routine in gated parallels the Berkeley kernel
redirect routine as closely as possible. Unlike the Berke-
ley kernel, gated times out routes learned via a REDIRECT
after six minutes. The route is then deleted from the ker-
nel routing tables. This helps keep the routing tables more
consistent. Any route that was learned via a REDIRECT is
NOT announced by any routing protocol.
The gated EGP code verifies that all nets sent and received
are valid class A, B or C networks per the EGP specifica-
tion. Information about networks that do not meet these
criteria is not propagated. If an EGP update packet con-
tains information about an network that is not either class
A, B or C, the update is considered to be in error and is
ignored. Only the information about the specific network
will be ignored if gated is compiled with the EGP_IGNORE_BAD
define specified. This option should be used with caution.
BOOT-TIME CONFIGURATION
When the file /etc/gated.conf (linked to
/usr/etc/gated.conf) exists, gated will automatically
startup at system boot-time. Default tracing flags can be
placed within this file, see "traceflags". If the
configuration/sentinel file is nonexistent, routed(1M) will
be started instead.
FILES
/etc/gated.conf The configuration file.
/etc/gated.pid The process ID is stored here.
/usr/tmp/gated_dump The memory dump file.
/etc/gated The gated process itself.
SEE ALSO
routed(1M).
RFC827 (EGP formal specs.), RFC891 (HELLO formal specs.),
RFC911 (EGP under UNIX).
The conf directory in the distribution package for sample
configuration files.
Page 14 Printed 11/19/92
GATED(1M) RISC/os Reference Manual GATED(1M)
AUTHORS
Mark Fedor (1986-1987)
fedor@nisc.nyser.net
Jeffrey C Honig
Cornell Theory Center
265 Olin Hall
Cornell University
Ithaca, NY 14853-5201
607/255-8686
jch@tcgould.tn.cornell.edu
{ucbvax,uunet,decvax}!tcgould.tn.cornell.edu!jch
CREDITS
This program was derived from Paul Kirton's EGP for UNIX,
UC-Berkeley's routed(8), and HELLO routines by Mike Petry at
the University of Maryland.
Special thanks to Craig Partridge, craig@nnsc.nsf.net, for
linting, profiling and performance enhancements.
Also, thanks to all the BETA-TESTERS and the NSFNET backbone
crew who put up with occasional nasty conditions brought on
by the development of this program.
Printed 11/19/92 Page 15