[radvd-devel-l] Linux and specific routes
sega01 at gmail.com
Mon Feb 2 12:24:00 EST 2009
I have finally obtained my answer. I ended up reading RFC 4191,
glancing at RFC 2461, and looking at Linux's source code, but found
what I was looking for. It turns out that "route information option"
is more precise than "specific routes", so I googled for it and found
that Linux supports it just fine; all you have to do is set
accept_ra_rt_info_max_plen to the maximum prefix length you want to
is very helpful.
Cheers and thanks,
On Sun, Dec 21, 2008 at 18:27, Arnaud Ebalard <arnaud.ebalard at eads.net> wrote:
> "Teran McKinney" <sega01 at gmail.com> writes:
>> I added the patch, but it does not seem to affect specific routes. I
>> was only using one router at first, but tried with an additional
>> router and had no luck. Specific routes just aren't been added :-(.
>> This configuration seems to work fine if manually added, so I'm not
>> sure what is wrong.
> If you compiled the kernel with the support and enabled the /proc
> entries to activate the feature, then it looks like a bug. Maybe you
> could drop a mail to the author of the patch.
> radvd-devel-l mailing list : radvd-devel-l at litech.org
More information about the radvd-devel-l