<html><head> <style type="text/css" title="rt_noDelete">
blockquote.rt {
margin: 0 0 15px;
border-left: 4px solid #81c784;
padding: 0 0 0 12px;
display: block;
}
p { margin: 0 0 0 0 }
.email-signature {font-family:"Arial"; font-size: 8pt; font-style: italic; font-weight: normal; text-decoration: none; }
</style></head><body><p>I have a subnet in dhcpd - lets just assume 192.168.1.0/24</p>
<p>(It's a fail-over served pool - if that matters.)</p>
<p><br/></p>
<p>I have a pool where unknown-clients are allowed</p>
<p>192.168.1.21-40</p>
<p><br/></p>
<p>I'd like to add a new lease for a machine where the IP is outside the unknown pool above. (I don't want to use a host definition with an IP in the conf files, because I want the ddns name to get added via the DDNS mechanisms - which doesn't happen in that case. Plus, if this machine/device gets moved to another subnet, and the host def is still there, it won't get ANY lease in the new subnet - which is bad. I'd like the device to still function if it gets dropped into a new subnet, even if it's not getting a "special" ip any more.)</p>
<p><br/></p>
<p>This new machine/device may have already been added to the network and currently has an address in the 192.168.21-40 pool.</p>
<p><br/></p>
<p>Lets assume I'd like to assign it 192.168.1.51 - and set a reservation. </p>
<p>Lets assume that I'll have several machines I'd like set as "static" between 51-70. </p>
<p>But I don't want just "any" machine to get one of these "special" addresses in the 51-70 range.</p>
<p><br/></p>
<p>What's the best way to go about this?</p>
<p><br/></p>
<p>---</p>
<p>Some thoughts I've had, but this gets complicated.</p>
<p><br/></p>
<p>---</p>
<p>I don't believe I can just add or modify the lease without changing the pool, because even if there's a defined lease, this is still an unknown client. So, even if there's a reserved lease for 192.168.1.51 - the DHCP server won't give out that address because this is an unknown client. (Right?)</p>
<p><br/></p>
<p>Yet if I make a pool for 51-70 and allow unknown clients, then any client might (will) get one - not just the ones I want to "move" there.</p>
<p><br/></p>
<p>I've thought about pre-creating leases for 51-70 and essentially adding "bogus" information for those leases and reserving them. (While allowing unknown-clients for the 51-70 pool - but since they're all "taken" it won't hand one out), Then when I want to move something there, I can remove the "bogus" reservation and move the "real" lease to the appropriate IP in the 51-70 block/pool.</p>
<p><br/></p>
<p>---</p>
<p>Or define the MAC address in a host definition, without an IP definition. (I think DDNS works in this case.)</p>
<p>Then define the 192.168.51-70 pool as "known" hosts only. (And make sure no "other" known hosts accidentally grab one of the IP's in this pool. This part worries me.)</p>
<p><br/></p>
<p>But it seems like I must be making this too hard.</p>
<p>Am I missing something?</p>
<p><br/></p>
<p>Surely someone else has done this and can point me a tried-and-true solution that works without a ton of drama. :)</p>
<p><br/></p>
<p>(Yes, my pools are larger than those, but the details are essentially the same - this example is just more manageable.)</p>
<p><br/></p>
<p>Thanks!</p>
<p>-Greg</p><p> </p><p>
</p></body>