<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFCC" text="#000000">
They are, to my knowledge and experience, independent.<br>
<br>
I.e. you make the allow/deny setup for each, both as described.<br>
<br>
<br>
<div class="moz-cite-prefix">On 14/02/14 14.33, Ole Holm Nielsen
wrote:<br>
</div>
<blockquote cite="mid:52FE1B29.4000004@fysik.dtu.dk" type="cite">Glenn
Satchell glenn.satchell at uniq.com.au wrote:
<br>
<blockquote type="cite">known hosts is a list that matches all
hosts defined in host statements,
<br>
doesn't matter if they have a fixed-address or not.
<br>
<br>
These hosts can also be a member of a class if they pass the
match
<br>
requirement defined in the class.
<br>
<br>
known or unknown hosts are completely independent of class
membership.
<br>
</blockquote>
<br>
Yes, that's exactly the point: We have two types of client
definitions: 1) hosts and 2) classes. The big question is: How do
allow/deny statements work when used simultaneously with clients
of types 1) and/or 2)?
<br>
<br>
Chris has clarified
(<a class="moz-txt-link-freetext" href="https://lists.isc.org/pipermail/dhcp-users/2014-February/017625.html">https://lists.isc.org/pipermail/dhcp-users/2014-February/017625.html</a>)
the case of 2) only.
<br>
<br>
Thanks,
<br>
Ole
<br>
<br>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Best regards
Sten Carlsen
No improvements come from shouting:
"MALE BOVINE MANURE!!!"
</pre>
</body>
</html>