<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p><span style="font-size: 10pt;"><span style="font-family: Calibri, Helvetica, sans-serif, EmojiFont, "Apple Color Emoji", "Segoe UI Emoji", NotoColorEmoji, "Segoe UI Symbol", "Android Emoji", EmojiSymbols; font-size: 13.3333px;">Francis Dupont</span> writes:</span><br>
</p>
<div style="color: rgb(0, 0, 0);"><font size="2"><span style="font-size:10pt;">
<div class="PlainText">> I think you miss the fact client-classes are used to do subnet<br>
> selection and not the opposite so when you specify a client-class in<br>
> a subnet this means this particular subnet can be selected only by<br>
> members of this class. Note that it means classification is done<br>
> before subnet selection.</div>
<div class="PlainText"><br>
</div>
<div class="PlainText">Yes, I have several client-classes defined (let's say Class A, Class B, Class C, etc.) and I'm going to have multiple subnets defined (Subnet 1, Subnet 2, etc). The vast majority of my clients probably won't be classified at all so let's
say they'll get Subnet 2. Subnet 1 is the special and I'd like Classes A, B, and C to all get IP addresses from Subnet 1. I figure I could condense all of them down to one client class and have a really large test statement with a number of "or" operators
but it seemed kind of messy to do it that way and breaking them out into different classes allows more options in the future if I need to assign special values of any kind.</div>
<div class="PlainText"><br>
</div>
<div class="PlainText">I should note that, in reality, every building I'm working with will have two subnets one of which will be the special one for these classified clients and the other for everything that isn't classified. Each subnet has a relay specified
which seems to further restrict what traffic can pull from each subnet.<br>
<br>
> in theory yes but I am afraid the corresponding classification<br>
> expression can be a bit hard to write.</div>
<div class="PlainText"><br>
</div>
<div class="PlainText">I was assuming it would be something like "test": "option[55].hex = '1,3,7,43'"</div>
<div class="PlainText"><br>
</div>
<div class="PlainText">This loads correctly on service start but I don't think I've gotten it to successfully match to a client yet. I'm guessing that is not the correct format but it is a little difficult to see what it as I'm just looking at a Wireshark
capture.<br>
<br>
> yes, valid-lifetime, renew-timer and rebind-timer are supported<br>
> parameters in DHCPv4 subnets.<br>
<br>
</div>
<div class="PlainText">Terrific, I'll start adding this to my config.</div>
<div class="PlainText"><br>
</div>
<div class="PlainText">Thanks,<br>
Jason Salmans</div>
</span></font></div>
</div>
</body>
</html>