Installing and Administering Internet Services

Chapter 8 249
Configuring gated
Configuring the RIP Protocol
RIP Protocol Statement
The syntax for the RIP protocol statement is:
rip yes|no | on|off [ {
broadcast|nobroadcast ;
nocheckzero ;
preference preference ;
defaultmetric metric ;
query authentication [none|[[simple|md5] password]] ;
interface interface_list
[noripin]|[ripin] [noripout]|[ripout]
[metricin metric] [metricout metric]
[version 1]|[version 2 [multicast|broadcast]]
[[secondary] authentication [none|[simple|md5] password]] ;
[interface ...]
trustedgateways router_list ;
sourcegateways router_list ;
traceoptions traceoptions ;
} ] ;
Curly braces ({}) are part of the syntax for the RIP protocol statement.
Square brackets ([]) are not part of the syntax; they are used here to
indicate optional parameters.
yes (or on) tells gated to enable the RIP protocol at this node and
process RIP packets coming in from other nodes. no (or off) tells gated
to disable the RIP protocol at this node. If gated finds fewer than two
network interfaces, the node only listens to RIP information. If gated
finds two or more network interfaces, the node both listens to and
broadcasts or multicasts RIP information. If you do not specify a RIP line
in your configuration file, rip on is assumed.
broadcast specifies that RIP packets are always generated. If the RIP
protocol is enabled and more than one interface is specified, broadcast
is assumed. Specifying broadcast with only one interface is useful only
when propagating static routes or routes learned from other protocols.
nobroadcast specifies that RIP packets are sent only to routers listed
in the sourcegateways clause. If the RIP protocol is enabled, but only
one interface is specified, nobroadcast is assumed.
nocheckzero specifies that the RIP protocol should not check to see if
the reserved fields in the RIP packets are zero. In RIP version 1 (as
described in RFC 1058), certain reserved fields should be zeroed out;
however, this may vary in RIP implementations.