[Kea-users] Question about vivso (option 125) with suboption config

[Philippe EA]

Hi All,



I would like to get a proper configuration for option 125 (vivso), and got some questions hope you guys can help me.



1st question :

Here is my current config for bootfile name :

{

    "subnet4": [ {

        "reservations": [

        {

            "hw-address": "aa:bb:cc:dd:ee:ff",

            "next-server": "10.171.20.254",

            "server-hostname": "10.171.20.72",

            "boot-file-name": " dhcp-ztp.txt"

        } ]

    } ]

}



With this config, the boot file is downloaded from a TFTP server,

How to switch from TFTP to HTTP server? what am I missing on the config?



2nd question : the config below is adapted from an existing vivso config

{

    "option-def": [

    {

        "name": "tftp",

        "code": 2,

        "space": "vendor-1966",

        "type": "string"

    } ],



    "client-classes": [

    {

        "name": "Perle",

        "test": "substring(option[60].hex,0,4) == '1966'",

        "option-data": [

            {

                "name": "vivso-suboptions",

                "data": "1966",

                "encapsulate": "vendor-1966"

            },

            {

                "name": "tftp",

                "space": "vendor-1966",

                "data": "URL file name",

                "always-send": true

            }

        ]

    } ]

}



And below the details of the option125 with suboption from the vendor :

[Une image contenant texte, capture d'?cran, Police, ligne  Description g?n?r?e automatiquement]
[Une image contenant texte, capture d'?cran, Police, nombre  Description g?n?r?e automatiquement]
[Une image contenant texte, capture d'?cran, nombre, Police  Description g?n?r?e automatiquement]



So in HEX format it looks like this:

00:00:07:AE:14:10:01:01:05:0F:73:63:67:2D:36:2E:31:2E:54:32:35:2E:65:6D:67



00:00:07:AE : vendor id

14 : data length in total until the end (HEX format)

Suboption 10 --> define which protocol to use for bootfile/software

01: Data lenght

01: HTTP protocol

Suboption 05 --> define software file name

0F : Data length

73:63:67:2D:36:2E:31:2E:54:32:35:2E:65:6D:67 : File name in HEX format



So my question is :



This format was working with ISC DHCP, however, is it possible to adapt this vivso option and suboption vendor into KEA config ?



it doesn't need to be in HEX format, as long as it works the same that's fine.



If yes, how to define in my current config vivso config, the suboption 10 and suboption 5 with their data ?



Thank you.



Regards.



Philippe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20240415/2777d7f0/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 12720 bytes
Desc: image001.png
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20240415/2777d7f0/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 70834 bytes
Desc: image002.png
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20240415/2777d7f0/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 42716 bytes
Desc: image003.png
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20240415/2777d7f0/attachment-0005.png>