Two active leases for client bug?

[Darko Bezjak]

Thanks very much Simon! I have solved problem with your configuration and
now I have in log file:

Mar 24 13:30:02 dhcpprimary dhcpd: DENY-RAS-SERVER 
Mar 24 13:30:02 dhcpprimary dhcpd: class=PUBLIC 
Mar 24 13:30:02 dhcpprimary dhcpd: DHCPDISCOVER from 00:0d:60:fe:6d:af via
10.106.0.1: booting disallowed

I have just one question. Way dhcp server kips all clients leases in lease
file although when is lease inactive. Client has been move from one class to
other class but lease for client has stay in lease file forever!?

lease 10.108.253.241 {
  starts 1 2005/11/28 14:17:23;
  ends 2 2005/11/29 10:37:50;
  tstp 2 2005/11/29 10:37:50;
  binding state free;
  hardware ethernet 00:12:f4:00:05:c1;
  uid "\001\000\022\364\000\005\301";
}
lease 10.102.248.230 {
  starts 3 2005/11/23 11:36:15;
  ends 4 2005/11/24 11:36:15;
  tstp 4 2005/11/24 11:36:15;
  binding state free;
  hardware ethernet 00:12:f4:00:05:c1;
  uid "\001\000\022\364\000\005\301";
}
lease 10.104.255.234 {
  starts 5 2006/03/24 03:01:53;
  ends 6 2006/03/25 03:01:53;
  tstp 6 2006/03/25 03:01:53;
  binding state active;
  next binding state free;
  hardware ethernet 00:12:f4:00:05:c1;
  uid "\001\000\022\364\000\005\301";
  option agent.circuit-id "GigabitEthernet 12/0.10661009:1009"; }

Kind regards, Darko.

-----Original Message-----
From: dhcp-users-bounce at isc.org [mailto:dhcp-users-bounce at isc.org] On Behalf
Of Simon Hobson
Sent: Friday, March 24, 2006 9:40 AM
To: dhcp-users at isc.org
Subject: Re: Two active leases for client bug?

Darko Bezjak wrote:

>I have problem with one clients which has receive two ip address at the
same
>time. How is possible to get client two ip address and have two active 
>records in lease file.

Because the client asked for two addresses using two different client IDs.
Because the client ids are different, the requests are from different
clients as far as the server is concerned - the client ID is the PRIMARY
database key, with the MAC address used instead if no client ID is supplied.


>lease 84.255.245.135 {

>   uid "\001RAS \000\021/H\261\261\000\000\000\000\000\000";



>lease 84.255.197.54 {

>   uid "\001\000\300I\265\011\314";


If you dig back through the archives, you'll see that this is an old issue -
Microsoft systems leasing addresses for their RAS service just in case a
client should ever actually connect to it (they normally ask to 10 (yes TEN)
addresses for RAS).

You can fix it either by turning off RAS on systems which don't need it, or
by putting something like this in the dhcpd.conf :

if { substring (client-id,1,4)="RAS "
   ignore booting ;
}

You'll have to check the exact syntax with the man pages as I'm going from
memory here.

--