Technical data

Gateway Routing Daemon (GATED) Configuration Reference
A.6 Defining Preferences and Routing
Table A–2 (Cont.) Default Preference Values
Preference Defined by Statement Default
RIP routes rip 100
Point-to-point interface 110
Routes to interfaces that are down interfaces 120
Aggregate/generate routes aggregate/generate 130
OSPF AS external routes ospf 150
BGP routes bgp 170
EGP egp 200
A.6.2 Sample Preference Specifications
In the following example, the preference applicable to routes learned through
RIP from gateway 138.66.12.1 is 75. The last preference applicable to routes
learned through RIP from gateway 138.66.12.1 is defined in the accept statement.
The preference applicable to other RIP routes is found in the rip statement.
The preference set on the interface statement applies only to the route to that
interface.
interfaces {
interface 138.66.12.2 preference 10 ;
};
rip yes {
preference 90 ;
};
import proto rip gateway 138.66.12.1 preference 75 ;
A.7 Tracing Options
You can specify tracing options at the following levels: file specifications, control
options, and global and protocol specific tracing options. Unless overridden,
tracing options from the next higher level are inherited by lower levels. For
example, Border Gateway Protocol (BGP) peer tracing options are inherited from
BGP group tracing options, which are inherited from global BGP tracing options,
which are inherited from global GATED tracing options. At each level, tracing
specifications override the inherited options.
The syntax for trace options statements is as follows:
traceoptions [trace_file [replace] [size size[k|m]
files files]]
[control_options] trace_options[except trace_options];
traceoptions none ;
Table A–3 describes the valid trace options.
A–6 Gateway Routing Daemon (GATED) Configuration Reference