TL-R605 v1.0 DHCP not working new update
TL-R605 v1.0 DHCP not working new update
I just updated to the new 1.1.1 firmware and I'm now having issues where DHCP isn't working properly. Certain devices will connect but others won't. I assume once the DHCP resevation is up they all won't work? With any devices I couildn't get working like my phone and PC I set a static IP on the device itsel and it started to work. Reserving an IP in OMADA doesn't work.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
With the help of tp-link support, I realized I had two clients with the same DHCP reservation. I removed one of the clients and then was able to upgrade my router to the latest 1.1.1 firmware successfully.
- Copy Link
- Report Inappropriate Content
@Frankfurts Rolled back to 1.0.1 and all good
- Copy Link
- Report Inappropriate Content
If you use DHCP to obtain an IP from router automatically, do those devices work normally? Those working devices have static IPs or dynamic IPs?
After configuring static IP, you can try to reboot the devices to refresh the IP addresses.
- Copy Link
- Report Inappropriate Content
Yes they usually work as soon as I reverted back to the old firmware they all started working again. The static IP workaround would only work if I set the static IP on the client itself.
I'll stay on the old firmware until the problems are sorted.
- Copy Link
- Report Inappropriate Content
I have had the same issue, same problems. Luckily I remembered the issue mentioned here... Did a rollback and everything is back to normal.
- Copy Link
- Report Inappropriate Content
Same problem. Did a firmware rollback for the router and dhcp works again
- Copy Link
- Report Inappropriate Content
Dear @Frankfurts, @Aberman, @RBL,
Frankfurts wrote
I just updated to the new 1.1.1 firmware and I'm now having issues where DHCP isn't working properly. Certain devices will connect but others won't. I assume once the DHCP resevation is up they all won't work? With any devices I couildn't get working like my phone and PC I set a static IP on the device itsel and it started to work. Reserving an IP in OMADA doesn't work.
The issue you are experiencing sounds unusual, I'd like to escalate your case to the TP-Link support team for further investigation.
They will reach you via your registered email address shortly, please pay attention to your email box later.
Once the issue is addressed or resolved, I'd encourage you to share it with the community.
Thank you so much for your cooperation and support!
- Copy Link
- Report Inappropriate Content
+1 for DHCP broken after upgrading to the 1.1.1 firmware.
The first thing I noticed after upgrade was the notice "The feature is available only when the gateway acts as the DHCP server." when trying to assign a static IP to a new client in the clients tab of Omada controller. Then I noticed an increasing number of clients without an IP as old leases expired and were unable to be renewed.
I have tried force provisioning the router again, various config changes to the DHCP section of the LAN setings which I can see are being applied as the router device status changes to "configuring" but still no luck getting a response to a DHCP request. I have also done a full factory reset of the router and re-adoption by Omada controller, but that didn't help either.
I'm unable to tell if the DHCP service is failing to start on the router, everything is very opaque behind the Omada controller. Direct access to the router logs/shell would be useful to try and debug.
I'll follow the advice above and rollback to previous version.
- Copy Link
- Report Inappropriate Content
With the help of tp-link support, I realized I had two clients with the same DHCP reservation. I removed one of the clients and then was able to upgrade my router to the latest 1.1.1 firmware successfully.
- Copy Link
- Report Inappropriate Content
@Aberman Yes I had the same issue I haven't had a chance to change it yet and try the update. It is odd that it works on the old firmware.
An event in the logs would be helpful to tell us why DHCP isn't working. I'm glad it solved your issue and hopefully it fixes mine too
- Copy Link
- Report Inappropriate Content
Thank you,
I had the same problem with address reservation. V1.1.1 did not work correctly. Some of my clients didn't get an ip-adres anymore, so I downgraded to v1.0.1 and IP reservation worked fine again.
In omada configuration (Insight, known clients), I found a double reservation as well.
I removed the wrong reservation and I upgraded to v1.1.1 again
Now IP reservation worked perfectly bas it has to :)
Thanks to your post.
Regards,
Alex
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 3717
Replies: 13
Voters 0
No one has voted for it yet.