Dynamic and static leases present

[Todd Snyder]

I've played and realized that my "belief" was based on past experience
with MS dhcp.

I've rejiggered my ranges and have things working, hopefully the users
are happy.

Thanks much for helping set my brain straight.

Cheers,

Todd. 

-----Original Message-----
From: dhcp-users-bounce at isc.org [mailto:dhcp-users-bounce at isc.org] On
Behalf Of Brian Raaen
Sent: Thursday, May 15, 2008 3:33 PM
To: dhcp-users at isc.org
Subject: Re: Dynamic and static leases present

Dear Todd,
	My understanding is even if you have a static assignment you
will need for that address to not be included in the "range" or other
dynamic clients will get the address.  I have duplicated and confirmed
this behavior.  ISC dhcpd will do this unlike Microsoft Windows dhcp
that has the concept of 'reservations'.  Our company tends to reserve
the top or bottom part of a subnet to not be in a range when we want to
assign static addresses.  Just make sure that the ip in question is not
in the range and you will not have this problem.  One way to think of
things is that a range in a "pool" of addresses that the server can
assign to anyone, setting the host entry basically tells the server that
if I can not have that address I will not have one at all.  If the
address has already been taken it will just sit there and not accept any
other offer.


--
Brian Raaen
Network Engineer
braaen at zcorum.com


On Thursday 15 May 2008, Todd Snyder wrote:
> I have my subnets defined as discussed the other day:
> 
> subnet 172.25.106.0 netmask 255.255.255.0 { range 172.25.106.16
> 172.25.106.254; option routers 172.25.106.1; }
> 
> And I have a host entry for the middle of the range:
> 
> host ns03 {    
> 	hardware ethernet 00:1a:64:8a:62:42;    
> 	option host-name "ns03";    
> 	fixed-address 172.25.106.22; 
> } 
> 
> But when the device tries to get an ip, I get the following in my
logs:
> 
> May 15 18:49:02 sa-bmp01 dhcpd: Dynamic and static leases present for
> 172.25.106.22. 
> May 15 18:49:02 sa-bmp01 dhcpd: Remove host declaration ns03 or remove
> 172.25.106.22 
> May 15 18:49:02 sa-bmp01 dhcpd: from the dynamic address pool for
> 172.25.106/24 
> 
> 
> One page I read suggests that I can't have a static assignment in the
> middle of a dynamic range, but I don't believe that to be correct.
> 
> My understanding is that I can assign a static ip within a dynamic
> range, and it's basically 'reserved' until that mac address asks for
an
> IP, which it is then given from it's host declaration.
> 
> Can anyone identify the error, or clarify whats going on here?  My
brain
> isn't working with me on this one ....
> 
> Thanks,
> 
> Todd.
> 
> 
> ...................................
> Todd Snyder
> Tools Analyst
> Blackberry Operations
> Research In Motion Ltd.
> 519-888-7465 x73176
> tsnyder at rim.com 
> ...................................
> 
> ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential

information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute
non-public 
information. Any use of this information by anyone other than the
intended 
recipient is prohibited. If you have received this transmission in
error, 
please immediately reply to the sender and delete this information from
your 
system. Use, dissemination, distribution, or reproduction of this 
transmission by unintended recipients is not authorized and may be
unlawful.
> 
> 

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.