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

[Andreas]

Hi Francis,

What do you mean by
> before the option is decoded.
Define the class as the first one in the config? I already tried to do this:

  {
     // DRG546 Voice
     "name": "drg546-voice",
     "test": "substring(option[60].text, 0, 11) == 'drg-DRG546s'",
         "option-def": [
             {
                 "name": "vendor-encapsulated-options",
                 "code": 43,
                 "type": "binary",
                 "space": "dhcp4",
                 "array": false,
                 "encapsulate": ""
             }
         ],
  },

and then set the option in the subnet reservation:
  {
      "ip-address": "10.123.123.2",
      "option-data": [
          {
              "code": 43,
              "data": "5446545...",
              "name": "vendor-encapsulated-options",
              "space": "dhcp4",
              "csv-format": false
          }
      ],
      "hw-address": "00:AA:BB:CC:60:ED",
  },

Obviously this is not working.

You mean to define these legacy devices via global reservation? Would 
that change the behaviour that kea treats the "data"-part as different 
suboptions like it does in the above example?


BR
Andreas

Am 28.09.2026 um 19:09 schrieb Francis Dupont:
> Option 43 is a mess because it is underf specified so you can need
> different incompatible ways to decode it. Kea tries to solve this issue
> with per class option definition so you only need to put the incoming
> query in the right class before the option is decoded. Now it can be
> hairy, early global reservation lookup should help...
>
> Regards
>
> Francis Dupont <fdupont at isc.org>