Impossible case at mdb.c:2335

David W. Hankins David_Hankins at
Wed Sep 5 16:25:13 UTC 2007

this is clearly a bug - i've queued a ticket to fix it.

the binding state and the reserved flag are separate according to
the failover draft.  the servers are supposed to transform the binding
state to their own locally free state (free or backup) internally.

what's happened here is a mixup in assertions around the queueing of
leases...there's a separate queue for reserved-flagged leases.

On Wed, Sep 05, 2007 at 11:48:05AM -0400, gerd at wrote:
> I've been playing around with V3.0.1, specifically the 'reserved;' statement that goes into dhcpd.leases.  It seems that when I have a client acquire a lease and then stop the server to insert the 'reserved;' keyword into the dhcpd.leases file and then start the server, everything is happy.  If I then turn off that client (ie release the lease); connect a new client (new lease at a new IP address); stop the server; edit the dhcpd.leases file for the new client; and then try to start the server again ... I get this impossible case message seemingly because the lease for the original client is marked as 'free' AND 'reserved'.  I think that the logic is that a 'binding free' lease can't be a reserved one?  If that's the case, then it would seem that you have to 'trick' the leases file each time you update it into thinking that all of the reserved hosts have active leases--either that or i'm doing something wrong here?

Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
Why settle for the lesser evil?
David W. Hankins	"If you don't do it right the first time,
Software Engineer		     you'll just have to do it again."
Internet Systems Consortium, Inc.		-- Jack T. Hankins

More information about the dhcp-users mailing list