<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>On Aug 8, 2013, at 9:21 AM, Sten Carlsen <<a href="mailto:stenc@s-carlsen.dk">stenc@s-carlsen.dk</a>> wrote:</div><div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
<div bgcolor="#FFFFCC" text="#000000">
It seems to me that the man-page is not quite in agreement with
this:<br>
~~~~<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
The <b>host</b> declarations will only match a client if one of
their <i>fixed-address</i> statements is viable on the subnet (or
shared network) where the
client is attached. <u>Conversely, for a </u><u><b>host</b></u><u>
declaration to match a client being allocated a dynamic address,
it must <b>not</b> have any </u><u><i>fixed-address</i></u><u>
statements. </u><br>
~~~~<br>
This text says "not have any fixed-address statements", it does not
say any fixed addresses in this subnet.<br>
<br>
I also find the following a bit confusing:<br>
~~~~<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
The <i>fixed-address</i> declaration is used to assign one or more
fixed IP addresses to a client. It should only appear in a <i>host</i>
declaration. If
more than one address is supplied, then when the client boots, it
will be assigned the address that corresponds to the network on
which it is booting.<u> If none
of the addresses in the </u><u><i>fixed-address</i></u><u>
statement are valid for the network to which the client is
connected, that client will not match the </u><u><i>host</i></u><u>
declaration containing that </u><u><i>fixed-address</i></u><u>
declaration. </u>Each <i>address</i> in the <i>fixed-address</i>
declaration should be either an IP address or a
domain name that resolves to one or more IP addresses.
<br>
~~~~<br>
What does it mean "will not match"? Does that mean that the client
is then an "unknown client"?<br></div></blockquote></div><br><div>These are both good questions.</div><div><br></div><div>In my experience, one should never assume that the DHCP man pages are 100% accurate. They are not.</div><div><br></div><div>Regards,</div><div>Chris Buxton</div></body></html>