ISC DHCPD giving out reserved IPs for non-reserved hosts

Glenn Satchell Glenn.Satchell at uniq.com.au
Mon Jul 9 14:20:31 UTC 2007


Yes. That's the best way to do it. Apologies for the previous duplication.

There's a script in the source distibution in the contrib section
called ms2isc for converting MS configs to ISC. Might be worth trying,
just to see what it thinks needs to be there.

regards,
-glenn

>Date: Mon, 09 Jul 2007 10:11:08 -0400
>From: Scott Lacy <LACY_S at Mercer.edu>
>
>That was going to be my next question, Glenn, if I could carve out 
>exceptions in the dhcp pool.  I'll do that for what we've already 
>allocated and just make sure in the future that reservations come from 
>one end of the dhcp pool and carve those out.
>
>
>Thanks!
>
>
>Scott
>
>Glenn Satchell wrote:
>>> From: "Brent L. Bates" <blbates at vigyan.com>
>>> Date: Mon, 9 Jul 2007 09:54:40 -0400
>>>
>>>     Since when does Micro$loth do anything in the `standard' way.  I believe
>>> their DHCP server `reserves' IP addresses.  ISC's DHCPD server versions less
>>> than 3.1 create `fixed addresses'.  I know it is a subtle difference, but it
>>> is a difference.  Check the list archives for details.  I haven't used the 
new
>>> version of ISC's DHCPD server yet, so I don't remember the details on if the
>>> IP address ranges are set up differently for fixed addresses and reserved
>>> ones.  Someone else on the list will know better.
>>>     
>>
>> With MS dhcp server you say 'use these addresses, except for these few
>> I specify'.
>>
>> With ISD dhcpd you say 'use this range of addresses'.
>>
>> So, if you have some fixed addresses supplied using host statements then you 
>> need to make sure these addresses are not part of the dynamic range. It means 
>> you can end up with things like:
>>
>> subnet ... {
>>   range 1.2.3.4 1.2.3.20;
>>   range 1.2.3.22 1.2.3.100;
>>   ...
>> }
>> host ... {
>>   fixed-address 1.2.3.21;
>>   ...
>> }
>>
>> regards,
>> -glenn
>>
>>   
>
>


More information about the dhcp-users mailing list