@Sunshine 

I appreciate all of you replying to my post.

It seems that one of the major issues with this new firmware release is that there is a problem with

how the AX55's DCHP server manages assigning IP addresses to network devices.

As an experiment before downgrading the firmware, I changed the default DHCP Address Lease Time

from 120 minutes to 2880 minutes (48 hours maximum allowed), and the problem with disconnects, and

failure to connect/reconnect new wireless devices, went away.

Everything has been completely stable so far for the past 14 hours. Will the problem return in 48 hours?

I don't know. But right now I can connect, disconnect, and reconnect wireless devices without any

problems. So, it is interesting.

I will keep you posted. Thanks again

  @Yellowjacket I had mine set to 2880 and the issue occurs...about 1 day after reboot...which is the default re-lease time for Windows if the lease is set to 2 days.

  @AdamPfromMN 

That's what I was afraid of. I know that halfway through the 48 hour lease cycle, DHCP is going

to try to renew the IP that was originally assigned. That's probably where the failure is occurring,

due to the bug introduced by the new firmware. Devices can be assigned an IP initially, but apparently,

that IP cannot be renewed, nor can a new one be assigned. I wonder how many AX55 routers

have been affected by this issue?

  @Sunshine 

1.Do both your wireless and wired devices experience this issue, or is it only specific devices that are affected? Please provide the models of the affected devices

I only have wireless devices associated with my AX55, no wired devices. The issue affects all of my wireless network devices.

2.How often does the problem occur, and how long does it last? How do you restore the connection?

The problem begins to occur at exactly one half of the DHCP Lease Time. For example, I currently have it set for 2880 seconds (48 hours).

The problem begins to occur exactly 24 hours after a reboot. The connections can be restored by rebooting the router, or resetting

the DHCP Lease Time to a different value.

3.When the issue occurs, do the affected devices automatically disconnect from the Wi-Fi?

Is the issue that devices cannot reconnect, or that devices are connected but have no internet access?

When the issue occurs, NO NEW DEVICES can connect to the router. Also, if a connected device

is powered off, and then powered on again, it cannot reconnect to the router. As long as a device remains

powrered on, and has already been assigned an IP address, it can maintain connectivity.

Sunshine: Are you saying that your recommended solution to this problem is to install the beta firmware

Archer_AX55_V1_1.2.6 Build_20231106 rather than downgrade to th prior firmware version as some others have done?

Please advise. Thank you!

  @Sunshine 

Hi Sunshine:

Do you want me to update to the current beta firmware version?

Public Beta for Archer AX55 V1 Supports EasyMesh Ethernet Backhaul, DoH&DoT, ECO Mode and More.

Thank you!

  @minion-me I'm experiencing the exact same problem.  Radom clients (I.e., Mac, LG tvs, iPhones, FireTV, etc...) lose WiFi connection. Not at the same time.  ISP connection is solid...no problem there.  Only way to clear seems to be restarting WiFi router. Problem started a couple weeks ago after firmware update to (1.2.5, build 20231025, rel 50143.  Does to-link have a fix in the works..?

  @Ping808 

You can try the beta of the next firmware version here: 

Public Beta for Archer AX55 V1 Supports EasyMesh Ethernet Backhaul, DoH&DoT, ECO Mode and More

Or, rollback to the prior version firmware here:

 https://www.tp-link.com/us/support/download/archer-ax55/v1/#Firmware

  @Sunshine same issues, glad found this post. Wired and wireless devices are dropping connections, getting 169.254. IP address using DHCP. Happening several times a day and the loss can last a couple minutes to 30 minutes before pulling a real IP.

 I hope a resolution is found soon, my wife is about to throw the router and me out the door :)