Difference between revisions of "Bering-uClibc 4.x - User Guide - IPv6 Networking - Configure Router Advertisements"

From bering-uClibc
Jump to: navigation, search
m (Corrected prefix address)
(Troubleshooting)
Line 46: Line 46:
  
 
==Troubleshooting==
 
==Troubleshooting==
TODO
 
  
 +
=== Check your configuration ===
 +
* <code class="filename">radvd</code> checks your configuration syntax if called with option '''-c'''.
 +
* To add comments to the radvd configuration file <code class="filename">/etc/radvd.conf</code> use the hash sign ('''#'''). Make shure have a space after the hash, otherwise <code class="filename">radvd</code> may detect an error while reading the configuration file.
 +
* To see what <code class="filename">radvd</code> advertises to your LAN, install a radvd package from your Linux distributions package repository and run <code class="filename">radvdump</code>.
  
 
----
 
----

Revision as of 17:16, 16 January 2011

IPv6 Networking - Configure Radvd
Prev Bering-uClibc 4.x - User Guide Next


Introduction

Every IPv6 router should be configured to run a Router Advertisement daemon in order to comply with the Router Discovery (RD) aspects of Neighbour Discovery (ND) as defined in RFC 2461. For Bering-uClibc 4.x, the Router Advertisement service is implemented by the radvd.lrp Package. This installs the de facto standard Router Advertisement daemon for Linux, radvd, which is described on the radvd Home Page.

Configuration

Configuration of radvd is relatively straightforward. There is a single configuration file, /etc/radvd.conf, which defines the Router Advertisement behaviour for each network interface. It is easiest to consider an example:

interface eth1
{
        AdvSendAdvert on;
        AdvManagedFlag off;
        prefix 2001:db8:1:1::/64
        {
                AdvOnLink on;
                AdvAutonomous on;
        };
};

The meaning of the various entries is:

interface eth1 
Indicates that this configuration block refers to the eth1 network interface.
AdvSendAdvert on; 
Indicates that radvd should send Router Advertisements and respond to Router Solicitations on this interface.
AdvManagedFlag off; 
Indicates that hosts should not also use DHCPv6 to acquire additional details about the network configuration.
See the next page for more information about DHCPv6.
prefix 2001:db8:1:1::/64 
Defines the IPv6 address prefix to be used for this network interface.
Note that the 2001:db8::/32 address range is specifically reserved for IPv6 documentation examples and should be replaced by part of your own allocated IPv6 address range.
AdvOnLink on; 
Indicates that this address prefix is specific to this network link so all hosts sharing this address prefix can be reached directly (i.e. in one hop) using this network interface.
AdvAutonomous on; 
Indicates that hosts may use this prefix for "autonomous" or "stateless" IPv6 address configuration as described in RFC 2462 which has been obsoleted by RFC 4862.

Additional interface configuration blocks can be added if there are additional IPv6 networks for radvd to manage.

Once configuration is complete the radvd daemon must be started:

svi radvd start

Correct Operation

If everything is working properly hosts will automatically derive their own IPv6 addresses based on the defined prefix in addition to allocating link-local addresses to each network interface.

Troubleshooting

Check your configuration

  • radvd checks your configuration syntax if called with option -c.
  • To add comments to the radvd configuration file /etc/radvd.conf use the hash sign (#). Make shure have a space after the hash, otherwise radvd may detect an error while reading the configuration file.
  • To see what radvd advertises to your LAN, install a radvd package from your Linux distributions package repository and run radvdump.

Prev Up Next