rtsold, rtsol(8) | router solicitation daemon |
rtsol, rtsold(8) | router solicitation daemon |
RTSOLD(8) | MidnightBSD System Manager's Manual | RTSOLD(8) |
rtsold
, rtsol
— router solicitation daemon
rtsold |
[-dDfFmu1 ] [-M
script-name] [-O
script-name] [-p
pidfile] [-R
script-name] interface
... |
rtsold |
[-dDfFmu1 ] [-M
script-name] [-O
script-name] [-p
pidfile] [-R
script-name] -a |
rtsol |
[-dDu ] [-M
script-name] [-O
script-name] [-R
script-name] interface
... |
rtsol |
[-dDu ] [-M
script-name] [-O
script-name] [-R
script-name] -a |
rtsold
is the daemon program to send
ICMPv6 Router Solicitation messages on the specified interfaces. If a node
(re)attaches to a link, rtsold
sends some Router
Solicitations on the link destined to the link-local scope all-routers
multicast address to discover new routers and to get non link-local
addresses.
rtsold
should be used on IPv6 hosts
(non-router nodes) only.
If you invoke the program as rtsol
, it
will transmit probes from the specified interface,
without becoming a daemon. In other words, rtsol
behaves as “rtsold
-f1
interfaces”.
Specifically, rtsold
sends at most 3
Router Solicitations on an interface after one of the following events:
rtsold
daemon.rtsold
detects such failures by periodically
probing to see if the status of the interface is active or not. Note that
some network cards and drivers do not allow the extraction of link state.
In such cases, rtsold
cannot detect the change of
the interface status.-m
option is specified and
the rtsold
daemon cannot get the interface status.
This feature does not conform to the IPv6 neighbor discovery
specification, but is provided for mobile stations. The default interval
for router advertisements, which is on the order of 10 minutes, is
slightly long for mobile stations. This feature is provided for such
stations so that they can find new routers as soon as possible when they
attach to another link.Once rtsold
has sent a Router
Solicitation, and has received a valid Router Advertisement, it refrains
from sending additional solicitations on that interface, until the next time
one of the above events occurs.
When sending a Router Solicitation on an interface,
rtsold
includes a Source Link-layer address option
if the interface has a link-layer address.
rtsold
manages a per-interface parameter
to detect if a separate protocol is needed for configuration parameters
other than host's addresses. At the invocation time, the flag is FALSE, and
becomes TRUE when the daemon receives a router advertisement with the
OtherConfig flag being set. A script file can be specified to deal with the
case (see below). When rtsold
start resending router
solicitation messages by one of the conditions events, the daemon resets the
parameter because the event may indicate a change on the attached link.
Upon receipt of signal SIGUSR1
,
rtsold
will dump the current internal state into
/var/run/rtsold.dump.
The options are as follows:
-a
rtsold
will try to
find any non-loopback, non-point-to-point, IPv6-capable interfaces and
send router solicitation messages on all of them.-d
-D
-f
rtsold
from becoming a daemon (foreground
mode). Warning messages are generated to standard error instead of
syslog(3).-F
rtsold
operation. Without this option, the current
settings will be obeyed; if they are incompatible with proper operation,
warning messages will be generated, but Router Solicitations will still be
sent. The settings may be changed manually with
sysctl(8) and
ifconfig(8).-m
rtsold
sends probing packets to default routers
that have advertised Router Advertisements when the node (re)attaches to
an interface. Moreover, if the option is specified,
rtsold
periodically sends Router Solicitation on
an interface that does not support SIOCGIFMEDIA
ioctl.-1
-M
script-namertsold
will invoke
script-name with a single argument of the receiving
interface name, expecting the script will then start a protocol for the
managed configuration. script-name must be the
absolute path from root to the script file, be a regular file, and be
created by the same owner who runs rtsold
.-O
script-namertsold
will invoke
script-name with a single argument of the receiving
interface name, expecting the script will then start a protocol for the
other configuration. The script will not be run if the Managed
Configuration flag in the router advertisement is also TRUE.
script-name must be the absolute path from root to
the script file, be a regular file, and be created by the same owner who
runs rtsold
.-p
pidfilertsold
to
pidfile instead of the default PID file
/var/run/rtsold.pid.-R
script-nameRDNSS
(Recursive DNS Server) or
DNSSL
(DNS Search List) are encountered. The
information of DNS servers and DNS search domains will be sent to standard
input of this script. The
resolvconf(8)
script is used by default.-u
If -u
is specified, the interface name
in the script parameters will be
‘ifname:slaac:[RA-source-address]
’.
Otherwise it will be
‘ifname:slaac
’.
rtsold
.The rtsold
utility exits 0 on
success, and >0 if an error occurs.
The rtsold
command is based on the
rtsol
command, which first appeared in WIDE/KAME
IPv6 protocol stack kit. rtsol
is now integrated
into rtsold(8).
In some operating systems, when a PCMCIA network card is removed
and reinserted, the corresponding interface index is changed. However,
rtsold
assumes such changes will not occur, and
always uses the index that it got at invocation. As a result,
rtsold
may not work if you reinsert a network card.
In such a case, rtsold
should be killed and
restarted.
The IPv6 autoconfiguration specification assumes a
single-interface host. You may see kernel error messages if you try to
autoconfigure a host with multiple interfaces. Also, it seems contradictory
for rtsold
to accept multiple
interface arguments.
August 19, 2020 | midnightbsd-3.1 |