[radvd-devel-l] Multiple radvds in a local network
sfzhi at yahoo.com
Fri Aug 19 12:14:18 EDT 2011
Router advertisements are meant for hosts for stateless auto-configuration (i.e. for IP address assignment). They are not meant for other routers. They are not meant to distribute routing information. Router advertisement is not a routing protocol (it's router, not routing advertisement) and radvd is not a routing daemon.
Basically, there is no relationship between router advertisements and local routing tables. You can often see hosts adjusting local routing tables, but that happens as a result of IP address assignment, and not as a direct consequence of receiving router advertisement.
If you want routing tables to be updated then you need to use a "real" routing protocol and a real routing daemon (which, as I mentioned, radvd is not).
--- On Thu, 8/18/11, Marc Singer <elf at buici.com> wrote:
From: Marc Singer <elf at buici.com>
Subject: [radvd-devel-l] Multiple radvds in a local network
To: radvd-devel-l at litech.org
Date: Thursday, August 18, 2011, 10:56 PM
I have been looking at the relationship between the router advertisementsand local routing tables. For example, I've observed that enabling ipv6forwarding on a host will block updates to the default ipv6 route on that host
as learned by listening to router advertisements. My goals are similar to thosepursued by Mr. Nathan.
ATM, I'm still researching. I haven't been able to find documentation about
*how* router advertisements are expected to be used. For example, shouldthe kernel be expected to add routes to networks published as router advertisements?
Are there any suggestions as to where to read-up on the uses of router advertisements?
-----Inline Attachment Follows-----
radvd-devel-l mailing list : radvd-devel-l at litech.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the radvd-devel-l