<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFCC" text="#000000">
<br>
<div class="moz-cite-prefix">On 14/02/14 16.25, Simon Hobson wrote:<br>
</div>
<blockquote
cite="mid:1945C078-352F-4B83-8C62-9DDDBA49CCDD@thehobsons.co.uk"
type="cite">
<pre wrap="">Sten Carlsen <a class="moz-txt-link-rfc2396E" href="mailto:stenc@s-carlsen.dk"><stenc@s-carlsen.dk></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">They are, to my knowledge and experience, independent.
I.e. you make the allow/deny setup for each, both as described.
</pre>
</blockquote>
<pre wrap="">
I think the question was more ...
If the class allow/deny statements mean that a client should be denied and the host (known host) allow/deny statements mean that it should be allowed (or vice versa), which one takes effect ? One says allow, the other says deny, one has to lose.</pre>
</blockquote>
My assumption is: first test host statements, then try classes. Use
the first allowed possibility, i.e. if the host is allowed, the
class is not tested. If the host is denied, try the class and allow
if the class is allowed.<br>
<br>
I am in no way certain about this but it would be logical since host
statements generally have higher priority.<br>
<br>
Does anyone know for sure?<br>
<blockquote
cite="mid:1945C078-352F-4B83-8C62-9DDDBA49CCDD@thehobsons.co.uk"
type="cite">
<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>