pfSense

This is on my SG-5100 which is currently running 25.07.1-RELEASE (amd64), but from Reddit comments (see below) this has been around for a while.

I keep seeing:

WARN [kea-dhcp4.alloc-engine.0x18d8e0216d00] ALLOC_ENGINE_V4_DISCOVER_ADDRESS_CONFLICT

in my DHCP logs. The IP and MAC it warns about are assigned to this IP address: 192.168.20.248. Nothing else is on this IP address and the Address Pool for this interface. The DHCP pool is .30 to .230 so DHCP should not be assigning addresses in this range.

the complete error message is (MAC address and my domain replaced by X's):

WARN [kea-dhcp4.alloc-engine.0x18d8e0216d00] ALLOC_ENGINE_V4_DISCOVER_ADDRESS_CONFLICT [hwtype=1 d0:76:02:1b:18:6e], cid=[01:00:00:00:00:00:00], tid=0xc91c454d: conflicting reservation for address 192.168.20.248 with existing lease Address: 192.168.20.248 Valid life: 21600 Cltt: 1750997378 Hardware addr: XX:XX:XX:1b:18:6e Client id: 01:d0:76:02:1b:18:6e Subnet ID: 3 Pool ID: 0 State: default Relay ID: (none) Remote ID: (none) User context: { "Netgate": { "option-data": { "domain-name": "XXX.XXX" } } }

The problem with this is, THERE IS NOT a conflict and my DHCP logs are flooded with these errors, rending the log nearly useless (it is hard to find meaningful info when these errors show up every few minutes).

I poseted this to Reddit (see https://www.reddit.com/r/PFSENSE/comments/1lmwtys/keadhcp4_throwing_warning_on_static_ipwarn/) and was told this is long-standing KEA bug. Jim Thompson said that Netgate fixes FreeBSD bugs, but that was 4 months ago and no word.

Creating this bug so this can be addressed