[Kea-users] IGEL DHCP-Option

[Francis Dupont]

"Wessel, Sebastian" writes:
> For our ThinClients on our network we are sending out our Management-Server
>  as option 224.

=> 224 is reserved for private use.

> /usr/local/etc/kea$ sudo keactrl start
> INFO/keactrl: Starting kea-dhcp4 -c /usr/local/etc/kea/kea.conf -d
> INFO/keactrl: Starting kea-dhcp-ddns -c /usr/local/etc/kea/kea.conf -d
> takko at takdeudhcp01:/usr/local/etc/kea$ 2017-01-17 08:49:08.294 ERROR [kea-d=
> hcp4.dhcp4/32500] DHCP4_INIT_FAIL failed to initialize Kea server: configur=
> ation error using file '/usr/local/etc/kea/kea.conf': definition for the op=
> tion 'dhcp4.IgelRMS-Server' having code '224' does not exist (/usr/local/et=
> c/kea/kea.conf:66:19)

=> yes it is not defined so Kea does not know how to fill it.

> The options in the conf-file looks like this:
> 
>     "option-data" :
>     [
>       {
>         <some other options>
>       },
>       {
>           "code": 224,
>           "name": "IgelRMS-Server",
>           "csv-format": true,
>           "data": "192.168.100.45"
>       }
>     ],
> 
> Does anybody have a clue, why the server isn't amused of this config?

=> you need to add an option-def at the global scope with the code,
the name and the type (looks like ipv4-address), etc. Look at
the "custom DHCPv4 options" in the admin manual.

Regards

Francis Dupont <fdupont at isc.org>