Technical data

Gateway Routing Daemon (GATED) Configuration Reference
A.5 Creating the GATED Configuration File
#------------------------------------------------------------------------------
#
# TCPIP$GATED.CONF - Sample config file, preconfigured for RIP v1.
#
#------------------------------------------------------------------------------
#
interfaces {
interface all passive ;
};
#
# Protocols:
#
rip on {
broadcast;
interface all ripin ripout version 1;
};
#
redirect on;
routerdiscovery server off;
hello off;
ospf off;
egp off;
bgp off;
snmp off;
#
# Static routes:
#
#static {
# 10.1.2.0 mask 255.255.255.0 gateway 10.1.1.1;
# default gateway 10.1.2.3;
#};
#
# Policy:
#
#export proto rip {
# proto static { all metric 1; };
# proto direct { all; };
# proto rip { all; };
#};
A.6 Defining Preferences and Routing
The configuration file can define routes from one protocol or peer to another,
assigning each route a value, called a preference.
The preference value determines the order of routes to the same destination in
a single routing database. The active route is chosen by the lowest preference
value. Some protocols implement a second preference (
preference2 ), sometimes
referred to as a ‘‘tie breaker.’’
Preferences have the following characteristics:
• May appear in several different configuration statements in the configuration
file. Be aware, however, that the last, or most specific value set for a route is
the value GATED will use.
• May specify one network interface over another, one protocol over another, or
one remote gateway over another.
• Cannot be used to control the selection of routes within an interior gateway
protocol (IGP). That function is accomplished automatically by the protocol
based on metric.
A–4 Gateway Routing Daemon (GATED) Configuration Reference