radvd IPv6 Router Advertisement Daemon

repository·master·Indexed 42 days ago

https://github.com/radvd-project/radvd

An IPv6 router advertisement daemon that listens for router solicitations and sends router advertisements per RFC 4861 to enable automatic host address configuration and default router selection.

Tokens
569
Snippets
1
Records
4
Agent score
4%

What's inside radvd

  1. Understand the scope and limitations of radvd

    master

    It is important to understand what radvd is and is not to avoid common configuration mistakes:

    • It is a route advertising daemon, not a configuration tool. radvd does not automatically configure the router's own interfaces, addresses, or routes. You must set up the router's networking (addresses, routes, etc.) manually or via system initscripts before running radvd.
    • It is not a routing or forwarding daemon. radvd does not perform unicast or multicast routing. You must configure any necessary routing/forwarding in the system first; radvd only advertises prefixes to hosts.
    • It does not automatically configure addresses from upstream RAs. By specification, routers ignore Router Advertisements (RAs). To use prefixes from upstream, you may need manual configuration, prefix delegation (RFC3633), or proxy-ND.
    • It does not support setting up downstream interface addresses/routes from dynamic prefixes. If you have a dynamic prefix (e.g., /48), radvd can advertise /64 prefixes from it (with special support for 6to4 upstream interfaces), but it assumes interface addresses and routes are already set up manually.
  2. Install radvd from source

    master

    To install radvd, you must first run the configure script with your desired paths, then build and install using make. On BSD systems, you may need to use gmake instead of make.

    ./configure --prefix=/usr/local --sysconfdir=/etc --mandir=/usr/share/man
    make
    make install
  3. Configure radvd

    master

    Configuration for radvd is handled via configuration files. For detailed syntax and usage, refer to the following resources:

    • INTRO.html (Documentation)
    • radvd.conf(8) (Manual page)
    • radvd.conf.example (Example configuration file)
  4. Review RFC implementation status

    master

    The implementation status of various IPv6 RFCs in radvd is tracked using the following legend:

    • COMPLETED: Every part of the RFC is implemented
    • MOST: The majority of the RFC is implemented
    • PARTIAL: Minimal or only parts of the RFC are implemented
    • WONTFIX: The RFC will not be implemented
    • NONE: The RFC is NOT implemented
    • OBSOLETE: The RFC has been superseded
    • DUMP: Only supported by radvddump
    • UNKNOWN: Implementation status unknown