Hello everyone, 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 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.
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. Best Regards,
-- ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. [email protected]
