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

[Andreas]

Dear list,


I'm running Kea DHCPv4 3.0.1 and need to send option 43 in two different 
formats depending on the client type:

1) Vendor suboptions (TLV encoded) for a client class, using 
vendor-encapsulated-options-space with suboption code 1 containing an 
TR-069 ACS URL. This is working fine.

2) Raw binary for some real old Packetfront DRG546 CPE devices, where 
option 43 contains a plain ASCII string with binary encoded IP addresses 
in the format 
TFTP=<4-byte-binary-ip>;SW=...;INI=...;GK=<4-byte-binary-ip>;D=sip.example.com;A1=.... 
This needs to be sent as raw binary without TLV suboption parsing. These 
devices are so old that they don't understand the "new" concept of 
sub-options within Option 43...

I found that defining option-def with "type": "binary" and 
"encapsulate": "" inside a test client class for DRG546 devices works 
when the option data is defined in the class itself. However, as this 
option43 is device specific, we need the option data delivered by a host 
reservation, this is where Kea falls back to the global option 43 
definition and parses the binary data as TLV suboptions, splitting it 
incorrectly.

Is there a way to make the class-level option-def apply to host 
reservations as well? Or is there another approach to send raw binary 
option 43 data per host reservation while keeping the TLV suboption 
format for another client class?

Thanks in advance!


BR

Andreas


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20260928/ca40aade/attachment.htm>