On Son, 2008-12-14 at 22:15 +0100, Juliusz Chroboczek wrote:
> > Of course you need that a clock - especially the one of a server - is
> > synchronized to itself (and that included reboots of the host). Well, if
> > one drops that requirement, I fear it gets quite ugly in the field.
>
> The client-side algorithm is reasonably simple -- you just use relative
> timestamps, and renew all leases at reboot and also whenever you suspect
> that your clock was stepped. The server-side stuff is somewhat more
> challenging.
ACK, that's the "real thing".
The simple solution is to have some "epoch" marker (e.g. a random
generated number at boot time with enough bits to define duplicated ones
as improbable enough) and force an immediate renew of all leases.
But for 10^6 (and more) nodes in large networks (which is nothing
special for DOCSIS networks today) it really ugly and inelegant ....
Bernd
--
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and Services
_______________________________________________
Babel-users mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/babel-users
