[radvd-devel-l] radvd FAQ added to README
pekkas at netcore.fi
Sun Nov 13 09:20:14 EST 2005
Based on a comment by Henrik Levkowetz, I've added a short FAQ
(currently only about radvd's applicability) to CVS.
Suggestions for changes/additions/etc to the FAQ are appreciated.
Pekka Savola "You each name yourselves king, yet the
Netcore Oy kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
-------------- next part --------------
RCS file: /work/cvsroot/radvd/CHANGES,v
retrieving revision 1.50
diff -u -r1.50 CHANGES
--- CHANGES 28 Oct 2005 09:25:38 -0000 1.50
+++ CHANGES 13 Nov 2005 14:16:30 -0000
@@ -1,5 +1,7 @@
$Id: CHANGES,v 1.50 2005/10/28 09:25:38 psavola Exp $
+11/13/2005 Create a short FAQ in README file.
10/28/2005 Get interface MTU automatically, so that you can
use jumboframes and advertise MTU >1500.
RCS file: /work/cvsroot/radvd/README,v
retrieving revision 1.6
diff -u -r1.6 README
--- README 14 Nov 2001 19:58:10 -0000 1.6
+++ README 13 Nov 2005 14:16:30 -0000
@@ -7,14 +7,53 @@
./configure --prefix=/usr/local --sysconfdir=/etc --mandir=/usr/share/man
-The configure script will now try to guess where your IPv6 libraries and
-include files are if you don't specify them explicitly via LDFLAGS or
-CPPFLAGS respectively. Currently it will search in /usr/inet6/(include|lib)
-and /usr/ipv6/(include|lib). If separate IPv6 libraries are not necessary
-for your system, like recent Linux distributions, you will not need to
-specify this option. You still have to use the --prefix option to specify
-the install tree though. The default prefix is /usr/local.
See configure --help for additional command line arguments.
-Run make and make install.
+Run make and make install.
+See INTRO.html, radvd.conf(8) and radvd.conf.example.
+Frequently Asked Questions:
+Setting up radvd is very simple, so the most frequently asked
+questions have been about what radvd _doesn't_ do...
+ 1. How do I set up the router running radvd to automatically
+ configure an address from the prefix advertised in Route
+ Advertisements from upstream?
+ -- You don't. By the specification, routers ignore RAs.
+ You'll probably need to use manual configuration. But you
+ can't use the same prefix on two links in any case unless you
+ use something like proxy-ND (draft-ietf-ipv6-ndproxy-04.txt)
+ or prefix delegation (e.g., manually or with RFC3633),
+ so you may need to re-think your topology.
+ 2. How do I set up the router running radvd to automatically
+ configure the interfaces to use an EUI64-based address?
+ -- You don't. The design philosophy of radvd is that it's
+ not the _router's_ configuration tool, but a route advertising
+ daemon. You'll need to set up all the addresses, routes, etc.
+ yourself. These tasks are something that system initscripts
+ could possibly do instead.
+ 3. I have a dynamic /48 prefix. How do I set up radvd to:
+ a) set up interface addresses on downstream interfaces, and
+ b) advertise /64 prefixes from on downstream interfaces?
+ -- For a), this isn't supported. For b), radvd includes special
+ support for 6to4 upstream interface only. This should probably
+ be done in the initscripts or manually. (Though if someone were
+ to send a patch for b), it might be incorporated.)
+ 4. How do I set up radvd to do either unicast or multicast routing?
+ -- You don't. Radvd is not a routing or forwarding daemon.
+ You need to set any appropriate routing/forwarding first,
+ and then radvd to only advertise the prefixes to hosts as
More information about the radvd-devel-l