Hello Yu, There were three things changed that you have mentioned here. I'll try to clarify theses.
- option-class-tagging (https://kea.readthedocs.io/en/kea-2.7.5/arm/classify.html#option-class-tagging) - This is a completely new feature that allows the use of a class guard ("client-classes": [ <list> ]) inside of an option. This limits the option availability to only those clients that are members of one of the classes in the list. - client-class -> client-classes - the former "client-class" is now "client-classes" and is a list. This allows you, for example, to allow members of more than one class to obtain an address from a pool. No longer will you have to make meta-classes testing membership in several other classes. For an example of this change, see: https://kea.readthedocs.io/en/kea-2.7.5/arm/dhcp4-srv.html#reserving-client-classes-in-dhcpv4 - require-client-classes -> evaluate-additional-classes - This change is merely a renaming to make it more clear what the functionality actually does. The naming was unclear before and led to confusion (see: https://kea.readthedocs.io/en/kea-2.7.5/arm/dhcp4-srv.html#additional-classification) Thank you, Darren Ankney On Mon, Jan 13, 2025 at 3:00 PM Xiao, Yu (CCI-Atlanta) via Kea-users <kea-users@lists.isc.org> wrote: > > Hi ISC team, > > > > Last year, during my testing, I found that we can configure one client class > string to a subnet definition, but the configurations won’t be changed. Since > then, I have seen some similar discussions. And there’s a new feature in > 2.7.4 called Option Class-Tagging which allows us to give different subnets > different specific configurations. Also, the keyword has been changed from > "client-class" to "client-classes". It looks to me, now we can assign > multiple client classes to one subnet. But I don’t know if this is just a > placeholder for now, or it has already supported the “OR'ed list of classes”. > Can you help clarify? > > > > And it also mentions that "client-class" will be changed to > "require-client-class" in future versions. When will it be made to the next > stable version? Thank you. > > > > > > "client-classes": [ > > { > > "name": "RPD", > > "test": "substring(option[17].option[2].hex,0,3) == 'RPD'", > > "option-data": [ > > … > > ] > > }, > > { > > "name": "RPD_new", > > "test": "substring(option[1].hex,0,9) == 0x000200001011E42BC2", > > "option-data": [ > > … > > ], > > > > "id": 2, > > "subnet": "2000:109:20:5320::1/64", > > "pools": [ > > { > > "pool": "2000:109:20: 5320::1-2000:109:20: 5320::10" > > } > > ], > > "relay": { > > "ip-addresses": [ "2000:109:20: 5320::1" ] > > }, > > "interface": "ens18", > > "client-class": "RPD", > > "allocator": "iterative" > > }, > > { > > "id": 3, > > "subnet": "2000:109:20:2110::1/64", > > "pools": [ > > { > > "pool": "2000:109:20: 2110::1-2000:109:20: 2110::9" > > } > > ], > > "relay": { > > "ip-addresses": [ "2000:109:20: 2110::1" ] > > }, > > "interface": "ens18", > > "client-class": "RPD_new", > > "allocator": "iterative" > > } > > > > > > > > > > Best Regards, > > Yu > > > > -- > 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. > > Kea-users mailing list > Kea-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/kea-users -- 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. Kea-users mailing list Kea-users@lists.isc.org https://lists.isc.org/mailman/listinfo/kea-users
