1.\" $KAME: rtadvd.8,v 1.24 2002/05/31 16:16:08 jinmei Exp $ 2.\" 3.\" Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project. 4.\" All rights reserved. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: 9.\" 1. Redistributions of source code must retain the above copyright 10.\" notice, this list of conditions and the following disclaimer. 11.\" 2. Redistributions in binary form must reproduce the above copyright 12.\" notice, this list of conditions and the following disclaimer in the 13.\" documentation and/or other materials provided with the distribution. 14.\" 3. Neither the name of the project nor the names of its contributors 15.\" may be used to endorse or promote products derived from this software 16.\" without specific prior written permission. 17.\" 18.\" THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND 19.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 20.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 21.\" ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE 22.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 23.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 24.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 25.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 26.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 27.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 28.\" SUCH DAMAGE. 29.\" 30.\" $FreeBSD$ 31.\" 32.Dd December 22, 2010 33.Dt RTADVD 8 34.Os 35.Sh NAME 36.Nm rtadvd 37.Nd router advertisement daemon 38.Sh SYNOPSIS 39.Nm 40.Op Fl dDfRs 41.Op Fl c Ar configfile 42.Op Fl F Ar dumpfile 43.Op Fl M Ar ifname 44.Op Fl p Ar pidfile 45.Ar interface ... 46.Sh DESCRIPTION 47.Nm 48sends router advertisement packets to the specified 49.Ar interfaces . 50.Pp 51The program will daemonize itself on invocation. 52It will then send router advertisement packets periodically, as well 53as in response to router solicitation messages sent by end hosts. 54.Pp 55Router advertisements can be configured on a per-interface basis, as 56described in 57.Xr rtadvd.conf 5 . 58.Pp 59If there is no configuration file entry for an interface, 60or if the configuration file does not exist altogether, 61.Nm 62sets all the parameters to their default values. 63In particular, 64.Nm 65reads all the interface routes from the routing table and advertises 66them as on-link prefixes. 67.Pp 68.Nm 69also watches the routing table. 70If an interface direct route is 71added on an advertising interface and no static prefixes are 72specified by the configuration file, 73.Nm 74adds the corresponding prefix to its advertising list. 75.Pp 76Similarly, when an interface direct route is deleted, 77.Nm 78will start advertising the prefixes with zero valid and preferred 79lifetimes to help the receiving hosts switch to a new prefix when 80renumbering. 81Note, however, that the zero valid lifetime cannot invalidate the 82autoconfigured addresses at a receiving host immediately. 83According to the specification, the host will retain the address 84for a certain period, which will typically be two hours. 85The zero lifetimes rather intend to make the address deprecated, 86indicating that a new non-deprecated address should be used as the 87source address of a new connection. 88This behavior will last for two hours. 89Then 90.Nm 91will completely remove the prefix from the advertising list, 92and succeeding advertisements will not contain the prefix information. 93.Pp 94Moreover, if the status of an advertising interface changes, 95.Nm 96will start or stop sending router advertisements according 97to the latest status. 98.Pp 99The 100.Fl s 101option may be used to disable this behavior; 102.Nm 103will not watch the routing table and the whole functionality described 104above will be suppressed. 105.Pp 106Basically, hosts MUST NOT send Router Advertisement messages at any 107time (RFC 4861, Section 6.2.3). 108However, it would sometimes be useful to allow hosts to advertise some 109parameters such as prefix information and link MTU. 110Thus, 111.Nm 112can be invoked if router lifetime is explicitly set zero on every 113advertising interface. 114.Pp 115The command line options are: 116.Bl -tag -width indent 117.\" 118.It Fl c 119Specify an alternate location, 120.Ar configfile , 121for the configuration file. 122By default, 123.Pa /etc/rtadvd.conf 124is used. 125.It Fl d 126Print debugging information. 127.It Fl D 128Even more debugging information is printed. 129.It Fl f 130Foreground mode (useful when debugging). 131Log messages will be dumped to stderr when this option is specified. 132.It Fl F 133Specify an alternative file in which to dump internal states when 134.Nm 135receives signal 136.Dv SIGUSR1 . 137The default is 138.Pa /var/run/rtadvd.dump . 139.It Fl M 140Specify an interface to join the all-routers site-local multicast group. 141By default, 142.Nm 143tries to join the first advertising interface appearing on the command 144line. 145This option has meaning only with the 146.Fl R 147option, which enables routing renumbering protocol support. 148.It Fl p 149Specify an alternative file in which to store the process ID. 150The default is 151.Pa /var/run/rtadvd.pid. 152.It Fl R 153Accept router renumbering requests. 154If you enable it, certain IPsec setup is suggested for security reasons. 155This option is currently disabled, and is ignored by 156.Nm 157with a warning message. 158.It Fl s 159Do not add or delete prefixes dynamically. 160Only statically configured prefixes, if any, will be advertised. 161.El 162.Pp 163Upon receipt of signal 164.Dv SIGUSR1 , 165.Nm 166will dump the current internal state into 167.Pa /var/run/rtadvd.dump 168or the file specified with option 169.Fl F . 170.Pp 171Use 172.Dv SIGHUP 173to reload the configuration file 174.Pa /etc/rtadvd.conf . 175If an invalid parameter is found in the configuration file upon the reload, 176the entry will be ignored and the old configuration will be used. 177When parameters in an existing entry are updated, 178.Nm 179will send Router Advertisement messages with the old configuration but 180zero router lifetime to the interface first, and then start to send a new 181message. 182.Pp 183Use 184.Dv SIGTERM 185to kill 186.Nm 187gracefully. 188In this case, 189.Nm 190will transmit router advertisement with router lifetime 0 191to all the interfaces 192.Pq in accordance with RFC 4861 6.2.5 . 193.Sh FILES 194.Bl -tag -width Pa -compact 195.It Pa /etc/rtadvd.conf 196The default configuration file. 197.It Pa /var/run/rtadvd.pid 198The default process ID file. 199.It Pa /var/run/rtadvd.dump 200The default file in which 201.Nm 202dumps its internal state. 203.El 204.Sh EXIT STATUS 205.Ex -std 206.Sh SEE ALSO 207.Xr rtadvd.conf 5 , 208.Xr rtsol 8 209.Rs 210.%A Thomas Narten 211.%A Erik Nordmark 212.%A W. A. Simpson 213.%A Hesham Soliman 214.%T Neighbor Discovery for IP version 6 (IPv6) 215.%R RFC 4861 216.Re 217.Rs 218.%A Thomas Narten 219.%A Erik Nordmark 220.%A W. A. Simpson 221.%T Neighbor Discovery for IP version 6 (IPv6) 222.%R RFC 2461 (obsoleted by RFC 4861) 223.Re 224.Rs 225.%A Richard Draves 226.%T Default Router Preferences and More-Specific Routes 227.%R draft-ietf-ipngwg-router-selection-xx.txt 228.Re 229.Rs 230.%A J. Jeong 231.%A S. Park 232.%A L. Beloeil 233.%A S. Madanapalli 234.%T IPv6 Router Advertisement Options for DNS Configuration 235.%R RFC 6106 236.Re 237.Sh HISTORY 238The 239.Nm 240command first appeared in the WIDE Hydrangea IPv6 protocol stack kit. 241.Sh BUGS 242There used to be some text that recommended users not to let 243.Nm 244advertise Router Advertisement messages on an upstream link to avoid 245undesirable 246.Xr icmp6 4 247redirect messages. 248However, based on the later discussion in the IETF ipng working group, 249all routers should rather advertise the messages regardless of 250the network topology, in order to ensure reachability. 251