Bug #16719
open
Changing the MAC address on a Kea static lease not does remove the old lease database entry
100%
Description
Editing a Kea static lease to change the MAC address does not clear the old entry from /var/lib/kea/dhcp4.leases, so when the new device is connected a new IPv4 address is assigned to the device, instead of the one configured in the static lease. The Kea log also shows e.g.:
WARN [kea-dhcp4.alloc-engine.0x218397417400] ALLOC_ENGINE_V4_DISCOVER_ADDRESS_CONFLICT [hwtype=1 30:13:8b:79:56:af], cid=[01:30:13:8b:79:56:46], tid=0x65b2ee64: conflicting reservation for address 10.6.0.4 with existing lease Address: 10.6.0.4 Valid life: 7200 Cltt: 1752320340 Hardware addr: e0:73:e7:c6:6a:24 Client id: 01:e0:73:e7:c6:6a:31 Subnet ID: 1 Pool ID: 0 State: default Relay ID: (none) Remote ID: (none)
The old lease entry is not being removed from dhcp4.leases when the static lease edit form is saved with a new MAC.
Discussion thread on the forum: https://forum.netgate.com/topic/198115/changing-the-mac-address-on-a-kea-static-lease-does-not-work
Updated by Jamie S about 2 months ago
Typo in the title, should be: Changing the MAC address on a Kea static lease does not clear dhcp4.leases
Updated by → luckman212 about 2 months ago
Just want to also note that rebooting pfSense does not clear this condition, the only way to fix it currently is to hand edit that dhcp4.leases file
Updated by Marcos M about 1 month ago
- Status changed from New to Pull Request Review
- Assignee set to Marcos M
Updated by Jim Pingle 14 days ago
- Subject changed from Changing the MAC address on a Kea static lease does clear dhcp4.leases to Changing the MAC address on a Kea static lease not does remove the old lease database entry