dhcp.leases overrides config-files?

[Peter Veerman]

Hi,

Last week I posted a rather complicated question regarding the "Billing 
subclass that does override configured allow/deny member subclasses". 
The question is rather complex, still open and unanswered and maybe 
that's why it's a good time for some summarization and clarification.

We have found out that as soon as a device is bound to a certain 
subclass, the " billing subclass" is set in the dhcp.leases file.
- Moving the customer to another subclass by changing the configfiles 
and restarting the server does not move this customer. S
- Stopping the server, removing the "billing subclass" line from the 
dhcp.leases file after which starting the server again does result in 
the expected move of the device to the configured subclass.

Is the behaviour just described correct?

We have the following config:

=============

class "knowncustomers"  {
   match option agent.remote-id;
   lease limit 1;
   }

subclass "knowncustomers" xx:xx:xx:xx:xx:xa
subclass "knowncustomers" xx:xx:xx:xx:xx:xb
subclass "knowncustomers" xx:xx:xx:xx:xx:xc
subclass "knowncustomers" xx:xx:xx:xx:xx:xd
etc.

subclass "unknowncustomers" xx:xx:xx:xx:xx:x1
subclass "unknowncustomers" xx:xx:xx:xx:xx:x2
subclass "unknowncustomers" xx:xx:xx:xx:xx:x3
subclass "unknowncustomers" xx:xx:xx:xx:xx:x4
etc.

pool{
   # known customer pool
   allow members of "knowncustomers"
   ....
   }

pool{
   # Unknown customer pool
   deny members of "unknowncustomers"
   ....
   }

=============

Kind regards,

Peter Veerman