Ad Schellevis

@mimugmail but if I'm not mistaken, they are mutually exclusive (so only one applies for that specific configuration)

> Based on 9.3 of https://www.isc.org/docs/2023kea_custom_options.pdf, there is a way to apply different options for different clients. But I would like to keep it as simple as possible.... these type...

@reitermarkus although it feels a bit like using a cannon to kill a mosquito, maybe it's something we can't prevent for these custom options (I was hoping to keep this...

@reitermarkus what if we merge the definitions and the data? from a data perspective the split might be cleaner, but from a user input perspective the question is how often...

I don't mind changing that for you, but if you want to give it a shot, usually we add a style to the field and hook an event. For example...

@reitermarkus I don't think we should add the client class now as the relation between both entries is not the same (usually a client class contains a set of options)....

Maybe a stupid question, but can't we use `uuids` to bind the definitions and payload together? Personally I have a hard time finding definitions for kea fields in different area's,...

hmm, that's annoying. Partly this is difficult in terms of templating (overcomplicated `jinja` templates are hard to maintain) and to some degree the user input is also problematic. We could...

@reitermarkus can you try the code currently in master? https://github.com/opnsense/core/commit/3f184a695fdbcbe4071f61da54227a437da94bcd adds the "vendor-encapsulated-options-space" with a minimal set of options. I haven't tested this myself, but the generated configuration on my...

@mimugmail tried it out, didn't seem to work, but config looks as expected. I've moved the feature into its own branch for now implementing https://github.com/opnsense/core/commit/79f62cf681afd722ca2d797901554ffcb2e73460 (kea_custom_opt_pr7361)