[radvd-devel-l] radvd stuck on linux 2.6.31+

steve at snewbury.org.uk steve at snewbury.org.uk
Mon Sep 28 10:36:27 EDT 2009

The low broadcast frequency on 2.6.29 is explianed by the lack of a specified interval, I left it running for quite a while on 2.6.31, but the only broadcasts were from startup and shutdown of radvd.

Just to make clear, solicted unicast is working fine on either kernel.

I'll try using HUP after the tunnel device comes up, I suspect it will work. 

Sorry about not replying in-line, this mail agent is pretty limited. :(
-original message-
Subject: Re: [radvd-devel-l] radvd stuck on linux 2.6.31+
From: Pekka Savola <pekkas at netcore.fi>
Date: 28/09/2009 14:33

On Mon, 28 Sep 2009, Steven J Newbury wrote:
> Okay, I'm not getting any unsolicited RA broadcasts with the new kernel.
> Also, devices configured IgnoreIfMissing are still ignored even after
> they come up and have a valid link-local address unless radvd is
> restarted. (Tested the latter with my OpenVPN tunnel.)

I note that you don't have {Min,Max}RtrAdvInterval configured.  It will take at least this long (the default value) for radvd to detect 
the link has come back up, and possibly the next cycle before it's 
done reactivating the interface.  Make sure that this is not skewing 
your test results.

Could you run a debug output with only one interface configured and 
above in mind?

By restarting radvd, do you mean a complete restart or sending HUP 
signal?  The latter should be enough but the code paths are different.

Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

radvd-devel-l mailing list  :  radvd-devel-l at litech.org

More information about the radvd-devel-l mailing list