[Kea-users] Option 43 - Different formats for different client classes and host reservations

Francis Dupont fdupont at isc.org
Tue Sep 29 08:04:43 UTC 2026


Reread your initial message: my answer was about decoding which is critical
because when you try to decode an option 43 with the wrong definition
it can fail and the query be dropped. But you were about the encoding side
which is easier: option data are processed at config time, the option defs
which apply are the local class one and when not found the global. So you
must put the option data with the corresponding option defs.
Configured options are applied following a built-in order (there is a plan
to make this more flexible but currently it is only a plan), the first
match wins so this order is critical and is:
 - host reservation
 - pool
 - subnet
 - shared network
 - client classes
 - global
Please remember that client classes are late but as options are added in
the response late too in general you can configure what you want without
having to use the flex option hook library.
Last comment: ISC DHCP used a different order, in particular client classes
were sooner.

Regards

Francis Dupont <fdupont at isc.org>


More information about the Kea-users mailing list