Ah, looking closer I think I may have found why the bootfile-url was also 
commented.

Somewhere else in the ISC DHCP config file we have:

```
option dhcp6.bootfile-url code 59 = string;
```

Which keama converts to this:

```
//    /// Kea does not allow redefinition of options
//    {
//      "space": "dhcp6",
//      "name": "bootfile-url",
//      "code": 59,
//      "type": "string"
//    },
```

And after that all occurrences of the bootfile-url option are commented out.

Sorry that I missed this initially.  Thanks for the support!

– Diogo

From: Kea-users <kea-users-boun...@lists.isc.org> on behalf of Diogo André de 
Assumpção via Kea-users <kea-users@lists.isc.org>
Date: Saturday, April 12, 2025 at 8:22 PM
To: Kea user's list <kea-users@lists.isc.org>
Cc: Diogo André de Assumpção <d...@meta.com>
Subject: Re: [Kea-users] ISC DHCP to Kea – Why KeaMa comments some options?
Thanks for the reply! So, In ISC DHCP, would that config mean that the `dhcp6. 
bootfile-url` option following the vendor-class would only be sent to clients 
matching that class? Thanks, – Diogo From: Kea-users <kea-users-bounces@ lists. 
isc. org>

Thanks for the reply!

So, In ISC DHCP, would that config mean that the `dhcp6. bootfile-url` option 
following the vendor-class would only be sent to clients matching that class?

Thanks,
– Diogo

From: Kea-users <kea-users-boun...@lists.isc.org> on behalf of Peter Davies 
<pet...@isc.org>
Date: Saturday, April 12, 2025 at 6:32 AM
To: Kea-users@lists.isc.org <kea-users@lists.isc.org>
Subject: Re: [Kea-users] ISC DHCP to Kea – Why KeaMa comments some options?
Hi Diogo I ran this config snippet through Keama and got: Started parsing new 
subnet declaration in line 1 (. . . )/bc97e1f6-17a1-11f0-8122-0242ac120002. 
conf line 3: unknown option dhcp6. vendor-class option dhcp6. vendor-class 0 ^ 
Could this be
Hi Diogo
   I ran this  config snippet through Keama and got:

Started parsing new subnet declaration in line 1

(...)/bc97e1f6-17a1-11f0-8122-0242ac120002.conf line 3: unknown option 
dhcp6.vendor-class

  option dhcp6.vendor-class 0

               ^

Could this be because option 16 is expected to be sent by the client and not by 
the server?

/Peter

________________________________
From: "Kea-users@lists.isc.org" <kea-users@lists.isc.org>
To: "Kea-users@lists.isc.org" <kea-users@lists.isc.org>
Cc: "Diogo André de Assumpção" <d...@meta.com>
Sent: Friday, 11 April, 2025 17:40:29
Subject: [Kea-users] ISC DHCP to Kea – Why KeaMa comments some options?

Hi all,

I’m using KeaMa to validate a few things around a planned migration from ISC to 
Kea. I noticed that for some v6 options the script will output a Kea version of 
the ISC config, but comment it out. Any idea why?

Here’s an example:

ISC:

subnet6 2001:db8:1234::/64 {
  option dhcp6.name-servers 2001:DB8:1234::53;
  option dhcp6.vendor-class 0 10 "HTTPClient";
  option dhcp6.bootfile-url 
"http://deploy.cisco.com/install/ipxe2/ipxeb.efi<https://urldefense.com/v3/__http:/deploy.cisco.com/install/ipxe2/ipxeb.efi__;!!Bt8RZUm9aw!_7Pw9jyv9RtUR1CuvwITq7M3xO6uqAO0upBEpcJiKGVOtN8k29ar6kSCssKgXnr_QDO6PA$>";
  pool6
  {
      range6 2001:DB8:1234::320 2001:DB8:1234::1000;
  }
}


Kea

{
  "id": 1997,
  "subnet": "2001:db8:1234::/64",
  "option-data": [
    {
      "space": "dhcp6",
      "name": "dns-servers",
      "code": 23,
//          "original-data": "2001:DB8:1234::53",
      "data": "2001:db8:1234::::53"
    }
//        {
//          "space": "dhcp6",
//          "name": "vendor-class",
//          "code": 16,
//          "data": "0, 10, HTTPClient"
//        }
//        {
//          "space": "dhcp6",
//          "name": "bootfile-url",
//          "code": 59,
//          "data": 
"http://deploy.cisco.com/install/ipxe2/ipxeb.efi<https://urldefense.com/v3/__http:/deploy.cisco.com/install/ipxe2/ipxeb.efi__;!!Bt8RZUm9aw!_7Pw9jyv9RtUR1CuvwITq7M3xO6uqAO0upBEpcJiKGVOtN8k29ar6kSCssKgXnr_QDO6PA$>"
//        }
  ],
  "pools": [
    {
      "pool": "2001:db8:1234::320 - 2001:db8:1234::1000"
    }
  ]
},


Thanks!
– Diogo

--
ISC funds the development of this software with paid support subscriptions. 
Contact us at 
https://www.isc.org/contact/<https://urldefense.com/v3/__https:/www.isc.org/contact/__;!!Bt8RZUm9aw!_7Pw9jyv9RtUR1CuvwITq7M3xO6uqAO0upBEpcJiKGVOtN8k29ar6kSCssKgXnouNLj_Og$>
 for more information.

To unsubscribe visit 
https://lists.isc.org/mailman/listinfo/kea-users<https://urldefense.com/v3/__https:/lists.isc.org/mailman/listinfo/kea-users__;!!Bt8RZUm9aw!_7Pw9jyv9RtUR1CuvwITq7M3xO6uqAO0upBEpcJiKGVOtN8k29ar6kSCssKgXnotrkeVoQ$>.

Kea-users mailing list
Kea-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/kea-users<https://urldefense.com/v3/__https:/lists.isc.org/mailman/listinfo/kea-users__;!!Bt8RZUm9aw!_7Pw9jyv9RtUR1CuvwITq7M3xO6uqAO0upBEpcJiKGVOtN8k29ar6kSCssKgXnotrkeVoQ$>
-- 
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