Hi Vicky, team,
Good to know! I was busy on something else for the past few days, but I will
try to repo in my home lab for this issue and provide you the configs.
Basically, I configured some V6 subnets configuration based on your default
template kea-dhcp6.conf, then I added some customization data using option data
as below. After that, I tested the subnet hook by adding some new v6 subnets. I
highly suspect adding the option-data to some subnets are the trigger of this
bug. But I will test in my lab again and keep you updated.
"option-data": [
{
"space": "vendor-4491",
"name": "ccap-cores",
"code": 61,
"data": “xxxxx",
"always-send": true
}
On Apr 24, 2025, at 1:28 PM, Victoria Risk <vi...@isc.org> wrote:
I think if anything, OP should be praised and thanked, instead of accused,
by ISC for sincerely working hard to try to improve Kea, one of ISC's
projects. Do you claim to speak for ISC in your accusation against OP, given
that you made the accusation from an isc.org<http://isc.org/> email account?
Everyone has good intentions here. To clear up any confusion, Darren leads
ISC’s Technical Support team, and Doug is on that team. I also work for ISC.
Darren was posting from his gmail account in this thread but we’re all listed
on ISC’s web site if anyone wants to check. (Darren is out today which is the
only reason I am chiming in now.)
The OP is using our most recent development version, and therefore might have
been the first to stumble on a significant bug, so Darren was particularly
motivated to try to reproduce the problem and didn’t object to an email
off-list. Doug is also right, that a community mailing list is for open
community support and building up the body of public knowledge about the
software. It won’t scale if others start emailing configurations to people’s
private mailboxes and it is counter to the point of the open list.
Ideally if a user has a problem that they have good reason to suspect is a bug,
they should open a Gitlab issue. I encourage everyone who has deployed Kea to
make an account in our Gitlab instance
(https://gitlab.isc.org/isc-projects/kea) and contribute issues.
There is also a lot of grey area, when it is unclear if there is a
configuration error or an actual bug: that is where this list can be very
useful. Hopefully, when the OP resolves their specific problem, the result will
be posted here for everyone’s benefit.
Vicky Risk (yet another ISC person on the list)
Kind regards,
Chuck Zmudzinski
I a
https://blog.powerdns.com/2016/01/18/open-source-support-out-in-the-open
If there's things in your config you can't share publicly, as noted in
that post, start by reproducing your issue with details you can share.
-Doug
--
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<mailto: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
