Static ip device stuck on dhcp ip range

Started by Fkhan6601, January 03, 2025, 07:09:08 AM

Previous topic - Next topic
Hi all,

I have a device that has been connected for over a year and it recently started doing this a couple days ago.

I have a camera that is connected to opnsense. Opnsense is the dhcp server, dns server, and firewall, but i have two routers connected as APs for a strong wifi signal. I also have all my devices on static addresses (for over a or two year) on isc ipv4 with a limited pool of ips for adding new devices. The app firewall also denies new devices until trusted.

When i add a new device, i uncheck deny unknown hosts and start setup. Then trust the device and add it to the static config. Recently, I did that and my camera on wifi went on the dhcp pool address for some reason. I have tried to restart opnsense, select ignore client uids, restarted the camera several times, changed dhcp pool and updated the max lease time to 2 hours.

It wont go back to the static address it was using. The hostname has not changed either. I have tried to save the device on the dhcp address as on the same static address in the lease section, but that also changed nothing.

If i turn on deny unknown clients again, the camera will go offline. If i turn it off, it connects with dhcp pool even if i change the cidr. What is going on here? Should be reinstalling opnsense? I dont see anything unusual related to this in any logs.

Anyone have any clues?

Anything in the DHCP logs?
It's legit for the camera to request its current address again.
If there's a reservation for a new address, the DHCP server should honor it, unless the reserved IP is currently used...
Can you ping the reserved IP? does it show up in ARP?

There is no entry in Interfaces: Diagnostics: ARP Table for the ip address.

I just removed every trace of it, reset the camera, and gave it the same static ip. Issue resolved.

Thanks for looking.