HP-UX Reference (11i v2 04/09) - 4 File Formats (vol 8)
g
gated.conf(4) gated.conf(4)
will only be opened when an interface with the appropriate local address (through which the
peer or gateway address is directly reachable) is operating. For other types of peers, a peer ses-
sion will be maintained when any interface with the specified local address is operating. In
either case incoming connections will only be recognized as matching a configured peer if they
are addressed to the configured local address.
holdtime time
Specifies the BGP holdtime value to use when negotiating the connection with this peer, in
seconds. According to BGP, if GateD does not receive a keepalive, update, or notification mes-
sage within the period specified in the Hold Time field of the BGP Open message, then the
BGP connection will be closed. The value must be either 0 (no keepalives will be sent) or at
least 3.
version version
Specifies the version of the BGP protocol to use with this peer. If not specified, the highest
supported version is used first and version negotiation is attempted. If it is specified, only the
specified version will be offered during negotiation. Currently supported version are 2, 3 and 4.
passive
Specifies that active OPENs to this peer should not be attempted. GateD should wait for the
peer to issue an open. By default all explicitly configured peers are active, they periodically
send OPEN messages until the peer responds.
sendbuffer buffer_size
recvbuffer buffer_size
Control the amount of send and receive buffering asked of the kernel. The maximum supported
is 65535 bytes although many kernels have a lower limit. By default, GateD configures the
maximum supported. These parameters are not needed on normally functioning systems.
indelay time
outdelay time
Used to dampen route fluctuations. Indelay is the amount of time a route learned from a
BGP peer must be stable before it is accepted into the gated routing database. Outdelay is
the amount of time a route must be present in the gated routing database before it is exported
to BGP. The default value for each is 0, meaning that these features are disabled.
keep all
Used to retain routes learned from a peer even if the AS paths of the routes contain one of our
exported AS numbers.
showwarnings
Causes GateD to issue warning messages when receiving questionable BGP updates such as
duplicate routes and/or deletions of nonexisting routes. Normally these events are silently
ignored.
noauthcheck
Normally GateD verifies that incoming packets have an authentication field of all ones. This
option may be used to allow communication with an implementation that uses some other form
of authentication.
noaggregatorid
Causes GateD to specify the routerid in the aggregator attribute as zero (instead of its
routerid) in order to prevent different routers in an AS from creating aggregate routes with
different AS paths.
keepalivesalways
Causes gated to always send keepalives, even when an update could have correctly substituted
for one. This allows interoperability with routers that do not completely obey the protocol
specifications on this point.
v3asloopokay
By default gated will not advertise routes whose AS path is looped (with an AS appearing more
than once in the path) to version 3 external peers. Setting this flag removes this constraint.
Ignored when set on internal groups or peers.
nov4asloop
Prevents routes with looped AS paths from being advertised to version 4 external peers. This
can be useful to avoid advertising such routes to peer which would incorrectly forward the
Section 4−−106 Hewlett-Packard Company − 30 − HP-UX 11i Version 2: September 2004