BGPD(8)                 OpenBSD System Manager's Manual                BGPD(8)

NAME
     bgpd - Border Gateway Protocol daemon

SYNOPSIS
     bgpd [-cdnv] [-D macro=value] [-f file] [-r path] [-s path]

DESCRIPTION
     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 en-
     abling daemons.

     When bgpd starts up, it reads settings from a configuration file, typi-
     cally 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 ques-
                 tion is already greater than 0.  bgpd will start handling de-
                 motion 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=value
                 Define macro to be set to value on the command line.  Over-
                 rides 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 va-
                 lidity.

     -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)

     A Border Gateway Protocol 4 (BGP-4), RFC 1771, March 1995.

     BGP Communities Attribute, RFC 1997, August 1996.

     Protection of BGP Sessions via the TCP MD5 Signature Option, RFC 2385,
     August 1998.

     Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing, RFC
     2545, March 1999.

     BGP Route Reflection - An Alternative to Full Mesh IBGP, RFC 2796, April
     2000.

     Route Refresh Capability for BGP-4, RFC 2918, September 2000.

     The Generalized TTL Security Mechanism (GTSM), RFC 3682, February 2004.

     NOPEER Community for Border Gateway Protocol, RFC 3765, April 2004.

     BGP Extended Communities Attribute, RFC 4360, February 2006.

     BGP Cease Notification Message Subcodes, RFC 4486, April 2006.

     Multiprotocol Extensions for BGP-4, RFC 4760, January 2007.

     BGP Support for Four-octet AS Number Space, RFC 4893, May 2007.

     Capabilities Advertisement with BGP-4, RFC 5492, February 2009.

     Error Handling for Optional Transitive BGP Attributes, draft-ietf-idr-
     optional-transitive-00, April 2009.

HISTORY
     The bgpd program first appeared in OpenBSD 3.5.

OpenBSD 4.7                    February 23, 2010                             2
