HP-UX Reference (11i v1 00/12) - 4 File Formats (vol 8)

ManualsBrandsHP ManualsSoftwareHP-UX Reference Manuals

111

112

113

114

115

116

117

118

119

120

__________________________________________________________________________________________________________________________________________________________________________________________________

STANDARD Printed by: Nora Chuang [nchuang] STANDARD

/build/1111/BRICK/man4/!!!intro.4

________________________________________________________________

___ ___

gated.conf(4) gated.conf(4)

EGP and BGP. Redirects must be manually conﬁgured 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 reﬂect 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 speciﬁcation for the description of the

interface_list. The possible parameters are:

noredirects

Speciﬁes that redirects received via the speciﬁed 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

Deﬁnes 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 speciﬁed only redirects from the gate-

ways in the list are accepted.

traceoptions trace_options

There are no redirect-speciﬁc tracing options. All non-error messages are traced under the nor-

mal class.

Tracing options

There are no Redirect-speciﬁc tracing options. All non-error 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 conﬁgured 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.

The Router Discovery Server

The Router Discovery Server runs on routers and announces their existence to hosts. It does this by period-

ically multicasting or broadcasting a Router Advertisement to each interface on which it is enabled.

These Router Advertisements contain a list of all the routers addresses on a given interface and their

preference for use as a default router.

Initially these Router Advertisements occur every few seconds, then fall back to every few minutes. In

addition, a host may send a Router Solicitation to which the router will respond with a unicast Router

Advertisement (unless a multicast or broadcast advertisement is due momentarily).

HP-UX Release 11i: December 2000 − 32 − Section 4−−103

___