<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p>Hi Glen,</p>
<p>I dig into man dhcpd.conf but missed that, sorry about that.<br />Undestood the explanation and thank you for that, will stick to the default.</p>
<p>Jorge,</p>
<p id="reply-intro">On 2022-08-21 14:00, glenn.satchell@uniq.com.au wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"><span style="white-space: nowrap;">Hi Jorge</span><br /><br /><span style="white-space: nowrap;">This is from the dhcpd.conf man page:</span><br /><br /><span style="white-space: nowrap;"> The one-lease-per-client statement</span><br /><br /><span style="white-space: nowrap;"> one-lease-per-client flag;</span><br /><br /> If this flag is enabled, whenever a client sends a DHCPREQUEST for<br /> a particular lease, the server will automatically free any other<br /> leases the client holds. This presumes that when the client sends<br /> a DHCPREQUEST, it has forgotten any lease not mentioned in the<br /> DHCPREQUEST - i.e., the client has only a single network interface<br /> and it does not remember leases it's holding on networks to which<br /> it is not currently attached. Neither of these assumptions are<br /> guaranteed or provable, so we urge caution in the use of this<br /><span style="white-space: nowrap;"> statement.</span><br /><br /><span style="white-space: nowrap;">So you could use:</span><br /><br /><span style="white-space: nowrap;">one-lease-per-client true;</span><br /><br />This is not always what you might want though. dhcpd follows the RFC precisely, and this means that if you connect to a particular subnet it should try to give you the same IP address as you had last time. Setting one-lease-per-client means it will forget the leases on other subnets. This is why it's a settable parameter - the default is the "safer" option.<br /><br />The man pages for dhcpd.conf, dhcpd, dhcpd.leases, dhcp-eval are worth looking at if you haven't<br /><br /><span style="white-space: nowrap;">regards,</span><br />Glenn<br /><br /><span style="white-space: nowrap;">On 2022-08-21 20:03, Jorge Bastos wrote:</span>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"><span style="white-space: nowrap;">Howdy,</span><br /><br /><span style="white-space: nowrap;">I've started using DHCPD, and noticed that the lease file is not</span><br /><span style="white-space: nowrap;">"cleaned",</span><br /><span style="white-space: nowrap;">What I mean is, if some cliente request IP, and get .....11, and after</span><br /><span style="white-space: nowrap;">two days/another time request again after the lease time ends, and the</span><br /><span style="white-space: nowrap;">......11 is already in someone else, it will get a new IP, so far so</span><br /><span style="white-space: nowrap;">good.</span><br /><span style="white-space: nowrap;">But the lease file stays with the information about the old lease,</span><br /><span style="white-space: nowrap;">aswell the new one.</span><br /><br /><span style="white-space: nowrap;">No way to make it have only the new lease for that MACADDRR? for</span><br /><span style="white-space: nowrap;">example like it does the MSWindows DHCPD.</span><br /><span style="white-space: nowrap;">I've been searching docs and did not found any information about it,</span><br /><span style="white-space: nowrap;">but did found people exposing extra large dhcpd.leases file (+1GB),</span><br /><span style="white-space: nowrap;">aswell others saying that their dhcpd.leases file dont have more than</span><br /><span style="white-space: nowrap;">50 or 100kb</span><br /><br /><span style="white-space: nowrap;">Thanks in advanced,</span></blockquote>
</div>
</blockquote>
<p><br /></p>
</body></html>