KEA DHCP not allocating IPV4 addresses.
-
I keep having this issue. Everything I’ve found online says the issue was resolved.
Mar 30 22:27:05 kea-dhcp4 38094 WARN [kea-dhcp4.alloc-engine.0x20c18486e810] ALLOC_ENGINE_V4_ALLOC_FAIL_CLASSES [hwtype=1 90:72:40:02:ec:47], cid=[01:90:72:40:02:ec:47], tid=0x231a46b: Failed to allocate an IPv4 address for client with classes: ALL, pool_lan_0, pool_opt8_0, pool_opt7_0, pool_opt6_0, pool_opt5_0, pool_opt4_0, pool_opt3_0, UNKNOWN
Mar 30 22:27:05 kea-dhcp4 38094 WARN [kea-dhcp4.alloc-engine.0x20c18486e810] ALLOC_ENGINE_V4_ALLOC_FAIL [hwtype=1 90:72:40:02:ec:47], cid=[01:90:72:40:02:ec:47], tid=0x231a46b: failed to allocate an IPv4 address after 225 attempt(s)
I had to change out of KEA to resolve this issue. Any tips? Thanks.
-
Without showing how kea Ipv4 for that LAN (or LANs) was set up ?
No way.
No one has a list with items like "do this and it will fail" but your post is a proof that the list isn't empty
-
The UNKNOWN class in that allocation failure is the key clue. KEA uses client classification to control which pool an address comes from. When a client shows as UNKNOWN in the allocation failure message, it usually means either the pool has a require-client-classification directive that this client does not satisfy, or there is a client-class restriction on the pool that excludes clients in the UNKNOWN class. Check your kea-dhcp4.conf - if any of your pools have client-class or require-client-classification set, that is likely why this client is being rejected. Also worth checking: is the MAC 90:72:40:02:ec:47 appearing from the expected interface? If that device is somehow arriving on a different VLAN or interface than where the pool is bound, KEA might not be matching it to the right subnet/pool definition at all.
