- supported a string notation for xxflags.
- deprecate routes#N, as it is hard to keep consistency with
rtprefixN. accept any number of "rtprefix", "rtrefix0",
..., "rtprefix99".
- deprecate "addrs#N", as it is difficult for users to keep
consistency with "addrN".
accept 100 prefix info in maximum - like "addr", "addr0"
... "addr99". WARNS=2 clean on netbsd.
old configuration file should work just fine.
behavior change:
previously, we rejected "addrN" if there's "addr", and we rejected
"addr" if there is "addrN". now we accept both without problem.
- when an advertised prefix configured from the kernel has been added
or invalidated, notice the change in a short delay.
- when invalidating a prefix, do not bark even if there is
inconsistency about prefix lifetimes.
- wrap more specific route info code into ROUTEINFO.
Obtained from: KAME
MFC after: 1 week
2003-08-15 19:13:53 +00:00
|
|
|
.\" $KAME: rtadvd.8,v 1.24 2002/05/31 16:16:08 jinmei Exp $
|
2000-07-05 22:09:50 +00:00
|
|
|
.\"
|
2000-01-06 12:40:54 +00:00
|
|
|
.\" 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.
|
|
|
|
.\"
|
2005-02-09 18:07:17 +00:00
|
|
|
.\" $FreeBSD$
|
|
|
|
.\"
|
2013-02-25 16:47:09 +00:00
|
|
|
.Dd February 25, 2013
|
2000-01-06 12:40:54 +00:00
|
|
|
.Dt RTADVD 8
|
2000-07-05 22:09:50 +00:00
|
|
|
.Os
|
2000-01-06 12:40:54 +00:00
|
|
|
.Sh NAME
|
|
|
|
.Nm rtadvd
|
|
|
|
.Nd router advertisement daemon
|
|
|
|
.Sh SYNOPSIS
|
|
|
|
.Nm
|
2011-06-06 03:06:43 +00:00
|
|
|
.Op Fl dDfRs
|
2000-01-06 12:40:54 +00:00
|
|
|
.Op Fl c Ar configfile
|
2013-02-25 16:47:09 +00:00
|
|
|
.Op Fl C Ar ctlsock
|
2011-06-06 03:06:43 +00:00
|
|
|
.Op Fl M Ar ifname
|
2010-12-22 23:58:21 +00:00
|
|
|
.Op Fl p Ar pidfile
|
2013-02-25 16:47:09 +00:00
|
|
|
.Op Ar interface ...
|
2000-01-06 12:40:54 +00:00
|
|
|
.Sh DESCRIPTION
|
2000-07-05 22:09:50 +00:00
|
|
|
.Nm
|
- supported a string notation for xxflags.
- deprecate routes#N, as it is hard to keep consistency with
rtprefixN. accept any number of "rtprefix", "rtrefix0",
..., "rtprefix99".
- deprecate "addrs#N", as it is difficult for users to keep
consistency with "addrN".
accept 100 prefix info in maximum - like "addr", "addr0"
... "addr99". WARNS=2 clean on netbsd.
old configuration file should work just fine.
behavior change:
previously, we rejected "addrN" if there's "addr", and we rejected
"addr" if there is "addrN". now we accept both without problem.
- when an advertised prefix configured from the kernel has been added
or invalidated, notice the change in a short delay.
- when invalidating a prefix, do not bark even if there is
inconsistency about prefix lifetimes.
- wrap more specific route info code into ROUTEINFO.
Obtained from: KAME
MFC after: 1 week
2003-08-15 19:13:53 +00:00
|
|
|
sends router advertisement packets to the specified
|
2000-01-06 12:40:54 +00:00
|
|
|
.Ar interfaces .
|
2013-02-25 16:47:09 +00:00
|
|
|
If no interfaces are specified,
|
|
|
|
.Nm
|
|
|
|
will still run, but will not advertise any routes until interfaces are
|
|
|
|
added using
|
|
|
|
.Xr rtadvctl 8 .
|
2000-01-06 12:40:54 +00:00
|
|
|
.Pp
|
|
|
|
The program will daemonize itself on invocation.
|
2000-10-29 16:44:10 +00:00
|
|
|
It will then send router advertisement packets periodically, as well
|
2000-07-05 22:09:50 +00:00
|
|
|
as in response to router solicitation messages sent by end hosts.
|
2000-01-06 12:40:54 +00:00
|
|
|
.Pp
|
2000-07-05 22:09:50 +00:00
|
|
|
Router advertisements can be configured on a per-interface basis, as
|
|
|
|
described in
|
2000-01-06 12:40:54 +00:00
|
|
|
.Xr rtadvd.conf 5 .
|
|
|
|
.Pp
|
2000-10-29 16:44:10 +00:00
|
|
|
If there is no configuration file entry for an interface,
|
2000-07-05 22:09:50 +00:00
|
|
|
or if the configuration file does not exist altogether,
|
2000-01-06 12:40:54 +00:00
|
|
|
.Nm
|
|
|
|
sets all the parameters to their default values.
|
|
|
|
In particular,
|
|
|
|
.Nm
|
2000-07-05 22:09:50 +00:00
|
|
|
reads all the interface routes from the routing table and advertises
|
2000-01-06 12:40:54 +00:00
|
|
|
them as on-link prefixes.
|
|
|
|
.Pp
|
2000-07-05 22:09:50 +00:00
|
|
|
.Nm
|
- supported a string notation for xxflags.
- deprecate routes#N, as it is hard to keep consistency with
rtprefixN. accept any number of "rtprefix", "rtrefix0",
..., "rtprefix99".
- deprecate "addrs#N", as it is difficult for users to keep
consistency with "addrN".
accept 100 prefix info in maximum - like "addr", "addr0"
... "addr99". WARNS=2 clean on netbsd.
old configuration file should work just fine.
behavior change:
previously, we rejected "addrN" if there's "addr", and we rejected
"addr" if there is "addrN". now we accept both without problem.
- when an advertised prefix configured from the kernel has been added
or invalidated, notice the change in a short delay.
- when invalidating a prefix, do not bark even if there is
inconsistency about prefix lifetimes.
- wrap more specific route info code into ROUTEINFO.
Obtained from: KAME
MFC after: 1 week
2003-08-15 19:13:53 +00:00
|
|
|
also watches the routing table.
|
2002-06-13 16:59:31 +00:00
|
|
|
If an interface direct route is
|
|
|
|
added on an advertising interface and no static prefixes are
|
2000-07-05 22:09:50 +00:00
|
|
|
specified by the configuration file,
|
2000-01-06 12:40:54 +00:00
|
|
|
.Nm
|
2002-06-13 16:59:31 +00:00
|
|
|
adds the corresponding prefix to its advertising list.
|
|
|
|
.Pp
|
|
|
|
Similarly, when an interface direct route is deleted,
|
|
|
|
.Nm
|
|
|
|
will start advertising the prefixes with zero valid and preferred
|
|
|
|
lifetimes to help the receiving hosts switch to a new prefix when
|
|
|
|
renumbering.
|
|
|
|
Note, however, that the zero valid lifetime cannot invalidate the
|
|
|
|
autoconfigured addresses at a receiving host immediately.
|
|
|
|
According to the specification, the host will retain the address
|
|
|
|
for a certain period, which will typically be two hours.
|
|
|
|
The zero lifetimes rather intend to make the address deprecated,
|
|
|
|
indicating that a new non-deprecated address should be used as the
|
|
|
|
source address of a new connection.
|
|
|
|
This behavior will last for two hours.
|
|
|
|
Then
|
|
|
|
.Nm
|
|
|
|
will completely remove the prefix from the advertising list,
|
|
|
|
and succeeding advertisements will not contain the prefix information.
|
|
|
|
.Pp
|
2000-07-05 22:09:50 +00:00
|
|
|
Moreover, if the status of an advertising interface changes,
|
|
|
|
.Nm
|
|
|
|
will start or stop sending router advertisements according
|
|
|
|
to the latest status.
|
2000-01-06 12:40:54 +00:00
|
|
|
.Pp
|
2002-06-13 16:59:31 +00:00
|
|
|
The
|
|
|
|
.Fl s
|
|
|
|
option may be used to disable this behavior;
|
|
|
|
.Nm
|
|
|
|
will not watch the routing table and the whole functionality described
|
|
|
|
above will be suppressed.
|
|
|
|
.Pp
|
2001-06-11 12:39:29 +00:00
|
|
|
Basically, hosts MUST NOT send Router Advertisement messages at any
|
2011-06-06 03:06:43 +00:00
|
|
|
time (RFC 4861, Section 6.2.3).
|
2001-06-11 12:39:29 +00:00
|
|
|
However, it would sometimes be useful to allow hosts to advertise some
|
|
|
|
parameters such as prefix information and link MTU.
|
|
|
|
Thus,
|
|
|
|
.Nm
|
|
|
|
can be invoked if router lifetime is explicitly set zero on every
|
|
|
|
advertising interface.
|
|
|
|
.Pp
|
2000-07-05 22:09:50 +00:00
|
|
|
The command line options are:
|
2000-01-06 12:40:54 +00:00
|
|
|
.Bl -tag -width indent
|
|
|
|
.\"
|
|
|
|
.It Fl c
|
|
|
|
Specify an alternate location,
|
|
|
|
.Ar configfile ,
|
|
|
|
for the configuration file.
|
|
|
|
By default,
|
2000-02-15 18:21:38 +00:00
|
|
|
.Pa /etc/rtadvd.conf
|
2000-01-06 12:40:54 +00:00
|
|
|
is used.
|
2013-02-25 16:47:09 +00:00
|
|
|
.It Fl C
|
|
|
|
Specify an alternate location for the control socket used by
|
|
|
|
.Xr rtadvctl 8 .
|
|
|
|
The default is
|
|
|
|
.Pa /var/run/rtadvd.sock .
|
2000-01-06 12:40:54 +00:00
|
|
|
.It Fl d
|
2000-07-05 22:09:50 +00:00
|
|
|
Print debugging information.
|
2000-01-06 12:40:54 +00:00
|
|
|
.It Fl D
|
2000-07-05 22:09:50 +00:00
|
|
|
Even more debugging information is printed.
|
2000-01-06 12:40:54 +00:00
|
|
|
.It Fl f
|
2000-07-05 22:09:50 +00:00
|
|
|
Foreground mode (useful when debugging).
|
- supported a string notation for xxflags.
- deprecate routes#N, as it is hard to keep consistency with
rtprefixN. accept any number of "rtprefix", "rtrefix0",
..., "rtprefix99".
- deprecate "addrs#N", as it is difficult for users to keep
consistency with "addrN".
accept 100 prefix info in maximum - like "addr", "addr0"
... "addr99". WARNS=2 clean on netbsd.
old configuration file should work just fine.
behavior change:
previously, we rejected "addrN" if there's "addr", and we rejected
"addr" if there is "addrN". now we accept both without problem.
- when an advertised prefix configured from the kernel has been added
or invalidated, notice the change in a short delay.
- when invalidating a prefix, do not bark even if there is
inconsistency about prefix lifetimes.
- wrap more specific route info code into ROUTEINFO.
Obtained from: KAME
MFC after: 1 week
2003-08-15 19:13:53 +00:00
|
|
|
Log messages will be dumped to stderr when this option is specified.
|
2001-06-11 12:39:29 +00:00
|
|
|
.It Fl M
|
|
|
|
Specify an interface to join the all-routers site-local multicast group.
|
|
|
|
By default,
|
|
|
|
.Nm
|
- supported a string notation for xxflags.
- deprecate routes#N, as it is hard to keep consistency with
rtprefixN. accept any number of "rtprefix", "rtrefix0",
..., "rtprefix99".
- deprecate "addrs#N", as it is difficult for users to keep
consistency with "addrN".
accept 100 prefix info in maximum - like "addr", "addr0"
... "addr99". WARNS=2 clean on netbsd.
old configuration file should work just fine.
behavior change:
previously, we rejected "addrN" if there's "addr", and we rejected
"addr" if there is "addrN". now we accept both without problem.
- when an advertised prefix configured from the kernel has been added
or invalidated, notice the change in a short delay.
- when invalidating a prefix, do not bark even if there is
inconsistency about prefix lifetimes.
- wrap more specific route info code into ROUTEINFO.
Obtained from: KAME
MFC after: 1 week
2003-08-15 19:13:53 +00:00
|
|
|
tries to join the first advertising interface appearing on the command
|
2001-06-11 12:39:29 +00:00
|
|
|
line.
|
|
|
|
This option has meaning only with the
|
|
|
|
.Fl R
|
|
|
|
option, which enables routing renumbering protocol support.
|
2010-12-22 23:58:21 +00:00
|
|
|
.It Fl p
|
|
|
|
Specify an alternative file in which to store the process ID.
|
|
|
|
The default is
|
2012-05-24 02:24:03 +00:00
|
|
|
.Pa /var/run/rtadvd.pid .
|
2000-07-05 22:09:50 +00:00
|
|
|
.It Fl R
|
|
|
|
Accept router renumbering requests.
|
|
|
|
If you enable it, certain IPsec setup is suggested for security reasons.
|
2001-06-11 12:39:29 +00:00
|
|
|
This option is currently disabled, and is ignored by
|
|
|
|
.Nm
|
|
|
|
with a warning message.
|
2000-01-06 12:40:54 +00:00
|
|
|
.It Fl s
|
2000-07-05 22:09:50 +00:00
|
|
|
Do not add or delete prefixes dynamically.
|
|
|
|
Only statically configured prefixes, if any, will be advertised.
|
2000-01-06 12:40:54 +00:00
|
|
|
.El
|
2000-07-05 22:09:50 +00:00
|
|
|
.Pp
|
|
|
|
Use
|
2011-06-11 03:25:10 +00:00
|
|
|
.Dv SIGHUP
|
|
|
|
to reload the configuration file
|
|
|
|
.Pa /etc/rtadvd.conf .
|
|
|
|
If an invalid parameter is found in the configuration file upon the reload,
|
|
|
|
the entry will be ignored and the old configuration will be used.
|
2012-03-29 05:02:12 +00:00
|
|
|
When parameters in an existing entry are updated,
|
2011-06-11 03:25:10 +00:00
|
|
|
.Nm
|
|
|
|
will send Router Advertisement messages with the old configuration but
|
|
|
|
zero router lifetime to the interface first, and then start to send a new
|
|
|
|
message.
|
|
|
|
.Pp
|
|
|
|
Use
|
2000-07-05 22:09:50 +00:00
|
|
|
.Dv SIGTERM
|
|
|
|
to kill
|
|
|
|
.Nm
|
|
|
|
gracefully.
|
|
|
|
In this case,
|
|
|
|
.Nm
|
|
|
|
will transmit router advertisement with router lifetime 0
|
|
|
|
to all the interfaces
|
2011-06-06 03:06:43 +00:00
|
|
|
.Pq in accordance with RFC 4861 6.2.5 .
|
2000-01-06 12:40:54 +00:00
|
|
|
.Sh FILES
|
2000-10-29 16:44:10 +00:00
|
|
|
.Bl -tag -width Pa -compact
|
2000-02-15 18:21:38 +00:00
|
|
|
.It Pa /etc/rtadvd.conf
|
2000-01-06 12:40:54 +00:00
|
|
|
The default configuration file.
|
2000-07-05 22:09:50 +00:00
|
|
|
.It Pa /var/run/rtadvd.pid
|
2010-12-22 23:58:21 +00:00
|
|
|
The default process ID file.
|
2000-01-06 12:40:54 +00:00
|
|
|
.El
|
2010-05-13 12:08:11 +00:00
|
|
|
.Sh EXIT STATUS
|
|
|
|
.Ex -std
|
2000-01-06 12:40:54 +00:00
|
|
|
.Sh SEE ALSO
|
|
|
|
.Xr rtadvd.conf 5 ,
|
2013-02-25 16:47:09 +00:00
|
|
|
.Xr rtadvctl 8 ,
|
2001-07-06 16:46:48 +00:00
|
|
|
.Xr rtsol 8
|
2011-06-06 03:06:43 +00:00
|
|
|
.Rs
|
|
|
|
.%A Thomas Narten
|
|
|
|
.%A Erik Nordmark
|
|
|
|
.%A W. A. Simpson
|
|
|
|
.%A Hesham Soliman
|
|
|
|
.%T Neighbor Discovery for IP version 6 (IPv6)
|
|
|
|
.%R RFC 4861
|
|
|
|
.Re
|
|
|
|
.Rs
|
|
|
|
.%A Thomas Narten
|
|
|
|
.%A Erik Nordmark
|
|
|
|
.%A W. A. Simpson
|
|
|
|
.%T Neighbor Discovery for IP version 6 (IPv6)
|
|
|
|
.%R RFC 2461 (obsoleted by RFC 4861)
|
|
|
|
.Re
|
|
|
|
.Rs
|
|
|
|
.%A Richard Draves
|
|
|
|
.%T Default Router Preferences and More-Specific Routes
|
|
|
|
.%R draft-ietf-ipngwg-router-selection-xx.txt
|
|
|
|
.Re
|
|
|
|
.Rs
|
|
|
|
.%A J. Jeong
|
|
|
|
.%A S. Park
|
|
|
|
.%A L. Beloeil
|
|
|
|
.%A S. Madanapalli
|
|
|
|
.%T IPv6 Router Advertisement Options for DNS Configuration
|
|
|
|
.%R RFC 6106
|
|
|
|
.Re
|
2000-01-06 12:40:54 +00:00
|
|
|
.Sh HISTORY
|
|
|
|
The
|
|
|
|
.Nm
|
- supported a string notation for xxflags.
- deprecate routes#N, as it is hard to keep consistency with
rtprefixN. accept any number of "rtprefix", "rtrefix0",
..., "rtprefix99".
- deprecate "addrs#N", as it is difficult for users to keep
consistency with "addrN".
accept 100 prefix info in maximum - like "addr", "addr0"
... "addr99". WARNS=2 clean on netbsd.
old configuration file should work just fine.
behavior change:
previously, we rejected "addrN" if there's "addr", and we rejected
"addr" if there is "addrN". now we accept both without problem.
- when an advertised prefix configured from the kernel has been added
or invalidated, notice the change in a short delay.
- when invalidating a prefix, do not bark even if there is
inconsistency about prefix lifetimes.
- wrap more specific route info code into ROUTEINFO.
Obtained from: KAME
MFC after: 1 week
2003-08-15 19:13:53 +00:00
|
|
|
command first appeared in the WIDE Hydrangea IPv6 protocol stack kit.
|
|
|
|
.Sh BUGS
|
2001-06-11 12:39:29 +00:00
|
|
|
There used to be some text that recommended users not to let
|
|
|
|
.Nm
|
|
|
|
advertise Router Advertisement messages on an upstream link to avoid
|
|
|
|
undesirable
|
2000-07-05 22:09:50 +00:00
|
|
|
.Xr icmp6 4
|
2001-06-11 12:39:29 +00:00
|
|
|
redirect messages.
|
|
|
|
However, based on the later discussion in the IETF ipng working group,
|
|
|
|
all routers should rather advertise the messages regardless of
|
|
|
|
the network topology, in order to ensure reachability.
|