<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFCC" text="#000000">
How is your configuration? do you specifically use the MAC or is it
the default (which is UID)?<br>
<br>
<div class="moz-cite-prefix">On 08/01/13 20:13, Neff, Glen wrote:<br>
</div>
<blockquote
cite="mid:F061F650C47E134C86F9605C5F44EE5F174AA481FE@MX23A.corp.emc.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="GENERATOR" content="MSHTML 9.00.8112.16457">
<div style="FONT-FAMILY: Tahoma; DIRECTION: ltr; COLOR: #000000;
FONT-SIZE: x-small">
<div>>The main piece of information to identify a client is
actually the UID, so with a new UID -> a new client,
obviously it >can not get the same IP, that is reserved for
the old client.<br>
>You may have luck looking into classes and subclasses.
Possibly with "spawn". I have never used these features
>but I have a feeling they may actually do what you need.<br>
>Use the hardware = MAC to create your subclass and that
could be independant from the UID - I think.<br>
</div>
<div><font face="tahoma">Is dhcpd.conf(5) erroneous then?:</font></div>
<div> </div>
<div><font face="tahoma"> The duplicates keyword</font></div>
<div><font face="tahoma"> allow duplicates;<br>
deny duplicates;</font></div>
<div><font face="tahoma"> Host declarations can match
client messages based on the DHCP Client<br>
Identifier option or based on the client's network
hardware type and<br>
MAC address. If the MAC address is used, the host
declaration will<br>
match any client with that MAC address - even
clients with different<br>
client identifiers. This doesn't normally happen,
but is possible<br>
when one computer has more than one operating system
installed on it -<br>
for example, Microsoft Windows and NetBSD or Linux.</font></div>
<div><font face="tahoma"> The duplicates flag tells the
DHCP server that if a request is received<br>
from a client that matches the MAC address of a
host declaration, any<br>
other leases matching that MAC address should be
discarded by the<br>
server, even if the UID is not the same. This is
a violation of the<br>
DHCP protocol, but can prevent clients whose client
identifiers change<br>
regularly from holding many leases at the same
time. By default,<br>
duplicates are allowed.<br>
</font></div>
<div>
<div class="BodyFragment"><font size="2">
<div class="PlainText">-G<br>
<br>
/*<br>
* Glen R. J. Neff<br>
* USD Lab Operations Infrastructure Team<br>
* <a class="moz-txt-link-abbreviated" href="mailto:glen.neff@emc.com">glen.neff@emc.com</a><br>
*<br>
* EMC^2 == E^2<br>
*/</div>
</font></div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
dhcp-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a>
<a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/dhcp-users">https://lists.isc.org/mailman/listinfo/dhcp-users</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Best regards
Sten Carlsen
No improvements come from shouting:
"MALE BOVINE MANURE!!!"
</pre>
</body>
</html>