[radvd-devel-l] RFC: interfaces going up/down during radvd lifetime

Pekka Savola pekkas at netcore.fi
Tue Mar 7 04:55:00 EST 2006

On Tue, 7 Mar 2006, Sten Spans wrote:
>> Now, one could argue it'd be nice if this "worked by default", so that, for 
>> example:
>> a) if interface goes missing and comes back, automatically restart
>>    advertisements
>> b) if interface didn't exist when starting up, but IgnoreIfMissing is
>>    defined, automatically start advertising when the interface starts
>>    working.
>> c) don't print a lot of error messages on missing/non-working
>>    interfaces if IgnoreIfMissing is defined
>> I'd like to note that doing the processing checks could take a bit of CPU 
>> time, especially if you advertise (say) 20 times a second.
> It shouldn't be difficult to run the "check interfaces" routine
> only every few minutes.

Well, we're currently only using one timer handler: when the timer 
runs out, we fire off a router advertisement.  That would need to 
change.  I'm not sure whether additional changes would need to be made 
for UnicastOnly interfaces (e.g., ISATAP).

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

More information about the radvd-devel-l mailing list