Open bdonfouet opened 4 months ago
I think after adding a reservation Kea DHCP service needs a restart and then a reservation works fine in our tests. This is not clear in the UI though so maybe a possible improvement would be to restart Kea service when "Apply" button is pressed?
maybe worth noting that KEA largely ignores MAC address and bypasses reservations if it already has a pool-IP cached to requestor's machine-id . I dont know enough about DHCP inner-workings to understand why sorry. (perhaps as part of the general networking stack rather than KEA itself)
On Debian machines dbus-uuidgen
etc (ie resetting machine-id) can help alleviate the KEA DHCP cache pains, but I dont know how to ease issue that with SynologyOS, sorry
(hopefully just resetting the Kea Service is enough to fix for Syno's)
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Describe the bug
I ' running opnsense 24.1.6 and have reservations on Kea DHCP. i have a synology nas which interface is configured to dhcp mode, and a reservation on Kea with the mac address. After reboots, the NAS still get the old IP it was getting before i setup the reservation and never get the reserved ip!
To Reproduce
Steps to reproduce the behavior:
Expected behavior
When restarted my lan device after created the dhcp reservation, the device should received the ip set in reservation
Describe alternatives you considered
Screenshots
none
Relevant log files
In Kea logs, i can see that the device request his old adress(normal dhcp behaviour), and the dhcp server leased it despite the reservation
Additional context
i was using ISC DHCP before, and it was working as expected
Environment OPNsense 24.1.6 (amd64). AMD GX-424CC SOC with Radeon(TM) R5E Graphics (4 cores, 4 threads)