already leased ip seems to be leased to another client

[Glenn Satchell]

Hi Katsu,

I think this is a bug that was fixed in a later version. I remember
some discussion a few months back about a bug where the client was
handed a lease with a given duration, but the server actually stored a
shorter lease time.

It is very fortunate for you that your old version has worked so well
for such a long time, but now it is time to upgrade :) Current release
is 3.0.3 which is a long way from 3.0.1rc4. 3.0.4b3 is also out, so you
may like to try that or wait for 3.0.4.

regards,
-glenn

>Date: Wed, 29 Mar 2006 18:38:49 +0900
>From: Katsu Yamamoto <yamamoto.mrn at pfu.fujitsu.com>
>
>Hi,
>
>Our dhcp server appears to be acting strange lately.
>
>Here is what's been happening:
>
>IP 219.104.251.76 is leased to client-A with lease time of 14400 secs.
>then...while client-A is using the address 219.104.251.76, the very same
>IP address is leased to different client. So unfotunate client-A has to
>request another available IP all over again.
>
>following is the excerpt of daemonlog:
>
>Mar 28 10:40:40 ****** dhcpd: DHCPDISCOVER from 00:0d:0b:e4:41:25 via 
219.104.227.129
>Mar 28 10:40:41 ****** dhcpd: DHCPOFFER on 219.104.251.76 to 00:0d:0b:e4:41:25 
via 219.104.227.129
>Mar 28 10:40:41 ****** dhcpd: DHCPREQUEST for 219.104.251.76 (211.125.60.112) 
from 00:0d:0b:e4:41:25 via 219.104.227.129
>Mar 28 10:40:41 ****** dhcpd: DHCPACK on 219.104.251.76 to 00:0d:0b:e4:41:25 
via 219.104.227.129
>  :
>(snip)
>  :
>Mar 28 11:28:22 ****** dhcpd: DHCPDISCOVER from 00:90:fe:58:04:23 via 
219.104.227.129
>Mar 28 11:28:23 ****** dhcpd: DHCPOFFER on 219.104.251.76 to 00:90:fe:58:04:23 
(PCG-F70 Series) via 219.104.227.129
>Mar 28 11:28:26 ****** dhcpd: DHCPDISCOVER from 00:90:fe:58:04:23 (PCG-F70 
Series) via 219.104.227.129
>Mar 28 11:28:26 ****** dhcpd: DHCPOFFER on 219.104.251.76 to 00:90:fe:58:04:23 
(PCG-F70 Series) via 219.104.227.129
>Mar 28 11:28:26 ****** dhcpd: DHCPREQUEST for 219.104.251.76 (211.125.60.112) 
from 00:90:fe:58:04:23 (PCG-F70 Series) via 219.104.227.129
>Mar 28 11:28:26 ****** dhcpd: DHCPACK on 219.104.251.76 to 00:90:fe:58:04:23 
(PCG-F70 Series) via 219.104.227.129
>  :
>(snip)
>  :
>Mar 28 12:40:33 ****** dhcpd: DHCPREQUEST for 219.104.251.76 from 
00:0d:0b:e4:41:25 via hme0: lease 219.104.251.76 unavailable.
>Mar 28 12:40:33 ****** dhcpd: DHCPNAK on 219.104.251.76 to 00:0d:0b:e4:41:25 
via hme0
>Mar 28 12:40:38 ****** dhcpd: DHCPREQUEST for 219.104.251.76 from 
00:0d:0b:e4:41:25 via hme0: lease 219.104.251.76 unavailable.
>Mar 28 12:40:38 ****** dhcpd: DHCPNAK on 219.104.251.76 to 00:0d:0b:e4:41:25 
via hme0
>Mar 28 14:10:30 ****** dhcpd: DHCPREQUEST for 219.104.251.76 from 
00:0d:0b:e4:41:25 via 219.104.227.129: lease 219.104.251.76 unavailable.
>Mar 28 14:10:30 ****** dhcpd: DHCPNAK on 219.104.251.76 to 00:0d:0b:e4:41:25 
via 219.104.227.129
>Mar 28 14:10:35 ****** dhcpd: DHCPREQUEST for 219.104.251.76 from 
00:0d:0b:e4:41:25 via 219.104.227.129: lease 219.104.251.76 unavailable.
>Mar 28 14:10:35 ****** dhcpd: DHCPNAK on 219.104.251.76 to 00:0d:0b:e4:41:25 
via 219.104.227.129
>Mar 28 14:10:40 ****** dhcpd: DHCPDISCOVER from 00:0d:0b:e4:41:25 via 
219.104.227.129
>Mar 28 14:10:45 ****** dhcpd: DHCPDISCOVER from 00:0d:0b:e4:41:25 via 
219.104.227.129
>Mar 28 14:10:46 ****** dhcpd: DHCPOFFER on 219.104.251.235 to 00:0d:0b:e4:41:25 
via 219.104.227.129
>Mar 28 14:10:46 ****** dhcpd: DHCPREQUEST for 219.104.251.235 (211.125.60.112) 
from 00:0d:0b:e4:41:25 via 219.104.227.129
>Mar 28 14:10:46 ****** dhcpd: DHCPACK on 219.104.251.235 to 00:0d:0b:e4:41:25 
via 219.104.227.129
>
>We're told that client A(00:0d:0b:e4:41:25) has been powered-on all the time.
>By the way, we are using dhcpd3.0.1rc4. I know it is an old version. But it has 
been
>in service since 2002 and has been working perfectly well since then.
>
>One more thing, this IP range has total of 253 ips, but 246 ips have been 
already
>leased to clients. So only 7 ips are supposedly free...
>
>Thanks in advance.
>
>Katsu Yamamoto
>