Re: [Kea-users] DDNS update for win10 clients

Hi, thanks for the clarification. I think we got a "works as designed" situation: The flags are indeed numerically zero, as I can see in wireshark... the full option 81 is like 51 08 00 00 00 41 50 46 45 4cQAPFEL Okay for me -- thinking twice about the

Re: [Kea-users] New Kea hook to call external scripts: kea-hook-runscript

I have just released version 1.1.0 of kea-hook-runscript: https://code.ffdn.org/zorun/kea-hook-runscript/src/master/CHANGELOG.md https://github.com/zorun/kea-hook-runscript/releases Full documentation is in the README: https://github.com/zorun/kea-hook-runscript/blob/master/README.md The

Re: [Kea-users] DDNS update for win10 clients

Thomas Markwalder writes: > However this will override the flags for all clients. => note there is a ticket about making dhcp-ddns setting local from a similar feature in ISC DHCP (e.g. in a client class matching MSFT vendor class). Regards Francis Dupont PS: I apologize for

Re: [Kea-users] DDNS update for win10 clients

Thanks for your reply. Here follow tcpdumps from the requests a windows and an android client, captured on the server machine with "tcpdump -i igb0 -vvv -n port 67 and port 68" (correct filter? I googled this one...). # # windows client: ipconfig /release, ipconfig /renew # 10:21:30.585569 IP