[radvd-devel-l] RFC: interfaces going up/down during radvd
lutchann at litech.org
Wed Mar 15 12:34:52 EST 2006
-----BEGIN PGP SIGNED MESSAGE-----
On Wed, 15 Mar 2006, Pekka Savola 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
This sounds like the most natural way for radvd to work. We shouldn't
need to send HUP to radvd if it can determine automatically when
interfaces appear and disappear.
> > 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.
If you set radvd to advertise 20 times a second you're already expecting
it to take a bit of overhead. If you'd rather not check for interface
changes that often, though, you can put another time compare in the timer
routine to run the interface checks no more than once a second, say.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the radvd-devel-l