Retaining information between DHCP requests

Simon Hobson dhcp1 at
Thu Oct 9 17:35:39 UTC 2014

CLOSE Dave <Dave.Close at> wrote:

>> One thought is to use a separate pool for Kickstart. Use a class to
>> have Kickstart use this pool and the booted machine to use the main
>> pool. You can then apply options to the pools. If you *must* have
>> fixed addresses, then would reserved addresses do ? Create a "stub"
>> lease and add the "reserved" statement to it. That lease will then
>> only be used for the specific client. Without the reserved statement,
>> the addresses will still be effectively static if your set of
>> machines is smaller than the pool size - because the server will try
>> and issue the same address to each client even if it was long
>> expired.
> Basically, that's what I was trying to do using vendor-class-identifer, 
> use a separate set of instructions for kickstart. I wasn't trying a 
> different pool but that might be possible. Can you please enlighten me 
> on how I can accomplish that?

I had a cunning scheme in mind, but then while writing it down I realised it won't work. Put another way, your client is broken and you'll need to fix it - I can't see any other way to meet your needs.

More information about the dhcp-users mailing list