gated maintains a complete routing table in the user
space, and keeps the kernel routing table synchronized with that
table. This section describes statements for setting up customized
routes in the Static class of the gated configuration file, /etc/gated.conf. These statements can be used to specify default
routers, static routes, passive interfaces, and routing metrics
for interfaces.
Specifying a Default Router |
 |
A static route provides a specific destination for network
packets. The static route can be a network address or host address
through a router. This route is installed in the kernel's
routing table. An example of a static route for the default route
is shown below:
static {
default gateway 15.13.114.196 retain ;
} ; |
The retain qualifier ensures that the entry is not deleted
when gated exists.
Installing Static Routes |
|
The static statement specifies a router or an interface in
the kernel routing tables. The following is an example of a static
route:
static {
193.2.1.32 mask 0xfffffff0 gateway 193.2.1.30
preference 8 retain ;
} ; |
If you specify an export statement for the default route, the route is passed
on to other routers. If only the static statement is specified and not an export statement, then the default route is not passed
on as a route to other routers. This is considered a passive default
route and is used only by the host that this gated is running on. The retain clause causes the route to be retained in the
kernel after gated is shut down.
Setting Interface States |
|
gated times out routes that pass through interfaces
that are not receiving any RIP, OSPF, or BGP packets. The passive clause in the interface statement in the Static class prevents gated from changing the preference of a route to the
interface if routing information is not received for the interface.
We recommend that you use the passive clause for all interfaces in HP-UX machines.
