bgpd
is a Border Gateway Protocol
(BGP)
daemon which manages the network routing tables.
Its main purpose is to exchange information
concerning
"network reachability"
with other BGP systems.
bgpd
uses the Border Gateway Protocol, Version 4,
as described in RFC 1771.
Please refer to that document for more information about BGP.
bgpd
is usually started at boot time, and can be enabled by
setting the following in
/etc/rc.conf.local:
bgpd_flags=\&"\&"
See
rc(8)
and
rc.conf(8)
for more information on the boot process
and enabling daemons.
When
bgpd
starts up, it reads settings from a configuration file,
typically
bgpd.conf(5).
A running
bgpd
process can be controlled using the
bgpctl(8)
utility.
The options are as follows:
-c
Force
bgpd
to do
carp(4)
demotion at startup when the
demote
functionality is used.
Normally,
bgpd
will only do demotion at startup when the demotion counter for the group
in question is already greater than 0.
bgpd
will start handling demotion after all sessions with demotion configured for
the given group have been successfully established.
At system startup,
rc(8)
has the demotion counter for the group
carp
increased until after
bgpd
is started, so this option should
not
be used in
rc.conf(8).
-D macro
Define
macro
to be set to
value
on the command line.
Overrides the definition of
macro
in the configuration file.
-d
Do not daemonize.
If this option is specified,
bgpd
will run in the foreground and log to
stderr.
-f file
Use
file
as the configuration file,
instead of the default
/etc/bgpd.conf.
-n
Configtest mode.
Only check the configuration file for validity.
-r path
Open a second, restricted, control socket that
bgpctl(8)
can use.
Only
show
requests are allowed on this socket.
-s path
Use an alternate location for the default control socket.
-v
Produce more verbose output.
FILES
/etc/bgpd.conf
default
bgpd
configuration file
/var/run/bgpd.sock
default
bgpd
control socket
SEE ALSO
bgpd.conf(5),
bgpctl(8),
bgplg(8),
bgplgsh(8)
.Rs
.%R RFC 1771
.%T "A Border Gateway Protocol 4 (BGP-4)"
.%D March 1995
.Re
.Rs
.%R RFC 1997
.%T "BGP Communities Attribute"
.%D August 1996
.Re
.Rs
.%R RFC 2385
.%T "Protection of BGP Sessions via the TCP MD5 Signature Option"
.%D August 1998
.Re
.Rs
.%R RFC 2796
.%T "BGP Route Reflection - An Alternative to Full Mesh IBGP"
.%D April 2000
.Re
.Rs
.%R RFC 2918
.%T "Route Refresh Capability for BGP-4"
.%D September 2000
.Re
.Rs
.%R RFC 3392
.%T "Capabilities Advertisement with BGP-4"
.%D January 1999
.Re
.Rs
.%R RFC 3682
.%T "The Generalized TTL Security Mechanism (GTSM)"
.%D February 2004
.Re
.Rs
.%R RFC 3765
.%T "NOPEER Community for Border Gateway Protocol"
.%D April 2004
.Re
.Rs
.%R RFC 4760
.%T "Multiprotocol Extensions for BGP-4"
.%D January 2007
.Re
.Rs
.%R draft-ietf-idr-as4bytes-13
.%T "BGP Support for Four-octet AS Number Space"
.%D February 2007
.Re