Hi Darren, (seems my last mail did not went well)
thanks for pointing me to that site.
The conversion is not quit as expected.
The definitions are clear to me although there is a problem (according to the
comments) with setting a space width of 4 as kea only accepts a width of 1
// /// Kea does not allow redefinition of options
// {
// "space": "dhcp4",
// "name": "option125",
// "code": 125,
// "type": "empty",
// "encapsulate": "vivso"
// }
],
// "option-space": {
// "name": "vivso",
// /// Only code width 1 is supported
// "code-width": 4
// },
"option-data": [
// {
// "space": "vivso",
// "name": "iana",
// "code": 0,
// "original-data": "01:01:01",
// "csv-format": false,
// /// Please consider to change last type in the record to binary
// /// Reference Kea #246
// "data": "010101"
// }
This might be a problem as the vendor states a width of 4 is needed but I have
not tested this so it might still work.
Other problem is that besides the strange (and possibly complicated) way of
selecting the scope to apply these options, they are all commented.. so none
are applied.
// "statement": {
// "if": {
// "condition": {
// "equal": {
// "left": {
// "substring": {
// "expression": {
// "option": {
// "universe": "dhcp",
// "name": "host-name",
// "code": 12
// }
// },
// "offset": 0,
// "length": 6
// }
// },
// "right": "geneos"
// }
// },
// "then": [
// {
// "option": {
// "space": "bbf",
// "name": "acs",
// "code": 11,
// "data":
"http://192.168.21.1:7547/ACSServer/services/ACSServlet";
// }
// },
// {
// "option": {
// "space": "bbf",
// "name": "provisioningcode",
// "code": 12,
// "data": "provisioning code value"
// }
// },
// {
// "option": {
// "space": "bbf",
// "name": "minwaitinterval",
// "code": 13,
// "data": "1"
// }
// },
// {
// "option": {
// "space": "bbf",
// "name": "retryintervalmultiplier",
// "code": 14,
// "data": "10"
// }
// },
// {
// "option": {
// "space": "genexis",
// "name": "config",
// "code": 3,
// "data": "tftp://192.168.21.1/test.cfg";
// }
// }
// ]
// }
// },
Should I just remove the comments (//) ? Not much faith in seeing this working
....
Regards
Ronald
________________________________
Van: Kea-users <kea-users-boun...@lists.isc.org> namens Darren Ankney
<darren.ank...@gmail.com>
Verzonden: donderdag 20 juli 2023 20:03
Aan: kea-users@lists.isc.org <kea-users@lists.isc.org>
Onderwerp: Re: [Kea-users] Trying to get GeniesACS / Genexis running
Hi,
Have a look at: https://dhcp.isc.org this may help you with these
conversions from ISC DHCP to Kea.
Thank you,
Darren Ankney
On Thu, Jul 20, 2023 at 11:10 AM DDFR | Ronald Blaas
<ronald.bl...@ddfr.nl> wrote:
>
> Hi All,
>
> As isc-dhcp is EOL/EOS I am looking into using isc-kea-dhcp.
>
> But I am having troubles converting the ACS options to kea-dhcp standards.
>
> these are the options which are needed for Genexis (and are working for
> isc-dhcp)
>
> option space bbf;
> option bbf.acs code 11 = text;
> option bbf.provisioningcode code 12 = text;
> option bbf.minwaitinterval code 13 = unsigned integer 32;
> option bbf.retryintervalmultiplier code 14 = unsigned integer 32;
>
> option space genexis;
> option genexis.fw code 2 = text;
> option genexis.config code 3 = text;
>
> option space vivso code width 4;
> option vivso.iana code 0 = string;
> option vivso.iana 01:01:01;
>
> option vivso.bbf code 3561 = encapsulate bbf;
> option vivso.genexis code 25167 = encapsulate genexis;
>
> option option125 code 125 = encapsulate vivso;
>
>
> So how to convert these options?
>
> I get the basics like:
> "option-def": [
> {
> "name": "tftp_fw",
> "code": 2,
> "space": "genexis",
> "type": "string"
> },
> {
> "name": "tftp_cfg",
> "code": 3,
> "space": "genexis",
> "type": "string"
> },
> {
> "name": "acs",
> "code": 11,
> "space": "bbf",
> "type": "string"
> },
> {
> "name": "acs_minwaitinterval",
> "code": 13,
> "space": "bbf",
> "type": "uint32"
> },
> {
> "name": "acs_retryintervalmultiplier",
> "code": 14,
> "space": "bbf",
> "type": "uint32"
> },
>
> but I somehow need to encapsulate all of these.
> It is unclear to me how to encapsulate these.
>
> Unfortunately verdors are not up 2 speed with the ending of isc-dhcp very
> little information is available..
>
> Any help is appreciated
>
> Regards,
>
> --
> 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
