Static
statements define the static routes used by GateD.
A single static
statement can specify any number routes.
The static
statements occur after protocol statements and
before control statements in the gated.conf file. Any number of
static
statements may be specified, each containing any
number of static route definitions. These routes can be overridden by
routes with better preference values.
static { ( host host ) | default | ( network [ ( mask mask ) | ( masklen number ) ] ) gateway gateway_list [ interface interface_list ] [ preference preference ] [ retain ] [ reject ] [ blackhole ] [ noinstall ] ; ( network [ ( mask mask ) | ( masklen number ) ] ) interface interface [ preference preference ] [ retain ] [ reject ] [ blackhole ] [ noinstall ] ; } ;
gateways
listed are available on directly attached interfaces. If more
than one elligible gateways are available, they are limited by
the number of multipath destinations supported (this compile time
parameter is currently almost always one on Unix).
Parameters for static routes are:
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
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
route is the same as a
reject
route except that
unreachable
messages are not supported.
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
elligible to be exported to other protocols.
preference
, retain
,
reject
, blackhole
and
noinstall
options are the same as described above.