Is anyone else seeing this? I had a similar problem in the past and people added in the ability to delete a DHCP entry from the table. Things have been stable for a few months now and, all of a sudden, after updating to 26.7.1_1, my address pool is getting exhausted. Normally, I am only using 2-3 addresses in a pool of 30+. These "declined" entries have a lifetime of 600 (instead of the default lifetime of 4000 which all of my "real" entries are set to). I'll have to try to do a wireshark trace to find out if anything sending out DHC requests on my network, but I am not aware of any new devices on my network or any config changes. As far as I know, the only recent change was updating to 26.7.1_1.
Luckily, it appears that my static pool is not being erroneously over-ridden (like it was last time) so, as long as I have static entries for the devices I want on the network (or existing dynamic entries), it is working fine.
What does "declined" mean as a "state" in the KeaDHCP Lease table? If OpnSense declined a DHCP request, why burn an entry in the Lease table? Even if it is for a shorter amount of time.
You probably have a faulty client polluting your leases.
https://github.com/opnsense/core/pull/10294
Thanks you. It appears that way, the OUI assigned to these devices are all proxmox. I do have a few Proxmox hypervisors but, as far as I can tell, my VMs and containers are all acting as expected. I will try to hunt this down.
One last OpnSense question. My Subnet pool is configured from 192.168.6.11 - 192.168.6.40 yet KeaDHCP appears to be dolling out other addresses. Specifically, 71 and 72
Sorry, have not had a ton of time to look into this. Turns out the problem is a Proxmox server of mine. Its a low end n150 based system which works great 95+% of the time. Every now and then though, it just crashes a burns. The odd part about it is the behavior when it is in this bad state. For whatever reason, it starts flooding my network with DHCP requests. Now that I know what is going on, I can try to combat it, or remove/replace this one system that keeps going belly up.