HP-UX Reference (11i v3 07/02) - 4 File Formats (vol 8)
g
gated.conf(4) gated.conf(4)
If GateD has determined that the state of the kernel forwarding table has been changed, the necessary
requests to the kernel are made to restore the correct state.
Note that on currently available systems it is not possible to disable the processing of ICMP redirects, even
when the system is functioning as a router. To ignore the effects of redirects, GateD must process each one
and actively restore any changes it made to the state of the kernel. Because of the mechanisms involved,
there will be windows where the effects of redirects are present in the kernel.
By default, GateD removes redirects when actively participating in an interior gateway protocol (RIP,
HELLO, OSPF or IS-IS). It is not possible to enable redirects once they have been automatically disabled.
Listening to RIP or HELLO in nobroadcast mode does not cause redirects to be ignored, nor does the use of
EGP and BGP. Redirects must be manually configured off in these cases.
Note that in accordance with the latest IETF Router Requirements document, GateD insures that all ICMP
net redirects are processed as host redirects. When an ICMP net redirect is accepted, GateD issues the
requests to the kernel to make sure that the kernel forwarding table is updated to reflect a host redirect
instead of a net redirect.
The redirect statement does not prevent the system from sending redirects, only from listening to them.
The Redirect Statement
redirect yes | no | on | off
[ {
preference preference ;
interface interface_list
[ noredirects ]|[redirects ] ;
trustedgateways gateway_list ;
traceoptions trace_options ;
} ] ;
preference
Sets the preference for a route learned from a redirect. The default is 30.
interface interface_list
The interface statement allows the enabling and disabling of redirects on an interface-by-
interface basis. See the section on interface list specification for the description of the
interface_list. The possible parameters are:
noredirects
Specifies that redirects received via the specified interface will be ignored. The default
is to accept redirects on all interfaces.
redirects
This is the default. This argument may be necessary when noredirects is used on a
wildcard interface descriptor.
trustedgateways gateway_list
Defines the list of gateways from which redirects will be accepted. The gateway_list is simply a
list of host names or addresses. By default, all routers on the shared network(s) are trusted to
supply redirects. But if the trustedgateways clause is specified only redirects from the gate-
ways in the list are accepted.
traceoptions trace_options
There are no redirect-specific tracing options. All non-error messages are traced under the nor-
mal class.
Tracing options
There are no Redirect-specific tracing options. All nonerror messages are traced under the normal class.
The Router Discovery Protocol
The Router Discovery Protocol is an IETF standard protocol used to inform hosts of the existence of
routers. It is intended to be used instead of having hosts wiretap routing protocols such as RIP. It is used in
place of, or in addition to statically configured default routes in hosts.
The protocol is split into to portions, the server portion which runs on routers, and the client portion that
runs on hosts. GateD treats these much like two separate protocols, only one of which may be enabled at a
time.
HP-UX 11i Version 3: February 2007 − 32 − Hewlett-Packard Company 159