KIA DHCP ISSUES
-
Hello, I'm having issues with my kia dhcp server on my lan interface only. When connecting a new device wired or wifi to my lan network 192.168.0.0 it won't give a ip address. I do have several static mappings and I have checked, there doesn't seem to any conflicting addresses, my dhcp pool is more than enough addresses. I've cleared the ARP table and dhcp leases and rebooted. That will clear it up for about 5 mins. I'm getting this message that floods my dhcp logs.
WARN [kea-dhcp4.alloc-engine.0x2f5cafe17400] ALLOC_ENGINE_V4_ALLOC_FAIL [hwtype=1 e2:11:e4:34:a3:b7], cid=[01:e2:11:e4:34:a3:b7], tid=0x32c2fcd2: failed to allocate an IPv4 address after 45 attempt(s)
also
WARN [kea-dhcp4.alloc-engine.0x2f5cafe16d00] ALLOC_ENGINE_V4_ALLOC_FAIL_SUBNET [hwtype=1 e0:bb:9e:1f:3e:fa], cid=[01:e0:bb:9e:1f:3e:fa], tid=0x6e4ecc6a: failed to allocate an IPv4 lease in the subnet 192.168.0.0/24, subnet-id 1, shared network (none)Interestingly, it's not doing this on any other vlan. So the only work around I can think of right now is to create another vlan with the same rule access and slowly move everything over to that vlan. Anyone else have this problem?
-
@khris2fer The only time I ran into that log was when the DHCP pool ran out of IPs.
Check Status > DHCP Leases at the bottom of the page.
-
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register LoginPrivacy Policy · Cookie Policy
