My two guesses are:
1) It might have something to do with the request coming after the T1
time (half the lease time), and it wasn't renewed then,

2) or (more likely) the server doesn't look for an existing lease
unless the client asks for an address (REQUEST) that's different from
the one OFFERed.

Some tcpdumping in both situations could probably shed some light on it.

_Matt

On 2/1/06, Steven M. Bellovin <smb@cs.columbia.edu> wrote:
> I'm not sure if this should actually be on a dhcp mailing list,
> but since I'm using NetBSD I'll ask here first.
>
> The dhcp server is running an old -current snapshot, mostly because
> there's no reason to update it -- it's a Soekris serving as a
> bridge.  It has dhcpd 3.0.3.  My laptop is running a very recent -current=