Hi Doug,

Thanks for pointing me to the "Redefining Standard Options" documentation.
That example using Option 60 and the "ACME IP Phone" Vendor Class
Identifier was helpful.

However, in my case, the client does *not* set a known or consistent Vendor
Class Identifier (Option 60), so the server has no way of classifying it
into a specific client class like "ACMEphone".

My goal is to override or send custom data on Option 121, even though it's
a standard option, because the client expects some custom behavior under
that code (as was possible in ISC DHCP).

Given that the client's Option 60 is not predictable or predefined, is
there a way in Kea to:

   1.

   Override Option 121 globally (even outside client classification)?
   2.

   Or assign clients to a class dynamically based on other conditions, so a
   custom Option 121 can be applied?

Regards.
Dipesh


On Wed, Jun 25, 2025 at 12:51 AM Dipesh Kayastha <
er.dipesh.kayas...@gmail.com> wrote:

> Hi Kea Dev Team,
>
> I’m migrating from ISC DHCP to Kea and encountered an issue when
> attempting to define a custom option using code 121. In ISC DHCP, I was
> able to define option 121 for custom use as follows:
>
> option custom-option-121 code 121 = array of integer 8;
>
> In Kea, when I try to replicate that using:
>
> "option-def": [
>   {
>     "name": "custom-option-121",
>     "code": 121,
>     "type": "uint8",
>     "array": true
>
>   }
> ]
>
> I get the following error:
> DHCP4_PARSER_FAIL failed to create or run parser for configuration element
> option-def: unable to override definition of option '121' in standard
> option space 'dhcp4'
>
>
> I understand from the Kea ARM documentation (
> https://kea.readthedocs.io/en/latest/arm/dhcp4-srv.html#id5) that Option
> 121 is already part of the standard DHCPv4 option definitions. However, in
> my use case, I need to send custom data under option 121 because the client
> expects it.
>
> Is there a supported way in Kea to:
>
>    1.
>
>    Override standard options like 121 with custom format/data?
>    2.
>
>    Send custom data using option 121 in a way compatible with clients
>    expecting it?
>
> Any advice or suggested workarounds would be greatly appreciated.
> Note that this is not only for option 121, I am also using other option
> numbers also as custom option.
>
> Best regards,
> Dipesh
>
-- 
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