2005-08-10 17:09:08 +00:00
|
|
|
.\" $KAME: rtadvd.conf.5,v 1.50 2005/01/14 05:30:59 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$
|
|
|
|
.\"
|
2000-01-06 12:40:54 +00:00
|
|
|
.Dd May 17, 1998
|
|
|
|
.Dt RTADVD.CONF 5
|
2000-07-05 22:09:50 +00:00
|
|
|
.Os
|
2000-01-06 12:40:54 +00:00
|
|
|
.Sh NAME
|
|
|
|
.Nm rtadvd.conf
|
|
|
|
.Nd config file for router advertisement daemon
|
|
|
|
.Sh DESCRIPTION
|
2001-01-21 15:25:05 +00:00
|
|
|
This file describes how the router advertisement packets must be constructed
|
2000-01-06 12:40:54 +00:00
|
|
|
for each of the interfaces.
|
2001-01-21 15:25:05 +00:00
|
|
|
.Pp
|
2000-10-29 16:44:10 +00:00
|
|
|
As described in
|
|
|
|
.Xr rtadvd 8 ,
|
|
|
|
you do not have to set this configuration file up at all,
|
|
|
|
unless you need some special configurations.
|
2001-01-21 15:25:05 +00:00
|
|
|
You may even omit the file as a whole.
|
|
|
|
In such cases, the
|
2000-10-29 16:44:10 +00:00
|
|
|
.Nm rtadvd
|
|
|
|
daemon will automatically configure itself using default values
|
|
|
|
specified in the specification.
|
2000-01-06 12:40:54 +00:00
|
|
|
.Pp
|
2000-07-05 22:09:50 +00:00
|
|
|
It obeys the famous
|
2000-01-06 12:40:54 +00:00
|
|
|
.Xr termcap 5
|
|
|
|
file format.
|
|
|
|
Each line in the file describes a network interface.
|
|
|
|
Fields are separated by a colon
|
2000-07-05 22:09:50 +00:00
|
|
|
.Pq Sq \&: ,
|
2000-01-06 12:40:54 +00:00
|
|
|
and each field contains one capability description.
|
2001-01-21 15:25:05 +00:00
|
|
|
Lines may be concatenated by the
|
2000-07-05 22:09:50 +00:00
|
|
|
.Sq \e
|
|
|
|
character.
|
|
|
|
The comment marker is the
|
2001-01-21 15:25:05 +00:00
|
|
|
.Sq \&#
|
2000-07-05 22:09:50 +00:00
|
|
|
character.
|
2000-01-06 12:40:54 +00:00
|
|
|
.Sh CAPABILITIES
|
|
|
|
Capabilities describe the value to be filled into ICMPv6 router
|
2000-07-05 22:09:50 +00:00
|
|
|
advertisement messages and to control
|
2000-01-06 12:40:54 +00:00
|
|
|
.Xr rtadvd 8
|
|
|
|
behavior.
|
2001-01-21 15:25:05 +00:00
|
|
|
Therefore, you are encouraged to read IETF neighbor discovery documents
|
2000-07-05 22:09:50 +00:00
|
|
|
if you would like to modify the sample configuration file.
|
2000-01-06 12:40:54 +00:00
|
|
|
.Pp
|
2001-01-21 15:25:05 +00:00
|
|
|
Note that almost all items have default values.
|
2000-01-06 12:40:54 +00:00
|
|
|
If you omit an item, the default value of the item will be used.
|
|
|
|
.Pp
|
2000-07-05 22:09:50 +00:00
|
|
|
There are two items which control the interval of sending router advertisements.
|
2000-10-29 16:44:10 +00:00
|
|
|
These items can be omitted, then
|
|
|
|
.Nm rtadvd
|
|
|
|
will use the default values.
|
2000-01-06 12:40:54 +00:00
|
|
|
.Bl -tag -width indent
|
|
|
|
.It Cm \&maxinterval
|
|
|
|
(num) The maximum time allowed between sending unsolicited
|
|
|
|
multicast router advertisements
|
- 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
|
|
|
.Pq unit: seconds .
|
2000-07-05 22:09:50 +00:00
|
|
|
The default value is 600.
|
|
|
|
Its value must be no less than 4 seconds
|
2000-01-06 12:40:54 +00:00
|
|
|
and no greater than 1800 seconds.
|
|
|
|
.It Cm \&mininterval
|
|
|
|
(num) The minimum time allowed between sending unsolicited multicast
|
|
|
|
router advertisements
|
- 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
|
|
|
.Pq unit: seconds .
|
2000-01-06 12:40:54 +00:00
|
|
|
The default value is the one third of value of
|
2001-01-21 15:25:05 +00:00
|
|
|
.Cm maxinterval .
|
2000-01-06 12:40:54 +00:00
|
|
|
Its value must be no less than 3 seconds and no greater than .75 *
|
|
|
|
the value of
|
2001-01-21 15:25:05 +00:00
|
|
|
.Cm maxinterval .
|
2000-01-06 12:40:54 +00:00
|
|
|
.El
|
|
|
|
.Pp
|
|
|
|
The following items are for ICMPv6 router advertisement message
|
|
|
|
header.
|
2000-10-29 16:44:10 +00:00
|
|
|
These items can be omitted, then
|
|
|
|
.Nm rtadvd
|
|
|
|
will use the default values.
|
2000-01-06 12:40:54 +00:00
|
|
|
.Bl -tag -width indent
|
|
|
|
.It Cm \&chlim
|
|
|
|
(num) The value for Cur Hop Limit field.
|
|
|
|
The default value is 64.
|
|
|
|
.It Cm \&raflags
|
- 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
|
|
|
(str or num) A 8-bit flags field in router advertisement message header.
|
|
|
|
This field can be specified either as a case-sensitive string or as an
|
|
|
|
integer.
|
|
|
|
A sting consists of characters each of which corresponds to a
|
|
|
|
particular flag bit(s).
|
|
|
|
An integer should be the logical OR of all enabled bits.
|
2000-01-06 12:40:54 +00:00
|
|
|
Bit 7
|
- 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
|
|
|
.Po
|
|
|
|
.Li 'm' or 0x80
|
|
|
|
.Pc
|
2000-01-06 12:40:54 +00:00
|
|
|
means Managed address configuration flag bit,
|
|
|
|
and Bit 6
|
- 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
|
|
|
.Po
|
|
|
|
.Li 'o' or 0x40
|
|
|
|
.Pc
|
2000-01-06 12:40:54 +00:00
|
|
|
means Other stateful configuration flag bit.
|
2001-07-15 08:06:20 +00:00
|
|
|
Bit 4
|
- 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
|
|
|
.Po
|
|
|
|
.Li 0x10
|
|
|
|
.Pc
|
2001-06-11 12:39:29 +00:00
|
|
|
and Bit 3
|
- 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
|
|
|
.Po
|
|
|
|
.Li 0x08
|
|
|
|
.Pc
|
2001-06-11 12:39:29 +00:00
|
|
|
are used to encode router preference.
|
- 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
|
|
|
Bits 01
|
|
|
|
.Po
|
|
|
|
or 'h'
|
|
|
|
.Pc
|
|
|
|
means high, 00 means medium, and 11
|
|
|
|
.Po
|
|
|
|
or 'l'
|
|
|
|
.Pc
|
|
|
|
means low.
|
2003-07-30 07:33:10 +00:00
|
|
|
Bits 10 is reserved, and must not be specified.
|
- 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
|
|
|
There is no character to specify the medium preference explicitly.
|
|
|
|
The default value of the entire flag is 0
|
|
|
|
.Po
|
|
|
|
or a null string,
|
|
|
|
.Pc
|
2003-07-30 07:33:10 +00:00
|
|
|
which means no additional
|
|
|
|
configuration methods, and the medium router preference.
|
2000-01-06 12:40:54 +00:00
|
|
|
.It Cm \&rltime
|
|
|
|
(num) Router lifetime field
|
- 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
|
|
|
.Pq unit: seconds .
|
|
|
|
The value must be either zero or between
|
2003-07-30 07:33:10 +00:00
|
|
|
the value of
|
|
|
|
.Cm maxinterval
|
|
|
|
and 9000.
|
2001-01-21 15:25:05 +00:00
|
|
|
When
|
|
|
|
.Nm rtadvd
|
|
|
|
runs on a host, this value must explicitly set 0 on all the
|
|
|
|
advertising interfaces as described in
|
|
|
|
.Xr rtadvd 8 .
|
2000-01-06 12:40:54 +00:00
|
|
|
The default value is 1800.
|
|
|
|
.It Cm \&rtime
|
|
|
|
(num) Reachable time field
|
- 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
|
|
|
.Pq unit: milliseconds .
|
2000-01-06 12:40:54 +00:00
|
|
|
The default value is 0, which means unspecified by this router.
|
|
|
|
.It Cm \&retrans
|
|
|
|
(num) Retrans Timer field
|
- 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
|
|
|
.Pq unit: milliseconds .
|
2000-01-06 12:40:54 +00:00
|
|
|
The default value is 0, which means unspecified by this router.
|
|
|
|
.El
|
|
|
|
.Pp
|
|
|
|
The following items are for ICMPv6 prefix information option,
|
|
|
|
which will be attached to router advertisement header.
|
2000-10-29 16:44:10 +00:00
|
|
|
These items can be omitted, then
|
|
|
|
.Nm rtadvd
|
|
|
|
will automatically get appropriate prefixes from the kernel's routing table,
|
|
|
|
and advertise the prefixes with the default parameters.
|
- 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
|
|
|
Keywords other than
|
|
|
|
.Cm clockskew
|
|
|
|
can be augmented with a number, like
|
|
|
|
.Dq Li prefix2 ,
|
|
|
|
to specify multiple prefixes.
|
2000-01-06 12:40:54 +00:00
|
|
|
.Bl -tag -width indent
|
2001-06-11 12:39:29 +00:00
|
|
|
.It Cm \&clockskew
|
|
|
|
(num) Time skew to adjust link propagation delays and clock skews
|
2002-12-27 12:15:40 +00:00
|
|
|
between routers on the link
|
- 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
|
|
|
.Pq unit: seconds .
|
2001-06-11 12:39:29 +00:00
|
|
|
This value is used in consistency check for locally-configured and
|
|
|
|
advertised prefix lifetimes, and has its meaning when the local router
|
|
|
|
configures a prefix on the link with a lifetime that decrements in
|
|
|
|
real time.
|
|
|
|
If the value is 0, it means the consistency check will be skipped
|
|
|
|
for such prefixes.
|
|
|
|
The default value is 0.
|
2000-01-06 12:40:54 +00:00
|
|
|
.It Cm \&prefixlen
|
|
|
|
(num) Prefix length field.
|
|
|
|
The default value is 64.
|
|
|
|
.It Cm \&pinfoflags
|
- 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
|
|
|
(str or num) A 8-bit flags field in prefix information option.
|
|
|
|
This field can be specified either as a case-sensitive string or as an
|
|
|
|
integer.
|
|
|
|
A sting consists of characters each of which corresponds to a
|
|
|
|
particular flag bit(s).
|
|
|
|
An integer should be the logical OR of all enabled bits.
|
2000-01-06 12:40:54 +00:00
|
|
|
Bit 7
|
- 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
|
|
|
.Po
|
|
|
|
.Li 'l' or 0x80
|
|
|
|
.Pc
|
2000-01-06 12:40:54 +00:00
|
|
|
means On-link flag bit,
|
|
|
|
and Bit 6
|
- 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
|
|
|
.Po
|
|
|
|
.Li 'a' or 0x40
|
|
|
|
.Pc
|
2000-01-06 12:40:54 +00:00
|
|
|
means Autonomous address-configuration flag bit.
|
- 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
|
|
|
The default value is "la" or 0xc0, i.e., both bits are set.
|
2000-01-06 12:40:54 +00:00
|
|
|
.It Cm \&addr
|
|
|
|
(str) The address filled into Prefix field.
|
|
|
|
Since
|
|
|
|
.Dq \&:
|
|
|
|
is used for
|
|
|
|
.Xr termcap 5
|
|
|
|
file format as well as IPv6 numeric address, the field MUST be quoted by
|
|
|
|
doublequote character.
|
|
|
|
.It Cm \&vltime
|
|
|
|
(num) Valid lifetime field
|
- 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
|
|
|
.Pq unit: seconds .
|
2001-01-21 15:25:05 +00:00
|
|
|
The default value is 2592000 (30 days).
|
2001-06-11 12:39:29 +00:00
|
|
|
.It Cm \&vltimedecr
|
2005-08-10 17:09:08 +00:00
|
|
|
(bool) This item means the advertised valid lifetime will decrement
|
2001-06-11 12:39:29 +00:00
|
|
|
in real time, which is disabled by default.
|
2000-01-06 12:40:54 +00:00
|
|
|
.It Cm \&pltime
|
|
|
|
(num) Preferred lifetime field
|
- 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
|
|
|
.Pq unit: seconds .
|
2001-01-21 15:25:05 +00:00
|
|
|
The default value is 604800 (7 days).
|
2001-06-11 12:39:29 +00:00
|
|
|
.It Cm \&pltimedecr
|
2005-08-10 17:09:08 +00:00
|
|
|
(bool) This item means the advertised preferred lifetime will decrement
|
2001-06-11 12:39:29 +00:00
|
|
|
in real time, which is disabled by default.
|
2000-01-06 12:40:54 +00:00
|
|
|
.El
|
|
|
|
.Pp
|
2000-10-29 16:44:10 +00:00
|
|
|
The following item is for ICMPv6 MTU option,
|
2000-01-06 12:40:54 +00:00
|
|
|
which will be attached to router advertisement header.
|
2000-10-29 16:44:10 +00:00
|
|
|
This item can be omitted, then
|
|
|
|
.Nm rtadvd
|
|
|
|
will use the default value.
|
2000-01-06 12:40:54 +00:00
|
|
|
.Bl -tag -width indent
|
|
|
|
.It Cm \&mtu
|
|
|
|
(num or str) MTU (maximum transmission unit) field.
|
|
|
|
If 0 is specified, it means that the option will not be included.
|
2000-07-05 22:09:50 +00:00
|
|
|
The default value is 0.
|
|
|
|
If the special string
|
2000-01-06 12:40:54 +00:00
|
|
|
.Dq auto
|
|
|
|
is specified for this item, MTU option will be included and its value
|
|
|
|
will be set to the interface MTU automatically.
|
|
|
|
.El
|
|
|
|
.Pp
|
|
|
|
The following item controls ICMPv6 source link-layer address option,
|
|
|
|
which will be attached to router advertisement header.
|
2000-10-29 16:44:10 +00:00
|
|
|
As noted above, you can just omit the item, then
|
|
|
|
.Nm rtadvd
|
|
|
|
will use the default value.
|
2000-01-06 12:40:54 +00:00
|
|
|
.Bl -tag -width indent
|
|
|
|
.It Cm \&nolladdr
|
|
|
|
(bool) By default
|
- 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
|
|
|
.Po
|
|
|
|
if
|
2000-01-06 12:40:54 +00:00
|
|
|
.Cm \&nolladdr
|
- 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
|
|
|
is not specified
|
|
|
|
.Pc ,
|
2000-01-06 12:40:54 +00:00
|
|
|
.Xr rtadvd 8
|
|
|
|
will try to get link-layer address for the interface from the kernel,
|
|
|
|
and attach that in source link-layer address option.
|
|
|
|
If this capability exists,
|
|
|
|
.Xr rtadvd 8
|
|
|
|
will not attach source link-layer address option to
|
|
|
|
router advertisement packets.
|
|
|
|
.El
|
|
|
|
.Pp
|
- 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
|
|
|
The following item controls ICMPv6 home agent information option,
|
2001-06-11 12:39:29 +00:00
|
|
|
which was defined with mobile IPv6 support.
|
|
|
|
It will be attached to router advertisement header just like other options do.
|
|
|
|
.Bl -tag -width indent
|
|
|
|
.It Cm \&hapref
|
|
|
|
(num) Specifies home agent preference.
|
|
|
|
If set to non-zero,
|
|
|
|
.Cm \&hatime
|
|
|
|
must be present as well.
|
|
|
|
.It Cm \&hatime
|
|
|
|
(num) Specifies home agent lifetime.
|
|
|
|
.El
|
|
|
|
.Pp
|
|
|
|
When mobile IPv6 support is turned on for
|
|
|
|
.Xr rtadvd 8 ,
|
|
|
|
advertisement interval option will be attached to router advertisement
|
|
|
|
packet, by configuring
|
|
|
|
.Cm \&maxinterval
|
|
|
|
explicitly.
|
|
|
|
.Pp
|
|
|
|
The following items are for ICMPv6 route information option,
|
|
|
|
which will be attached to router advertisement header.
|
|
|
|
These items are optional.
|
- 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
|
|
|
Each items can be augmented with number, like
|
|
|
|
.Dq Li rtplen2 ,
|
|
|
|
to specify multiple routes.
|
2001-06-11 12:39:29 +00:00
|
|
|
.Bl -tag -width indent
|
- 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
|
|
|
.It Cm \&rtprefix
|
2001-06-11 12:39:29 +00:00
|
|
|
(str) The prefix filled into the Prefix field of route information option.
|
|
|
|
Since
|
|
|
|
.Dq \&:
|
|
|
|
is used for
|
|
|
|
.Xr termcap 5
|
|
|
|
file format as well as IPv6 numeric address, the field MUST be quoted by
|
|
|
|
doublequote character.
|
- 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
|
|
|
.It Cm \&rtplen
|
|
|
|
(num) Prefix length field in route information option.
|
|
|
|
The default value is 64.
|
|
|
|
.It Cm \&rtflags
|
|
|
|
(str or num) A 8-bit flags field in route information option.
|
|
|
|
Currently only the preference values are defined.
|
|
|
|
The notation is same as that of the raflags field.
|
|
|
|
Bit 4
|
|
|
|
.Po
|
|
|
|
.Li 0x10
|
|
|
|
.Pc
|
|
|
|
and
|
2003-09-14 13:41:59 +00:00
|
|
|
Bit 3
|
- 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
|
|
|
.Po
|
|
|
|
.Li 0x08
|
|
|
|
.Pc
|
|
|
|
are used to encode the route preference for the route.
|
2004-07-02 22:50:25 +00:00
|
|
|
The default value is 0x00, i.e., medium preference.
|
- 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
|
|
|
.It Cm \&rtltime
|
2001-06-11 12:39:29 +00:00
|
|
|
(num) route lifetime field in route information option.
|
- 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
|
|
|
.Pq unit: seconds .
|
|
|
|
Since the specification does not define the default value of this
|
|
|
|
item, the value for this item should be specified by hand.
|
|
|
|
However,
|
|
|
|
.Nm rtadvd
|
|
|
|
allows this item to be unspecified, and uses the router lifetime
|
|
|
|
as the default value in such a case, just for compatibility with an
|
|
|
|
old version of the program.
|
2001-06-11 12:39:29 +00:00
|
|
|
.El
|
- 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
|
|
|
.Pp
|
|
|
|
In the above list, each keyword beginning with
|
|
|
|
.Dq Li rt
|
|
|
|
could be replaced with the one beginning with
|
|
|
|
.Dq Li rtr
|
|
|
|
for backward compatibility reason.
|
|
|
|
For example,
|
|
|
|
.Cm rtrplen
|
|
|
|
is accepted instead of
|
|
|
|
.Cm rtplen .
|
|
|
|
However, keywords that start with
|
|
|
|
.Dq Li rtr
|
|
|
|
have basically been obsoleted, and should not be used any more.
|
|
|
|
.Pp
|
2000-01-06 12:40:54 +00:00
|
|
|
You can also refer one line from another by using
|
|
|
|
.Cm tc
|
|
|
|
capability.
|
|
|
|
See
|
|
|
|
.Xr termcap 5
|
|
|
|
for details on the capability.
|
2000-11-17 11:44:16 +00:00
|
|
|
.Sh EXAMPLES
|
2001-01-21 15:25:05 +00:00
|
|
|
As presented above, all of the advertised parameters have default values
|
|
|
|
defined in specifications, and hence you usually do not have to set them
|
|
|
|
by hand, unless you need special non-default values.
|
|
|
|
It can cause interoperability problem if you use an ill-configured
|
|
|
|
parameter.
|
|
|
|
.Pp
|
|
|
|
To override a configuration parameter, you can specify the parameter alone.
|
|
|
|
With the following configuration,
|
|
|
|
.Xr rtadvd 8
|
|
|
|
overrides the router lifetime parameter for the
|
|
|
|
.Li ne0
|
|
|
|
interface.
|
|
|
|
.Bd -literal -offset
|
|
|
|
ne0:\\
|
|
|
|
:rltime#0:
|
|
|
|
.Ed
|
|
|
|
.Pp
|
|
|
|
The following example manually configures prefixes advertised from the
|
|
|
|
.Li ef0
|
|
|
|
interface.
|
|
|
|
The configuration must be used with the
|
|
|
|
.Fl s
|
|
|
|
option to
|
|
|
|
.Xr rtadvd 8 .
|
|
|
|
.Bd -literal -offset
|
|
|
|
ef0:\\
|
- 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
|
|
|
:addr="3ffe:501:ffff:1000::":prefixlen#64:
|
2001-01-21 15:25:05 +00:00
|
|
|
.Ed
|
|
|
|
.Pp
|
|
|
|
The following example presents the default values in an explicit manner.
|
|
|
|
The configuration is provided just for reference purposes;
|
|
|
|
YOU DO NOT NEED TO HAVE IT AT ALL.
|
2000-01-06 12:40:54 +00:00
|
|
|
.Bd -literal -offset
|
2001-01-21 15:25:05 +00:00
|
|
|
default:\\
|
|
|
|
:chlim#64:raflags#0:rltime#1800:rtime#0:retrans#0:\\
|
- 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
|
|
|
:pinfoflags="la":vltime#2592000:pltime#604800:mtu#0:
|
2001-01-21 15:25:05 +00:00
|
|
|
ef0:\\
|
- 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
|
|
|
:addr="3ffe:501:ffff:1000::":prefixlen#64:tc=default:
|
2000-01-06 12:40:54 +00:00
|
|
|
.Ed
|
|
|
|
.Sh SEE ALSO
|
|
|
|
.Xr termcap 5 ,
|
|
|
|
.Xr rtadvd 8 ,
|
|
|
|
.Xr rtsol 8
|
2004-07-02 22:50:25 +00:00
|
|
|
.Rs
|
|
|
|
.%A Thomas Narten
|
|
|
|
.%A Erik Nordmark
|
|
|
|
.%A W. A. Simpson
|
|
|
|
.%T Neighbor Discovery for IP version 6 (IPv6)
|
|
|
|
.%R RFC 2461
|
|
|
|
.Re
|
|
|
|
.Rs
|
|
|
|
.%A Richard Draves
|
|
|
|
.%T Default Router Preferences and More-Specific Routes
|
|
|
|
.%R draft-ietf-ipngwg-router-selection-xx.txt
|
|
|
|
.Re
|
2000-01-06 12:40:54 +00:00
|
|
|
.Sh HISTORY
|
|
|
|
The
|
|
|
|
.Xr rtadvd 8
|
|
|
|
and the configuration file
|
|
|
|
.Nm
|
|
|
|
first appeared in WIDE Hydrangea IPv6 protocol stack kit.
|
|
|
|
.\" .Sh BUGS
|
|
|
|
.\" (to be written)
|