Project

General

Profile

Actions

Bug #16719

open

Changing the MAC address on a Kea static lease does clear dhcp4.leases

Added by Jamie S 2 days ago. Updated 2 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
DHCP (IPv4)
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
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 #1

Updated by Jamie S 2 days ago

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

Actions #2

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

Also available in: Atom PDF