Filter
Top Products
Configuring gated
Configuring the RIP Protocol
Chapter 3 57
B: Cluster (or Root) Server Node
Run gated to get routing information about the 121.0.0.0 network. Set
up /etc/gated.conf as follows:
interfaces {
interface 130.15.0.6 121.1.0.92 passive ;
};
rip yes {
interface 130.15.0.6 noripout ;
interface 121.1.0.92 version 2 multicast;
};
static {
default gateway 121.1.0.2 preference 255 ;
};
In the previous example, setting rip to yes is similar to setting rip to
broadcast. Both the arguments inform the node to send out RIP
packets, because the node has at least two interfaces. To reduce traffic on
the 130.15.0.0 LAN, use the noripout option on this interface. This
prevents RIP from sending packets on the 130.15.0.0 network.
To isolate the 130.15.0.0 LAN, use the following:
export proto rip interface 121.1.0.92 {
proto direct {
130.15.0.0 restrict ;
};
};
To further isolate the LAN from the 121.1.0.0 LAN, do not specify any
static routes that specify that you can reach the LAN through B. See
“Importing and Exporting Routes” on page 97 for more information.
Always specify the passive option with the interface’s IP address. It
informs gated to maintain the routes even if no other nodes on the
121.0.0.0 network are using RIP. Without this clause, gated changes the
preference of the route to the interface if it does not receive routing
information for that interface. The static default route adds the specified
default to the kernel routing table. Setting the preference to 255
replaces this route whenever another default route is learned from one of
the protocols.
C: End System on a LAN with RIP Routers
Set up /etc/gated.conf as follows: