[Kea-users] config Kea via database.

[Peter Davies]

Hi Vadim,
    This behaviour may be caused by a known Kea Configuration Backend 
(CB) issue.
GitLab #2881 "DHCP4 Vendor-Specific Options do not get encapsulated when 
using
the DB Backend (mysql)"

See: https://gitlab.isc.org/isc-projects/kea/-/issues/2881

This issue was fixed in Kea development release  2.5.8.

If you are unable to upgrade to 2.6, a workaround may be to add the 
hexadecimal
data directly to option 43 instead of defining an encapsulated suboption 
separately.

For example, sub-option 61 with the value "XXX.XXX.XXX.XXX" could be 
represented as:
"3D0F5858582E5858582E5858582E585858"
3D = 61; 0F = 15 (length) and 5858582E5858582E5858582E585858 for 
XXX.XXX.XXX.XXX

This would look like this.

"options": [ {
"always-send": true,
"code": 43,
"csv-format": false,
"data": "3D0F5858582E5858582E5858582E585858",
"name": "vendor-encapsulated-options",
"never-send": false,
"space": "dhcp4"
...
}
If you intend to upgrade to Kea 2.6, I suggest you wait until Kea 2.6.1, 
which
is scheduled for release shortly. Kea 2.6.1 will include a fix for 
Gitlab #3481
"Subnet DHCP options in the config backend are not correctly 
encapsulated when
fetched from the config backend" which  affects vendor-encapsulated 
options saved
to the CB.

See: https://gitlab.isc.org/isc-projects/kea/-/issues/3481

Kind Regards Peter

Peter Davies
Support Engineer
Internet Systems Corporation