Hi Marek,

I was able to find in the correct section of the documentation by
first looking at this chart of options in Kea:
https://kea.readthedocs.io/en/kea-2.4.1/arm/dhcp6-srv.html#id3 and
following the link there for option 17:
https://kea.readthedocs.io/en/kea-2.4.1/arm/dhcp6-srv.html#dhcp6-vendor-opts

Something like this MIGHT work:

{
  "Dhcp6": {
    "option-def": [
      {
        "name": "worldbox_adb_bmc",
        "code": 1,
        "type": "string",
        "space": "vendor-14810",
        "encapsulate": ""
      }
    ],
    "option-data": [
      {
        "name": "worldbox_adb_bmc",
        "space": "vendor-14810",
        "data": "'tmpwh2.cvs.adbglobal.com'",
        "always-send": true
      },
      {
        "name": "vendor-opts",
        "data": "14810"
      }
    ]
  }
}

Thank you,
Darren Ankney

On Fri, Mar 8, 2024 at 9:50 AM Marek Hajduczenia
<mxhajducze...@gmail.com> wrote:
>
> Yeah, I forgot to mentioned that indeed - Option 17 is specific to IPv6. I 
> was able to get that done for DHCPv4 without any problems, but v6 side seems 
> to be using slightly different configuration logic, which does not seem to be 
> documented anywhere, at least that I can find.
>
> Thanks !
>
> Marek
>
> On Fri, Mar 8, 2024 at 3:42 AM Darren Ankney <darren.ank...@gmail.com> wrote:
>>
>> Hi Marek,
>>
>> It is unclear to me.  Is this for DHCPv6?
>>
>> Thank you,
>> Darren Ankney
>>
>> On Thu, Mar 7, 2024 at 10:51 PM Marek Hajduczenia
>> <mxhajducze...@gmail.com> wrote:
>> >
>> > Dear mailing list users,
>> >
>> > I have been trying to create an Option 17 with a specific structure for a 
>> > vendor with the ID of 14810, where all I have is a sub-option 1, 
>> > containing a string with an arbitrary FQDN. I have a working code for ISC 
>> > DHCP, but I have not been able to locate a working example of an 
>> > implementation for Kea.
>> >
>> > # ADB VSIO
>> > option space worldbox_adb code width 2 length width 2 hash size 1;
>> > option worldbox_adb.bmc code 1 = text;
>> > option vsio.worldbox_adb code 14810 = encapsulate worldbox_adb;
>> >
>> > # use the option within a subnet
>> > ...
>> > option worldbox_adb.bmc "tmpwh2.cvs.adbglobal.com";
>> > ...
>> >
>> > My failed attempt to translate looks like the following, but it does not 
>> > produce any particular output as confirmed with the packet capture. DNS 
>> > servers are present, so I am sure the config is parsed correctly.
>> >
>> >                 "option-data": [
>> >                                 {
>> >                                         "name": "dns-servers",
>> >                                         "data": "2001:db8:2::dead:beef, 
>> > 2001:db8:2::cafe:babe"
>> >                                 }, {
>> >                                         "space": "vendor-14810",
>> >                                         "name": "bmc",
>> >                                         "data": "tmpwh2.cvs.adbglobal.com"
>> >                                 }, {
>> >                                         "name": "vendor-14810-bmc"
>> >                                 } ]
>> >                 } ],
>> >
>> >                 "option-def": [ {
>> >                         // We define a short name, so the option can be 
>> > referenced by name.
>> >                         // The option has code 2 and resides within vendor 
>> > space 25167.
>> >                         // Its data is a plain string.
>> >                         "name": "bmc",
>> >                         "code": 1,
>> >                         "space": "vendor-14810",
>> >                         "type": "string",
>> >                         "array": false,
>> >                         "encapsulate": ""
>> >                 }, {
>> >                         "name": "vendor-14810-bmc",
>> >                         "code": 14810,
>> >                         "type": "empty",
>> >                         "space": "dhcp6",
>> >                         "encapsulate": "bmc"
>> >                 } ],
>> >
>> > I did not see any example showing how to build Option 17 anywhere. Any 
>> > pointers / examples would be really appreciated.
>> >
>> > Marek
>> > --
>> > ISC funds the development of this software with paid support 
>> > subscriptions. Contact us at https://www.isc.org/contact/ for more 
>> > information.
>> >
>> > To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.
>> >
>> > Kea-users mailing list
>> > Kea-users@lists.isc.org
>> > https://lists.isc.org/mailman/listinfo/kea-users
>> --
>> ISC funds the development of this software with paid support subscriptions. 
>> Contact us at https://www.isc.org/contact/ for more information.
>>
>> To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.
>>
>> Kea-users mailing list
>> Kea-users@lists.isc.org
>> https://lists.isc.org/mailman/listinfo/kea-users
>
> --
> ISC funds the development of this software with paid support subscriptions. 
> Contact us at https://www.isc.org/contact/ for more information.
>
> To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.
>
> Kea-users mailing list
> Kea-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/kea-users
-- 
ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.

To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.

Kea-users mailing list
Kea-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/kea-users

Reply via email to