KEA DHCPv4 will not change client from a dynamic IP to new static IP
The client keeps getting given a dynamic IP address that OPNsense calls "static" when its's not.
I have two esp32 devices, both joined the wireless network and OPNsense is the DHCP server using Kea.
I have 2 x static IP addresses setup, with the correct client MAC address and outside the dynamic range of the 10.220.220.0/24 scope 50-150 (10.220.220.162 & .163)
I've deleted the current leased addresses as given out, (10.220.220.5x something) and rebooted OPNsense. I reboot the esp32 devices and they keep getting a .5x address which under DHCP leases strangely is listed as a "static" address (which it's not, .5x is in the dynamic range).
This happened on 26.7.7_1 and now also on 26.7.2
I cannot get these clients to change to pickup a new assigned static IP address. There is nothing on .162 nor .163, arp shows these addresses as empty.
Warning
kea-dhcp4
WARN [kea-dhcp4.alloc-engine.0x3c4c2b483010] ALLOC_ENGINE_V4_DISCOVER_ADDRESS_CONFLICT [hwtype=1 b8:1f:3f:fe:2d:74], cid=[01:b8:1f:3f:fe:2d:74], tid=0x49607173: conflicting reservation for address 10.220.220.163 with existing lease Address: 10.220.220.163
Remote ID: (none)
Relay ID: (none)
State: default
Pool ID: 0
Subnet ID: 1
Client id: (none)
Hardware addr: 8c:53:e6:33:d4:b2
Cltt: 1786580276
Valid life: 28800
2026-08-13T18:47:44
Warning
kea-dhcp4
WARN [kea-dhcp4.alloc-engine.0x3c4c2b483010] ALLOC_ENGINE_V4_DISCOVER_ADDRESS_CONFLICT [hwtype=1 b8:1f:3f:fe:03:cc], cid=[01:b8:1f:3f:fe:03:cc], tid=0xb055b682: conflicting reservation for address 10.220.220.162 with existing lease Address: 10.220.220.162
can you get the client OS to do a DHCP release, then DHCP renew ?
Also your reservation doesn't have the CID populated, and kea by default will try and match on CID (Match client-id), rather than MAC address, there is an option to disable CID matching, and to then match on MAC address instead, in the OPNsense KEA subnets UI...
I personally turn of KEA CID matching, as many client's rarely populate it, however your logs show the client is populating the CID (cid=[01:b8:1f:3f:fe:2d:74])...so perhaps add the proper CID to the reservation, then have the client do a DHCP release, then DHCP renew...
If I'm reading that right, there's already a lease for IP address 10.220.220.163, with a different MAC address (8c:53:e6:33:d4:b2 vs b8:1f:3f:fe:2d:74). Kea won't allocate an address that's in use by an existing lease...