@Gertjan said in Kea DHCPv6 and clients with unstable IAID:
@rolfl said in Kea DHCPv6 and clients with unstable IAID:
by adding /usr/local/lib/libdhcp_flex_id.so to
... wouldn't that be :
/usr/local/lib/kea/hooks/
for pfSense ? I found some kea libraries there.
Correct, I must have been copying from a google search.
Regardless, the file isn't there.
I you could find a pre build "libdhcp_flex_id.so" (build against FreeBSD 15.x - light up a candle, and copy it in place) it might just work.
PfSense is using Kea 2.6.2. Apparently pre 3.0 Kea had this library as a premium feature and requires a token to enable it.
Btw : just to be sure : these devices use Wifi, right ? So it could be the wifi that 'breaks' every 10 minutes, so a DHCP initial 'boot' request will get emitted every time ? That stull doesn't expmlain why the IAID is randomized like that.
I have checked unifi logs for the devices and there is no evidence of disconnect/connect behavior for wifi.
If this isn't the case, why not mentioning the device by type, serial number, brand etc ?
So we will all know what device not to chose at any cost, as it is known that every constructor out there wants to break IPv6, and some of them are doing a great job.
I did mention that the brand was TAPO / TP-link, particularly the matter compatible wifi light switches.
The model numbers are: S505, S505D, S515, P125M.