Installing and Administering Internet Services

338 Chapter8
Configuring gated
Configuring the RIP Protocol
/etc/rc.config.d/netconf file as follows:
ROUTE_DESTINATION[0]= "default"
ROUTE_GATEWAY[0]= "130.15.0.6"
ROUTE_COUNT[0]= "1"
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 this case, setting rip to yes is like setting rip to broadcast. Either
argument tells 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 a
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 377.
Always specify the passive option with the interface’s IP address. It tells
gated to maintain routes even if no other nodes on the 121.0.0.0 network
are using RIP. Without this clause, gated may change the preference of
the route to the interface if routing information is not received for the
interface. The static default route adds the specified default to the kernel
routing table. Setting the preference to 255 allows this route to be
replaced whenever another default route is learned from one of the
protocols.