AX55 / AX3000 v1.0 DHCP Issues with New Firmware 1.2.5 Build 20231025 rel.50143(5553)
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
UGH. Buggy firmware again for the AX55 / AX3000. This is the second time this year that buggy firmware has been put out with the first being a full lockup of the device that required reboot every 12-36 hours or so.
This time around with the 1.2.5 firmware with the date of 20231025, my router goes into a state of no longer being able to hand out IP addresses. The device has been up for 1 day, 22 hours and 28 minutes. Below is what my log shows and is around when the issue started today...~30 minutes from there.
2023-11-28 06:12:22 DHCPC INFO [15059] send select request with options(cliid=01/b4:b0:24:78:34:11:;)
2023-11-28 06:12:22 DHCPC INFO [15059] 1/2 lease passed, enter renewing state
There are only a few DHCP clients listed in the table, unlike before. My lease time is 2880 minutes.
After reboot, all seems to function again for a day or so. Odd to see the below in the logs with Time...router starts up with the time being set to the release date of this firmware then adjusts once it sync's with my time server.
2023-11-28 07:50:32 Time Settings INFO [26616] Service restart
2023-11-28 07:49:32 Time Settings INFO [26238] Service restart
2023-11-28 07:47:14 Led Controller INFO [1108] Start to run WAN1_ON
2023-11-28 07:47:14 Led Controller INFO [1108] Start to run WAN0_OFF
2023-11-28 07:47:14 Led Controller INFO [1108] Start to run LAN_ON
2023-10-25 00:02:08 UPnP INFO [17495] Service stop
2023-10-25 00:02:03 Remote Management INFO [16672] Service stop
2023-10-25 00:01:56 NAT INFO [14693] IPSEC ALG enabled
2023-10-25 00:01:56 NAT INFO [14693] L2TP ALG enabled
2023-10-25 00:01:56 NAT INFO [14693] PPTP ALG enabled
tp-link team, I again need to roll my firmware back to the previous release. Am I able to do this myself now or do I need assistance again?
Please let me know ASAP as this issue started when I installed the latest firmware this past weekend. No other changes have been made to my network or devices outside of adding 2 new Amazon Echo Shows, which obviously should not be an issue.
I've now set my router to reboot daily to try to work around this issue, but have no idea as to if it will work yet.
