OpenBSD manual page server

NAME

rad — router advertisement daemon

SYNOPSIS

DESCRIPTION

rad is an IPv6 router advertisement daemon. It periodically sends IPv6 router advertisement messages with prefix and default router information. Clients like slaacd(8) use these to configure IPv6 addresses on network interfaces and set default routes. Additionally it listens for IPv6 router solicitation messages and responds with router advertisements.

rad is usually started at boot time, and can be enabled by setting the following in /etc/rc.conf.local:

See rc(8) and rc.conf(8) for more information on the boot process and enabling daemons.

A running rad can be controlled with the ractl(8) utility.

The options are as follows:

-d

Do not daemonize. If this option is specified, rad will run in the foreground and log to stderr.

-f file

Specify an alternative configuration file.

-n

Configtest mode. Only check the configuration file for validity.

-s socket

Use an alternate location for the default control socket.

-v

Produce more verbose output.

FILES

/etc/rad.conf

Default rad configuration file.

/var/run/rad.sock

UNIX-domain socket used for communication with ractl(8).

SEE ALSO

rad.conf(5), ractl(8), slaacd(8)

STANDARDS

R. Draves and D. Thaler, Default Router Preferences and More-Specific Routes, RFC 4191, November 2005.

R. Hinden and S. Deering, IP Version 6 Addressing Architecture, RFC 4291, February 2006.

T. Narten, E. Nordmark, W. Simpson, and H. Soliman, Neighbor Discovery for IP version 6 (IPv6), RFC 4861, September 2007.

A. Yourtchenko and L. Colitti, Reducing Energy Consumption of Router Advertisements, RFC 7772, February 2016.

J. Jeong, S. Park, L. Beloeil, and S. Madanapalli, IPv6 Router Advertisement Options for DNS Configuration, RFC 8106, March 2017.

HISTORY

The rad program first appeared in OpenBSD 6.4.

AUTHORS

The rad program was written by Florian Obser <florian@openbsd.org>.

CAVEATS

When running rad on a carp(4) interface, it is recommended to either disable SOIIs (persistent Semantically Opaque Interface Identifiers) on the interface with ifconfig(8), or ensure that all CARP peers have the same SOII key stored in /etc/soii.key. Otherwise the default IPv6 router's link-local address will change during CARP failover, which temporarily disrupts connectivity of IPv6 autoconf clients.