Project

General

Profile

Actions
Copy link

Bug #16719

closed

DHCP clients may not receive the reserved address after changing the DHCP static mapping

Added by Jamie S 3 months ago. Updated 3 days ago.

Status:
Closed
Priority:
Normal
Assignee:
Marcos M
Category:
DHCP (IPv4)
Target version:
2.9.0
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
26.07
Release Notes:
Force Exclusion
Affected Version:
2.8.1
Affected Architecture:
All

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

Actions
Copy link
 #1

Updated by Jamie S 3 months ago

Typo in the title, should be: Changing the MAC address on a Kea static lease does not clear dhcp4.leases

Actions
Copy link
 #2

Updated by → luckman212 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

Actions
Copy link
 #3

Updated by Marcos M 2 months ago

  • Status changed from New to Pull Request Review
  • Assignee set to Marcos M

Kea itself handles the memfile but we can try making sure the old lease - if one exists - has been cleared so that the reserved address is available for the new lease.
https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/1272

Actions
Copy link
 #4

Updated by Marcos M about 1 month ago

  • Status changed from Pull Request Review to Feedback
  • Target version set to 2.9.0
  • % Done changed from 0 to 100
  • Plus Target Version set to 26.07
Actions
Copy link
 #5

Updated by Jim Pingle about 1 month 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
Actions
Copy link
 #6

Updated by Marcos M 11 days ago

  • Subject changed from Changing the MAC address on a Kea static lease not does remove the old lease database entry to DHCP clients may not receive the reserved address after changing the DHCP static mapping
  • Status changed from Feedback to Ready To Test

Updating issue title to reflect the problem reported on the forum.

Actions
Copy link
 #7

Updated by Alhusein Zawi 11 days ago

  • Status changed from Ready To Test to Feedback

I changed the MAC address on a Kea static lease, and I do not see that warning in the logs. The DHCP client is able to receive the new IP.

26.07-DEVELOPMENT (amd64)
built on Sat Apr 25 6:00:00 UTC 2026
FreeBSD 16.0-CURRENT

Edit: Same results on 25.11.1.

Actions
Copy link
 #8

Updated by Marcos M 6 days ago

  • Release Notes changed from Default to Force Exclusion
Actions
Copy link
 #9

Updated by Marcos M 3 days ago

  • Status changed from Feedback to Closed
Actions
Copy link

Also available in: Atom PDF