<html aria-label="message body">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<span style="font-size: 14px;">Hello everyone,</span>
<div><span style="font-size: 14px;"><br>
</span></div>
<div><span style="font-size: 14px;">Last year, I tested on kea 2.6.2 with two different client classes Client_class1 and Client_class2 with similar configurations but slightly different, then I found my devices couldn’t match the Client_class2 even it should
match all the criteria. Some other kea users told me that it was because I defined the </span><span style="font-size: 14px;">Client_class1 configuration first then the Client_class2 configuration. So when the device came online, kea detects it match the criteria
of Client_class1 first, so it won’t check the rest of similar client classes.</span></div>
<div><span style="font-size: 14px;"><br>
</span></div>
<div><span style="font-size: 14px;">I am wondering if you have made some improvement on this and allow kea to match the most satisfying client class instead of the 1st defined one? Thank you.</span></div>
<div><span style="font-size: 14px;"><br>
</span></div>
<div><span style="font-size: 14px;"><br>
</span></div>
<div><span style="font-size: 14px;"><br>
</span></div>
<div><span style="font-size: 14px;"><br>
</span></div>
<div><span style="font-size: 14px;"><br>
</span></div>
<div><span style="font-size: 14px;"><br>
</span></div>
<div><span style="font-size: 14px;"><br>
</span></div>
<div><span style="font-size: 14px;">Best Regards,</span></div>
<div><span style="font-size: 14px;"><br>
</span></div>
<div><span style="font-size: 14px;"><br>
</span></div>
<div><br>
</div>
</body>
</html>