HP-UX Reference (11i v1 05/09) - 4 File Formats (vol 8)

g
gated.conf(4) gated.conf(4)
route competes with routes from other protocols. The default preference is 60.
retain
Normally gated removes all routes except interface routes from the kernel forwarding table
during a graceful shutdown. The retain option may be used to prevent specific static
routes from being removed. This is useful to insure that some routing is available when
gated is not running.
reject
Instead of forwarding a packet like a normal route, reject routes cause packets to be
dropped and unreachable messages to be sent to the packet originators. Specifying this
option causes this route to be installed as a reject route. Not all kernel forwarding engines
support reject routes.
blackhole
A blackhole route is the same as a reject route except that unreachable messages
are not supported.
noinstall
Normally the route with the lowest preference is installed in the kernel forwarding table
and is the route exported to other protocols. When noinstall is specified on a route, it
will not be installed in the kernel forwarding table when it is active, but it will still be eligi-
ble to be exported to other protocols.
( network [(mask mask )|(masklen number )])interface interface
This form defines a static interface route which is used for primitive support of multiple network
addresses on one interface. The preference, retain, reject, blackhole and noinstall
options are the same as described above.
Control Statements Overview
Control statements control routes that are imported from routing peers and routes that are exported to
these peers. These are the final statements to be included in the gated.conf file. The control statements are:
• the Import Statement
• the Export Statement
• the Aggregate Statement
• the Generate Statement
Route Filtering
Routes are filtered by specifying configuration language that will match a certain set of routes by destina-
tion, or by destination and mask. Among other places, route filters are used on martians, import and
export statements.
The action taken when no match is found is dependent on the context, for instance import and export
route filters assume an all reject ; at the end a list.
A route will match the most specific filter that applies. Specifying more than one filter with the same desti-
nation, mask and modifiers will generate an error.
Filtering syntax
network [ exact | refines ]
network mask mask [ exact | refines ]
network masklen number [ exact | refines ]
all
default
host host
These are all the possible formats for a route filter. Not all of these formats are available in all places, for
instance the host and default formats are not valid for martians.
In most cases it is possible to specify additional parameters relevant to the context of the filter. For exam-
ple, on a martian statement it is possible to specify the allow keyword, on an import statement you
can specify a preference, and on a export you can specify a metric.
network [ exact | refines ]
Section 4−−110 Hewlett-Packard Company − 41 − HP-UX 11i Version 1: September 2005