bgpd.8

同时支持IPv4和IPv6的BGP协议实现

.\"	$KAME: bgpd.8,v 1.10 2000/12/04 06:28:21 itojun Exp $
.\"
.\" Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project.
.\" All rights reserved.
.\" 
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\"    notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\"    notice, this list of conditions and the following disclaimer in the
.\"    documentation and/or other materials provided with the distribution.
.\" 3. Neither the name of the project nor the names of its contributors
.\"    may be used to endorse or promote products derived from this software
.\"    without specific prior written permission.
.\" 
.\" THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
.Dd May 17, 1998
.Dt BGPD 8
.Os KAME
.\"
.Sh NAME
.Nm bgpd
.Nd BGP4+ and RIPng routing protocol daemon
.\"
.Sh SYNOPSIS
.Nm
.Op Fl c Ar configfile
.Op Fl C
.Op Fl f
.\"
.Sh DESCRIPTION
.Nm
speaks IPv6 routing protocols,
and maintains the IPv6 network routing table.
Though the name is
.Nm bgpd ,
it supports both BGP4+ (RFC\ 2283)
and RIPng (RFC\ 2080) as IPv6 routing protocols.
.Pp
Options supported by
.Nm bgpd :
.Bl -tag -width Ds
.It Fl c Ar configfile
Specify alternate location,
.Ar configfile ,
for configuration file.
By default,
.Pa /usr/local/v6/etc/bgpd.conf
is used.
.It Fl C
Just check the configuration and immediately exit.
When
.Nm
is invoked with this option, super user privilege is not required.
.It Fl f
Do not become daemon, run in foreground.
.El
.Pp
The
.Nm
program dumps its current routing information to a dump file when
it receives a SIGUSR1 signal.
The information includes per-interface
RIPng routes and per-peer base BGP information.
By default, the dump file is
.Ar /var/run/bgpd.dump ,
which is configurable in the configuration file.
If the dump file does not exist,
.Nm
will create a new one and dump to it.
.\"
.Sh "ERROR MESSAGES"
The
.Nm
daemon logs error messages using
.Xr syslog 3 .
.\"
.Sh FILES
.Bl -tag -width /var/run/inetd.pid -compact
.It Pa /usr/local/v6/etc/bgpd.conf
default configuration file.
.It Pa /var/run/bgpd.pid
the pid of the currently running
.Nm bgpd .
.It Pa /var/run/bgpd.dump
default dump file.
.El
.\"
.Sh SEE ALSO
.Xr bgpd.conf 5
.\"
.Sh HISTORY
The
.Nm
command was first appeared in Toshiba IPv6 protocol stack kit.
.\"
.Sh BUGS
No authentication is supported.
Therfore, OPEN message's optional parameter always consists of nothing.
.Pp
Currently, the
.Nm
daemon doesn't watch the routing socket.
So after invoking,
.Nm
can't handle new routes which are manually added or are added
by some other routing daemons/commands.
.Pp
There is code to handle OSPFv6 in the
.Nm
source directory, but OSPFv6 support is just in progress.
.Nm
is not able to distribute nor get IPv6 routing information via OSPFv6.