In our case we are using routable (not private space) ips on our dhcp server. Until we re-vamp a few things we are limited by the routable ip space we were assigned. Are you aware of a way to put an ip back into the pool if you know the client has been turned off or otherwise is not using the ip? Or do you just have to wait until the lease expires? This gets me back to setting a shorter lease time to possibly put an ip back into the pool quicker? Also, is the dhcpd.leases file the actually database that the deamon consults when giving out ips? If so, could you possibly remove an ip stanza that you know is no longer being used but the lease has not yet expired effectively putting it back in the pool? I know this is not something you would want to do all the time, but if it is possible it would help when you really need an ip.
Thanks
Main Topics
Browse All Topics





by: jleviePosted on 2005-12-20 at 18:05:28ID: 15523602
If a client fails to renew its lease before expiration for any reason the DHCP server will return that IP to the free pool. Clients can release an IP at any time, though that is usually associated with negotiationg for a different one.
Who/what is imposing the limit on the pool and is the pool larger than the max client population?
For just about all cases now one will be using IP's from one of the RFC 1918 private networks for local clients. Accordingly there should be no reason to have a pool that's too small. However, windows clients aren't the best behaved network citizens and I've seen them take a different IP, rather that asking for or accepting the previous, sometimes when they reboot. Since one might reboot a windows box a number of times in a day that can eat up a DHCP pool that should be big enough (more IP's than possible clients).