[Kea-users] Question about vivso (option 125) with suboption config
Marek Hajduczenia
mxhajduczenia at gmail.com
Tue Apr 16 14:22:11 UTC 2024
111 is just a random sub-option number I picked, the same is with the value of 1.
The way it works (at least how I understand it) is that the vendor-xxxx defines the vendor-specific number space (14810 and 16666, in my examples. The ‘code’ provides definition of the suboption, which goes within the given vendor space.
The screenshot above shows both Option 125 inserted, one for vendor 16666 and one for vendor 14810, with specific suboptions in them.
Attached is a pcap from my home lab – it should help piece it all together for you as well.
Marek
From: Kea-users <kea-users-bounces at lists.isc.org> On Behalf Of Philippe EA
Sent: Tuesday, April 16, 2024 2:02 AM
To: Kea user's list <kea-users at lists.isc.org>
Subject: Re: [Kea-users] Question about vivso (option 125) with suboption config
Thanks Marek.
That will help me.
Regarding your config, what code 1 and 111 refer to ? is it standard code or it refers to specific suboptions vendor ?
Regards.
Philippe EA
Technical Sales Engineer
Perle Systems EMEA
De : Kea-users <kea-users-bounces at lists.isc.org <mailto:kea-users-bounces at lists.isc.org> > De la part de Marek Hajduczenia
Envoyé : lundi 15 avril 2024 18:02
À : Kea user's list <kea-users at lists.isc.org <mailto:kea-users at lists.isc.org> >
Objet : Re: [Kea-users] Question about vivso (option 125) with suboption config
A working example from my home lab setup follows
"option-def": [
{
"name": "worldbox_adb_bmc",
"code": 1,
"type": "string",
"space": "vendor-14810",
"encapsulate": ""
},
{
"name": "vendor-16666-test",
"code": 111,
"type": "string",
"space": "vendor-16666",
"encapsulate": ""
}
],
"option-data": [
{
"name": "worldbox_adb_bmc",
"space": "vendor-14810",
"data": "'some URL from worldbox_adb_bmc'",
"always-send": true
},
{
"name": "vendor-16666-test",
"space": "vendor-16666",
"data": "'some URL from vendor-16666-test'",
"always-send": true
},
{
"name": "vivso-suboptions",
"data": "14810",
"always-send": true
},
{
"name": "vivso-suboptions",
"data": "16666",
"always-send": true
}
],
Regards
Marek
On Mon, Apr 15, 2024 at 9:51 AM Philippe EA < <mailto:pea at perle.com> pea at perle.com> wrote:
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 :
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
--
ISC funds the development of this software with paid support subscriptions. Contact us at <https://www.isc.org/contact/> https://www.isc.org/contact/ for more information.
To unsubscribe visit <https://lists.isc.org/mailman/listinfo/kea-users> https://lists.isc.org/mailman/listinfo/kea-users.
Kea-users mailing list
<mailto:Kea-users at lists.isc.org> Kea-users at lists.isc.org
<https://lists.isc.org/mailman/listinfo/kea-users> https://lists.isc.org/mailman/listinfo/kea-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20240416/e85fcee8/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 12720 bytes
Desc: not available
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20240416/e85fcee8/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 70834 bytes
Desc: not available
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20240416/e85fcee8/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 42716 bytes
Desc: not available
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20240416/e85fcee8/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 73390 bytes
Desc: not available
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20240416/e85fcee8/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pcap.20240416.01.dhcp.pcap
Type: application/octet-stream
Size: 1962 bytes
Desc: not available
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20240416/e85fcee8/attachment-0001.obj>
More information about the Kea-users
mailing list