> In fact you have two cases:
>  - the option gets a static value -> use a standard config to assign
>   this value to the option in responses
>  - the option gets a dynamic value i.e. a value based on a dynamic field
>   in requests -> use the flex-option hook
> In both cases it is often easier to use a client class to summarize
> a condition (easier to configure and even more important easier to debug).

But the question still remains:

Is it somehow possible to use someting like

{
   "Dhcp4": {
       "hooks-libraries": [
           {
               "library": "/usr/local/lib/libdhcp_flex_option.so",
               "parameters": {
                   "options": [
                       {
                           "code": 67,
                           "add": "ifelse(option[host-
name].exists,concat(option[host-name].text,'.boot'),'')"
                       }
                   ]
               }
           }
       ]
   }
}

with an add: component that uses an option string that has not been
already set in the client request, but only in the server reply.


Attachment: signature.asc
Description: This is a digitally signed message part

-- 
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

Reply via email to