DHCP Reservation cannot be deleted, respectively is not freeing the ip
Hello,
i am using Omada Controler V 5.9.31 and i have a problem with DCHP IP-Reservation.
I have a working DHCP Reservation for a device, the device always gets the definied ip adress. Now the device got defect and i had to replace it. So i deleted the old DHCP Reservation rule under settings/Services/DHCP Reservations and i created a new one with the new devices under the Client-List ( Config / Use Fixed IP Address).
I used the old IP Adress, after clicking apply i got a "Succeeded" message.
But the IP Adress is not going to be assigned.
Instead of 192.168.1.57 the device gets 192.168.1.200?
I tried to use a never used IP-Adress (192.168.1.58) and with this adress it is working.
So using a never used ip is working, using an already once used Ip (but of course the old rule is deleted) is not working?
I looks like the old IP is not freed?
Any idea why?
Best regards Martin
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hello @zmaier,
Thanks for reporting this feedback to the TP-Link community!
The current mechanism of DHCP Reservation is that the router will not take the initiative to release the IP address, you may reboot the router manually or release the original IP address on the original PC.
I've recorded this request and will report it to the developer team for evaluation.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Virgo : Ok, i haven't done the most obvious thing, rebooting the router.
No it works, the old IP is released. Still i think this is not how it should be?
- Copy Link
- Report Inappropriate Content
@zmaier I had the exact same problem. I had removed the old device from the list of reserved IP addresses and when I assigned the same IP address to the new device it said "Succeeded!" but the new device would never get the correct IP.
Thanks to this thread I tried rebooting the router (boy does that take long! Several minutes for booting a simple Linux machine??) and there we go: the new device eventually got the IP.
So there is obviously a bug which results in the DHCP server not releasing the fixed IP.
Considering that the very idea of fixed IPs is that you can control them, this bug defeats the very purpose of fixed IPs.
- Copy Link
- Report Inappropriate Content
I don't think it is an issue, the DHCP lease expired needs some time, and you can change the lease time as below:
- Copy Link
- Report Inappropriate Content
@Virgo : That's not the case. Still days after deleting the reservation, the ip is not released. So the lease time is definitely elapsed.
- Copy Link
- Report Inappropriate Content
Hello @zmaier,
Thanks for reporting this feedback to the TP-Link community!
The current mechanism of DHCP Reservation is that the router will not take the initiative to release the IP address, you may reboot the router manually or release the original IP address on the original PC.
I've recorded this request and will report it to the developer team for evaluation.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 1626
Replies: 6