Show Posts
1
24.1 Legacy Series / KEA-Problem with Reservation: ALLOC_ENGINE_V4_DISCOVER_ADDRESS_CONFLICT
« on: February 12, 2024, 10:54:18 am »
Hi All,
I migrated to KEA yesterday hoping to try it out and for the most part things seem to work.
However I am running into a weird issue with one of my devices for which I created a reservation.
I created the reservation without errors and initially the device even takes the address I assigned. However after a few minutes I see the following in the logs:
2024-02-12T10:38:18 Informational kea-dhcp4 INFO [kea-dhcp4.leases.0x834ee2f00] DHCP4_LEASE_ADVERT [hwtype=1 xx:xx:xx:xx:a9:93], cid=[01:00:00:00:00:00:00], tid=0x2bf8807b: lease 10.0.0.103 will be advertised
None None Remote ID: (none)
None None Relay ID: (none)
None None State: default
None None Pool ID: 0
None None Subnet ID: 3
None None Client id: 01:xx:xx:xx:xx:a9:93
None None Hardware addr: xx:xx:xx:xx:a9:93
None None Cltt: 1707730161
None None Valid life: 3600
2024-02-12T10:38:18 Warning kea-dhcp4 WARN [kea-dhcp4.alloc-engine.0x834ee2f00] ALLOC_ENGINE_V4_DISCOVER_ADDRESS_CONFLICT [hwtype=1 xx:xx:xx:xx:a9:93], cid=[01:00:00:00:00:00:00], tid=0x2bf8807b: conflicting reservation for address 10.0.0.26 with existing lease Address: 10.0.0.26
After which the device promptly changes IP to 10.0.0.103.
This comes back in the log every 5 minutes and every time it getś a new IP. But it never stays on the IP I reserved for it (this would be 10.0.0.26 as shown in the error).
I have several other reservations setup in the same range and these all work fine.
I tried recreating the reservation several times already. Rebooted the OPNsense box. Rebooted the device several times. But I keep getting this error and the device moving IP every 5 minutes.
Any idea what is going on here? Any help is appreciated.
I migrated to KEA yesterday hoping to try it out and for the most part things seem to work.
However I am running into a weird issue with one of my devices for which I created a reservation.
I created the reservation without errors and initially the device even takes the address I assigned. However after a few minutes I see the following in the logs:
2024-02-12T10:38:18 Informational kea-dhcp4 INFO [kea-dhcp4.leases.0x834ee2f00] DHCP4_LEASE_ADVERT [hwtype=1 xx:xx:xx:xx:a9:93], cid=[01:00:00:00:00:00:00], tid=0x2bf8807b: lease 10.0.0.103 will be advertised
None None Remote ID: (none)
None None Relay ID: (none)
None None State: default
None None Pool ID: 0
None None Subnet ID: 3
None None Client id: 01:xx:xx:xx:xx:a9:93
None None Hardware addr: xx:xx:xx:xx:a9:93
None None Cltt: 1707730161
None None Valid life: 3600
2024-02-12T10:38:18 Warning kea-dhcp4 WARN [kea-dhcp4.alloc-engine.0x834ee2f00] ALLOC_ENGINE_V4_DISCOVER_ADDRESS_CONFLICT [hwtype=1 xx:xx:xx:xx:a9:93], cid=[01:00:00:00:00:00:00], tid=0x2bf8807b: conflicting reservation for address 10.0.0.26 with existing lease Address: 10.0.0.26
After which the device promptly changes IP to 10.0.0.103.
This comes back in the log every 5 minutes and every time it getś a new IP. But it never stays on the IP I reserved for it (this would be 10.0.0.26 as shown in the error).
I have several other reservations setup in the same range and these all work fine.
I tried recreating the reservation several times already. Rebooted the OPNsense box. Rebooted the device several times. But I keep getting this error and the device moving IP every 5 minutes.
Any idea what is going on here? Any help is appreciated.