HP-UX Routing Services Administrator's Guide HP-UX 11i v2, HP-UX 11i v3 (B2355-91153, November 2011)

finds two or more network interfaces, the node not only listens but also broadcasts or multicasts
the RIP information. If you do not specify a RIP statement in your configuration file, rip on is
assumed.
The following describes the various options in the RIP statement:
• 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 must not check whether the reserved fields in
the RIP packets are zero. In RIP Version 1 (as described in RFC 1058), certain reserved fields
must be zero; however, this may vary in RIP implementations.
• preference determines the order of routes from other protocols to the same destination in
the routing table. gated allows one route to a destination per protocol for each autonomous
system. In case of multiple routes, the route used is determined by the value of preference.
◦ Default: 100
◦ Range: 0 (most preferred) – 255 (least preferred)
• defaultmetric is the default metric used when propagating routes learned from other
protocols.
◦ Default: 16
◦ Range: 1 – 16
• query authentication [none [[simple|md5] password]]specifies the
authentication, if any, that is required for query packets that do not originate from routers. If
authentication consisting of only a password is required, specify simple password or
password. If the required authentication consists of a key that was created with the MD5
algorithm, specify md5. Default: none.
• interface is specified as one of the following (in the order of precedence): an IP address
(for example, 193.2.1.36), a domain or interface name (for example, lan0 or lan1), a
wildcard name (for example, lan*), or all (which refers to all interfaces). You can specify
multiple interface statements with different clauses. If you specify a clause more than once,
the instance with the most specific interface reference is used.
• noripin specifies that gated does not process any RIP information received through the
specified interface. Default: ripin.
• noripout specifies that gated does not send any RIP information through the specified
interface. Default: ripout.
• metricin specifies the incoming metric for all routes propagated to this node through the
specified interface.
◦ Default: kernel interface metric plus 1 (the default RIP hopcount)
• metricout specifies the outgoing metric for all routes propagated by this node through the
specified interface.
◦ Default: 0
• version 1 specifies that RIP Version 1 packets (as defined in RFC 1058) are sent; RIP Version
2 packets (defined in RFC 1388) are sent only in response to a Version 2 poll packet. version
2 specifies that RIP Version 2 packets are sent to the RIP multicast address or to the broadcast
addresses. You can specify how the packets are sent with the multicast or broadcast
Configuring the RIP Protocol 23