[Kea-users] [kea-dev] Vendor Specific Options (Code 17)

[sathish k]

Francis

   Thanks again for the reply . But i am slightly confused . In one of your previous reply  you mentioned

"=> I thought use a sheat of paper to compute the wanted value of the

vendor option with multiple vendors and insert the hexadecimal result
in the configuration. Now you can do it using a hook and some code
merging (v4) or pushing (v6) multiple vendor options with one vendor
per option from the configuration..."



this reply made me believe that its possible to do it through config file. and i got the same reply from other source at kea too.

do you know when #1518 will be available in the build ?





________________________________
From: Francis Dupont <fdupont at isc.org>
Sent: Saturday, April 2, 2022 5:01 AM
To: sathish k <sat98 at hotmail.com>
Cc: Francis Dupont <fdupont at isc.org>; kea-dev at lists.isc.org <kea-dev at lists.isc.org>; kea-users <kea-users at lists.isc.org>
Subject: Re: [kea-dev] Vendor Specific Options (Code 17)

sathish k writes:
>     Can you provide Sample config file that supports multiple vendors scena=
> rio below . Thanks

=> I can't because it is not currently supported.

> "option-data": [
>        {
>         "space": "dhcp6",
>         "name": "vendor-opts",
>         "code": 17,
>         "data": "0x270f"
>       },
>        {
>         "space": "dhcp6",
>         "name": "vendor-opts",
>         "code": 17,
>         "data": "0x6774"
>       },

=> note if it is allowed to specify more than once an option data of course
only one will be applied.

> The Relay -Reply that I got shows only one vendor (Cisco ) even though opti=
> on-data has Cisco and xyz(9999)

=> yes and it will be the result until #1518 is fully implemented.
I am afraid you have to write some code to do this.

Regards

Francis Dupont <fdupont at isc.org>

PS: the OptionCollection is a multimap so if you add multiple options
sharing the same code point they will be added to the packet. Now
there is no way to add more than one option 16 or 17 in the collection
without writing a hook doing this. The config can help by building
each option you want so the hook can just add the missing options.

PPS: the flex_option hook does not help here: it does not handle
multiple vendor options more than other code. Now it is planned to
add multiple vendor supports including for the flex_option in #1518
but the exact milestone is not yet scheduled...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20220403/a0f5a1b9/attachment.htm>