agent.circuit-id as dhcp-client-identifier

[Simon Hobson]

David W. Hankins wrote:

>  > > version 3.1 has I believe the ability to set the identifier selection
>>  > code. The default is match first value ( client-id, hardware) the
>>  > same as version 3.0.x, but you could change this to match first value
>>  > ( agent.circuit-id, client-id, hardware) in version 3.1 to achieve
>>  > what you want.
>
>Actually, this feature did not make the final cut for 3.1.

Well I guess the OP will have to start hacking then !

I would be tempted to suggest a quick and dirty hack would be to 
stuff the agent.circuit-id option value into the client-id at some 
point early on in the packet processing. This would then use the 
existing code to tie the lease to the client-id and avoid having to 
hack 'the innards' of the server - though of course it will result in 
what is technically broken behaviour.