DHCP Static reservations are no longer working
DHCP Static reservations are no longer working
Recently I noticed that some of my IP camera's and servers stopped responding.
Upon investigation, it turns out that they suddenly received a different IP address. However, I have set static DHCP reservations for all of these devices but ever since the latest firmware these devices are handed out different IP addresses.
For example:
My backyard camera:
And frontyard camera:
They've had these fixed IP address since forever, but they recently received a totally different IP:
This obviously causes issues for my NVR and Home Assistant which use IP addresses rather than hostnames. From the DHCP Log for my backyard camera:
For the device that should recieve IP .14, I'm also seeing this in the logs. The DHCP server rejects the .16 request, but then hands it out anyway:
So on the 18th of October it stopped giving the proper DHCP static and instead gave the next free address in the DHCP scope. I'm running the Omada Controller in Docker, so it could be that there was a firmware update that day. I'm currently running Controller version 5.14.32.2 (Stable). I can not downgrade to 5.14.26.1 to test.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @US007
Thank you so much for taking the time to post the issue on TP-Link community!
US007 wrote
I'm seeing something similar…I have 1 apple TV device on the network that’s requesting DHCP every second. It’s filling up the logs…I tried using a DHCP reservation from the controller and also a fixed IP from the controller (not from the device itself). It’s the only Apple TV on the network doing this (I have 6, all the same model and iOS version). All devices have been rebooted…seems like some sort of bug on the controller firmware so I’ve disabled the Event for now to calm the logs down.
Controller is OC200 on 5.14.26.23
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID241258623, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!
- Copy Link
- Report Inappropriate Content
Hi @csinasac
Thank you so much for taking the time to post the issue on TP-Link community!
csinasac wrote
@Matva
Same here, I just upgraded to 1.2.3 and from what I can see DHCP reservation is now ignored. My cameras are getting different IP addresses than are reserved. version 1.2.2 seemed to work so I will try and downgrade.
Craig
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID241258621, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 596
Replies: 12
Voters 0
No one has voted for it yet.