Router Advertisements

radvd (the service responsible for this functionality) is the router advertisement daemon for IPv6. It listens to router solicitations and sends router advertisements as described in “Neighbor Discovery for IP Version 6 (IPv6)” (RFC 4861). With these advertisements hosts can automatically configure their addresses and some other parameters. It also defines “Neighbor Discovery Optimization for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs)” (RFC6775). They also can choose a default router based on these advertisements.

Attention

Dnsmasq is the default RA daemon in new installations, deactivate its Router Advertisement setting if you want to use radvd.

General Settings

The service can be configured in Services ‣ Router Advertisements.

Option

Description

Enabled

Enable or disable this entry. If “Track Interface (legacy)” is used, an existing disabled entry will also deactivate advertisements on that interface. Alternatively, switch to “Identity association” for full manual configuration if needed.

Interface

Choose the interface that should send Router Advertisements. A prefix will be constructed from the primary IP of that interface, which is assigned by “Identity association” or “Track interface (legacy)” IPv6 modes of said interface. If additional virtual IP addresses exist on this interface, their prefixes will also be advertised.

Mode

Select which flags to set in Router Advertisements sent from this interface.

Minimum interval

The minimum time allowed between sending unsolicited multicast router advertisements from the interface, in seconds.

Maximum interval

The maximum time allowed between sending unsolicited multicast router advertisements from the interface, in seconds.

Recursive DNS Servers (RDNSS)

The default is to use this interface IP address with an enabled DNS service or the configured global DNS servers. You may specify up to three explicit servers here instead.

DNS Search List (DNSSL)

The default is to use the domain name of this system as the DNSSL option. You may specify explicit domains here instead.

Routes

Routes are specified in CIDR format. The prefix of a route definition should be network prefix; it can be used to advertise more specific routes to the hosts.

Router Advertisements (Mode)

The mode selection contains some predefined settings for radvd, which influence a set of configuration options and are intended for specific implementation scenarios. They define the type of client deployment used in your network.


Router Only

Only advertise this router, clients are using static IPv6 addresses

Unmanaged

Clients will use Stateless Address Autoconfiguration (SLAAC), without other (non-address) information being provided.

Managed

Stateful configuration, address configuration provided by DHCPv6

Assisted

Stateful configuration, address configuration provided by DHCPv6, although advertised routes can also be used on Stateless Address Autoconfiguration setups (SLAAC).

Stateless

Clients will use Stateless Address Autoconfiguration (SLAAC)

A detailed overview of the radvd settings determined by the mode can be found below:

scope

Settings

Router Only

Unmanaged

Managed

Assisted

Stateless

Per interface

AdvManagedFlag

X

X

AdvOtherConfigFlag

X

X

X

Per prefix

AdvOnLink

X

X

X

X

AdvAutonomous

X

X

X

Note

Technical details about the options can be found in the man page of radvd

Configuration examples

DHCPv6

Router Advertisements are sufficient for clients to auto-generate a SLAAC address, receive a default gateway and a DNS server. These are the basic requirement for IPv6 connectivity.

There can be advanced requirements like hostname registration, static reservations and DHCPv6 options.

For these cases, there are two DHCPv6 servers available: KEA and Dnsmasq. As Dnsmasq is best used with its own router advertisement functionality, KEA is the most logical choice to pair with radvd. This is especially true for HA setups, as KEA can synchronize IPv6 leases.

Attention

A combination of KEA and radvd requires a static WAN prefix, as KEA cannot track prefixes dynamically.

To advertise a DHCPv6 server to clients, configure the available modes to your requirements.

High availability

For high availability with IPv6, static prefixes are a requirement for seamless failover.

You can follow this setup example: Configure CARP