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

clauses. version 2 multicast implies that you want to send Version 2 packets (containing
subnet mask information). version 2 broadcast implies that you want to send Version
2 packets. If you do not specify a version, version 1 is assumed.
• [secondary] authentication [none [simple | md5] password] specifies the
type of authentication for RIP Version 2 packets (it is ignored for Version 1 packets).
secondary indicates that the secondary authentication is defined; otherwise, the primary
authentication is defined. If authentication consisting of only a password is required, specify
simple password or password (where password is a quoted string of 0 – 16 characters).
If the required authentication consists of a key that was created with the MD5 algorithm,
specify md5. Default: none. (If you do not specify the authentication clause, the default
is primary authentication of none and no secondary authentication.
• trustedgateways provides a list of routers that provide valid RIP routing information; routing
packets from other routers are ignored.
◦ Default: all routers on the attached networks.
• sourcegateways specifies routers to which you can send RIP routing packets. If you specify
the nobroadcast clause, routing updates are sent only to routers listed in the
sourcegateways clause.
• traceoptions enables tracing for the RIP protocol. See “Specifying Tracing Options”
(page 45).
Simple RIP Configuration
A simple RIP configuration consists of RIP routers and end nodes that listen to information exchanged
by the RIP routers, as shown in Figure 4.
Figure 4 and the accompanying text describe configuration of a single end system (node A) and
a RIP router (node B). The configuration is the same for multiple end systems and RIP routers (only
node B’s configuration is shown here). This example shows only the syntax needed for a simple
configuration. A detailed description of the entire RIP protocol statement is given after this example.
Figure 4 Example of Simple RIP Configuration
A: End System on a LAN with RIP Routers
Set up the configuration file /etc/gated.conf in the end system A as follows:
rip yes {
interface 121.1.0.10 version 2 multicast;
};
static {
default interface 121.1.0.10 preference 255 ;
};
With one interface, A can listen to RIP traffic on the network but does not forward routing
information. Routers must be multicasting RIP packets on this network for A to learn about them
24 Configuring gated