<div dir="ltr"><div>Thanks Darren, <br></div><div><br></div><div>I think it was some sort of a fluke - once I rebooted the VM to remedy the issue with Stork registration, the problem seems to be gone. I hate bugs like this - they are ephemeral and next to impossible to reproduce, with the problem going away when the VM is rebooted. <br></div><div><br></div><div>Marek<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 9, 2024 at 4:02 AM Darren Ankney <<a href="mailto:darren.ankney@gmail.com">darren.ankney@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Marek,<br>
<br>
I'm still thinking about this one. Out of curiosity, could you try<br>
specifying the option-data inside of the "ecm-vince" client class? I<br>
am curious if that overrides the global option data.<br>
<br>
Thank you,<br>
Darren Ankney<br>
<br>
On Fri, May 3, 2024 at 4:16 PM <<a href="mailto:mxhajduczenia@gmail.com" target="_blank">mxhajduczenia@gmail.com</a>> wrote:<br>
><br>
> Good afternoon,<br>
><br>
><br>
><br>
> I observed a rather surprising behavior today in Kea 2.4.1 DHCPv6 server.<br>
><br>
><br>
><br>
> I have a global (shared) custom option value defined as follows. Note the config file value<br>
><br>
><br>
><br>
> {<br>
><br>
> "space": "vendor-4491",<br>
><br>
> "name": "config-file",<br>
><br>
> "code": 33,<br>
><br>
> "data": "WBDocCfg166_erouter6_no_nat_usp_v5_commscope_cert.cfg"<br>
><br>
> },<br>
><br>
><br>
><br>
> In one of the subnets, I assigned a custom value as follows<br>
><br>
><br>
><br>
> {<br>
><br>
> "id": 102,<br>
><br>
> "interface": "enp6s18",<br>
><br>
> "comment": "CMs connected to Vince's RPDs",<br>
><br>
> "subnet": "2600:6ce4:0:208::/64",<br>
><br>
> "relay": {<br>
><br>
> "ip-addresses": [ "2600:6ce4:0:3e::1" ]<br>
><br>
> },<br>
><br>
> "pools": [<br>
><br>
> {<br>
><br>
> "pool": "2600:6ce4:0:208::2 - 2600:6ce4:0:208:ffff:ffff:ffff:ffff",<br>
><br>
> "client-class": "ecm-vince",<br>
><br>
> "option-data": [<br>
><br>
> {<br>
><br>
> "space": "vendor-4491",<br>
><br>
> "name": "config-file",<br>
><br>
> "code": 33,<br>
><br>
> "data": "WBDocCfg166_upgrade.cfg"<br>
><br>
> },<br>
><br>
> {<br>
><br>
> "space": "dhcp6",<br>
><br>
> "name": "dns-servers",<br>
><br>
> "code": 23,<br>
><br>
> "data": "2600:6ce4:40:12c:8000::3"<br>
><br>
> }<br>
><br>
> ]<br>
><br>
> }<br>
><br>
> ]<br>
><br>
> },<br>
><br>
><br>
><br>
> hoping that it would override the parameter value assigned globally. Unfortunately, the TFTP server logs show that the previous config file value is still being served.<br>
><br>
><br>
><br>
> 20:01:57.672602 IP6 2600:6ce4:0:208::24.59455 > 2600:6ce4:0:42::132.69: TFTP, length 83, RRQ "WBDocCfg166_erouter6_no_nat_usp_v5_commscope_cert.cfg" octet blksize 1428 tsize 0<br>
><br>
> 20:01:59.745978 IP6 2600:6ce4:0:208::27.44638 > 2600:6ce4:0:42::132.69: TFTP, length 83, RRQ "WBDocCfg166_erouter6_no_nat_usp_v5_commscope_cert.cfg" octet blksize 1428 tsize 0<br>
><br>
> 20:02:00.584499 IP6 2600:6ce4:0:208::39.36093 > 2600:6ce4:0:42::132.69: TFTP, length 83, RRQ "WBDocCfg166_erouter6_no_nat_usp_v5_commscope_cert.cfg" octet blksize 1428 tsize 0<br>
><br>
> 20:02:00.684559 IP6 2600:6ce4:0:208::2a.57747 > 2600:6ce4:0:42::132.69: TFTP, length 83, RRQ "WBDocCfg166_erouter6_no_nat_usp_v5_commscope_cert.cfg" octet blksize 1428 tsize 0<br>
><br>
> 20:02:03.390078 IP6 2600:6ce4:0:208::9.35267 > 2600:6ce4:0:42::132.69: TFTP, length 83, RRQ "WBDocCfg166_erouter6_no_nat_usp_v5_commscope_cert.cfg" octet blksize 1428 tsize 0<br>
><br>
> 20:02:04.210522 IP6 2600:6ce4:0:208::3b.39781 > 2600:6ce4:0:42::132.69: TFTP, length 83, RRQ "WBDocCfg166_erouter6_no_nat_usp_v5_commscope_cert.cfg" octet blksize 1428 tsize 0<br>
><br>
> 20:02:04.429295 IP6 2600:6ce4:0:208::6.39985 > 2600:6ce4:0:42::132.69: TFTP, length 83, RRQ "WBDocCfg166_erouter6_no_nat_usp_v5_commscope_cert.cfg" octet blksize 1428 tsize 0<br>
><br>
> 20:02:04.483974 IP6 2600:6ce4:0:208::38.41514 > 2600:6ce4:0:42::132.69: TFTP, length 83, RRQ "WBDocCfg166_erouter6_no_nat_usp_v5_commscope_cert.cfg" octet blksize 1428 tsize 0<br>
><br>
> 20:02:04.813712 IP6 2600:6ce4:0:208::3a.36185 > 2600:6ce4:0:42::132.69: TFTP, length 83, RRQ "WBDocCfg166_erouter6_no_nat_usp_v5_commscope_cert.cfg" octet blksize 1428 tsize 0<br>
><br>
> 20:02:05.034628 IP6 2600:6ce4:0:208::37.42895 > 2600:6ce4:0:42::132.69: TFTP, length 83, RRQ "WBDocCfg166_erouter6_no_nat_usp_v5_commscope_cert.cfg" octet blksize 1428 tsize 0<br>
><br>
> 20:02:05.035990 IP6 2600:6ce4:0:208::3.57665 > 2600:6ce4:0:42::132.69: TFTP, length 83, RRQ "WBDocCfg166_erouter6_no_nat_usp_v5_commscope_cert.cfg" octet blksize 1428 tsize 0<br>
><br>
> 20:02:05.960857 IP6 2600:6ce4:0:208::8.34523 > 2600:6ce4:0:42::132.69: TFTP, length 83, RRQ "WBDocCfg166_erouter6_no_nat_usp_v5_commscope_cert.cfg" octet blksize 1428 tsize 0<br>
><br>
> 20:02:06.692774 IP6 2600:6ce4:0:208::35.36573 > 2600:6ce4:0:42::132.69: TFTP, length 83, RRQ "WBDocCfg166_erouter6_no_nat_usp_v5_commscope_cert.cfg" octet blksize 1428 tsize 0<br>
><br>
> 20:02:10.619007 IP6 2600:6ce4:0:208::29.39632 > 2600:6ce4:0:42::132.69: TFTP, length 83, RRQ "WBDocCfg166_erouter6_no_nat_usp_v5_commscope_cert.cfg" octet blksize 1428 tsize 0<br>
><br>
> 20:02:11.693711 IP6 2600:6ce4:0:208::10.48226 > 2600:6ce4:0:42::132.69: TFTP, length 83, RRQ "WBDocCfg166_erouter6_no_nat_usp_v5_commscope_cert.cfg" octet blksize 1428 tsize 0<br>
><br>
> 20:02:12.474559 IP6 2600:6ce4:0:208::1b.46737 > 2600:6ce4:0:42::132.69: TFTP, length 83, RRQ "WBDocCfg166_erouter6_no_nat_usp_v5_commscope_cert.cfg" octet blksize 1428 tsize 0<br>
><br>
> 20:02:12.974028 IP6 2600:6ce4:0:208::18.43246 > 2600:6ce4:0:42::132.69: TFTP, length 83, RRQ "WBDocCfg166_erouter6_no_nat_usp_v5_commscope_cert.cfg" octet blksize 1428 tsize 0<br>
><br>
> 20:02:13.018275 IP6 2600:6ce4:0:208::5.54250 > 2600:6ce4:0:42::132.69: TFTP, length 83, RRQ "WBDocCfg166_erouter6_no_nat_usp_v5_commscope_cert.cfg" octet blksize 1428 tsize 0<br>
><br>
> 20:02:13.082634 IP6 2600:6ce4:0:208::f.51793 > 2600:6ce4:0:42::132.69: TFTP, length 83, RRQ "WBDocCfg166_erouter6_no_nat_usp_v5_commscope_cert.cfg" octet blksize 1428 tsize 0<br>
><br>
> 20:02:14.953996 IP6 2600:6ce4:0:208::d.40428 > 2600:6ce4:0:42::132.69: TFTP, length 83, RRQ "WBDocCfg166_erouter6_no_nat_usp_v5_commscope_cert.cfg" octet blksize 1428 tsize 0<br>
><br>
> 20:02:16.716193 IP6 2600:6ce4:0:208::28.55492 > 2600:6ce4:0:42::132.69: TFTP, length 83, RRQ "WBDocCfg166_erouter6_no_nat_usp_v5_commscope_cert.cfg" octet blksize 1428 tsize 0<br>
><br>
> 20:02:17.513615 IP6 2600:6ce4:0:208::21.37665 > 2600:6ce4:0:42::132.69: TFTP, length 83, RRQ "WBDocCfg166_erouter6_no_nat_usp_v5_commscope_cert.cfg" octet blksize 1428 tsize 0<br>
><br>
> 20:02:17.842297 IP6 2600:6ce4:0:208::31.35849 > 2600:6ce4:0:42::132.69: TFTP, length 83, RRQ "WBDocCfg166_erouter6_no_nat_usp_v5_commscope_cert.cfg" octet blksize 1428 tsize 0<br>
><br>
><br>
><br>
> I attempted that a few times with no success. I also ran packet captures and the DHCPv6 packets do show only the global config-file value, irrespective of the override for the specific prefix.<br>
><br>
><br>
><br>
> Is this an expected behavior or am I hitting some known bug? I did review the documentation and it seems to imply that the override should work without any problems. Is there anything I am missing in the config to force the override to work?<br>
><br>
><br>
><br>
> Regards<br>
><br>
><br>
><br>
> Marek<br>
><br>
> --<br>
> ISC funds the development of this software with paid support subscriptions. Contact us at <a href="https://www.isc.org/contact/" rel="noreferrer" target="_blank">https://www.isc.org/contact/</a> for more information.<br>
><br>
> To unsubscribe visit <a href="https://lists.isc.org/mailman/listinfo/kea-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/kea-users</a>.<br>
><br>
> Kea-users mailing list<br>
> <a href="mailto:Kea-users@lists.isc.org" target="_blank">Kea-users@lists.isc.org</a><br>
> <a href="https://lists.isc.org/mailman/listinfo/kea-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/kea-users</a><br>
-- <br>
ISC funds the development of this software with paid support subscriptions. Contact us at <a href="https://www.isc.org/contact/" rel="noreferrer" target="_blank">https://www.isc.org/contact/</a> for more information.<br>
<br>
To unsubscribe visit <a href="https://lists.isc.org/mailman/listinfo/kea-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/kea-users</a>.<br>
<br>
Kea-users mailing list<br>
<a href="mailto:Kea-users@lists.isc.org" target="_blank">Kea-users@lists.isc.org</a><br>
<a href="https://lists.isc.org/mailman/listinfo/kea-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/kea-users</a><br>
</blockquote></div>