Early Access Archer AX55 V1 Supports Extending Guest Network via EasyMesh and Optimizing Performance in AP Mode
Hello Everyone,
We're excited to announce the release of the pre-release firmware for Archer AX55 V1. This update introduces support for extending the Guest Network via EasyMesh, implements EasyMesh R3 functionality (including DPP and encrypted communication), and optimizes performance in AP Mode. We encourage you to try out this version of firmware and take advantage of the new features and bug fixes. Your feedback and suggestions are greatly appreciated.
This Article Applies to:
Archer AX55 V1/1.6
New Features and Modifications:
1. Added Easymesh R2 Traffic Separation feature to support network traffic segmentation.
**This allows the satellite unit to extend the Guest Network via EasyMesh.
**Both the main router and satellite unit must support this feature.
2. Implemented Easymesh R3 functionality, including DPP (Device Provisioning Protocol) and encrypted communication.
Bugs Fixed:
1. Fixed an issue where switching the AX55 from Router mode to AP mode caused an EasyMesh UI inconsistency,
2. Fixed an issue where the AX55 in AP mode prevented clients connected to the Guest Network from obtaining an IP address.
Firmware Download:
Before the Upgrade
(1) Please be sure you have read the Beta Test Agreement before upgrading the pre-release firmware!
(2) For the sake of insurance, it's always recommended to save a copy of the router Backup Config file before upgrading or downgrading.
(3) This pre-release firmware for Archer AX55 V1 can be applied to all versions (EU/US/CA/TW//JP/etc).
(4) You may follow the guide to upgrade the firmware of your router. How to Upgrade the Firmware on the TP-Link Wi-Fi Routers.
Direct Firmware Download Link
| Archer AX55_V1 | Archer AX55_V1_1.3.5 Build 20241211 (Pre-release Firmware) |
Additional Information
As always, we value your feedback. If somehow you encounter an issue during or after the router firmware upgrade, it's suggested to comment below with the following info. Your input helps us continue improving and providing the best products and support.
- Provide a detailed network layout, including how the devices are connected, especially if there are EasyMesh satellite devices.
- Detailed issue description, and provide more information on the specific conditions that seem to trigger the problem.
Thank you for your continued support and for being part of our community.
Related Articles
Product List of Wi-Fi Routers that Support EasyMesh Ethernet Backhaul
What is EasyMesh and how does it work with TP-Link routers and extenders?
EasyMesh Is Available When Wi-Fi Routers Work in AP Mode as A Controller
How to Build an Ethernet Backhaul Using Two EasyMesh Routers
@Kevin_Z good news! 
This firmware has been available since January from the Canada webpage and it's official :P why you call it Pre-release Firmware?
https://www.tp-link.com/ca/support/download/archer-ax55/v1/#Firmware
ChrisBS wrote
This firmware has been available since January from the Canada webpage and it's official :P why you call it Pre-release Firmware?
https://www.tp-link.com/ca/support/download/archer-ax55/v1/#Firmware
@ChrisBS You're correct. Version 1.3.5 has been released for specific versions, such as CA and TW. However, it is not yet available for others. Therefore, we are providing a direct download link in the community and still call it a pre-release version.
Some website admins may not publish new firmware updates promptly, which can delay visibility.
However, for the Archer AX55(EU) V1 version 1.3.5, the delay is not the local admin's fault. This version has not yet been officially released from the cloud. We’re providing early access to users like you so you can upgrade and explore the new features.
So I installed this beta and all of my mesh devices appears offline - all blinking orange/green - not able to connect. I have AX55 as main, 3x AX23 as satelites, needless to say I had to drop interconnection cables from them quite long time ago, because it was not possible to establish reliable eth backhaul at all. (This time - after fw upgrade of main AX55 to beta - I tried interconnect it via cables .. but no LUCK again - whenever I plug cables in it starts to be super unstable and sometimes it reboots itself or even resets to factory defaults)
I have also one other AX55 in the shelf (unpowered for like a year), but I dont dare to add it to a mesh, because that makes the netwerk super unstable - I mean like everything reboots or is supper bussy all the time - network is barely usable and I feel like im not going throu this excercise with new beta with it at least for now..
To sum it up - with this beta software, I dont have any mesh at all .. prior installation, I had at least wireless mesh
2025-04-04 00:04:56 QoS INFO [14062] Service start
2025-04-04 00:04:00 NAT NOTICE [12043] The address 192.168.0.90 will be DMZ host
2025-04-04 00:04:00 UPnP INFO [16130] Service start
2025-04-04 00:03:57 NAT INFO [12043] DMZ enabled
2025-04-04 00:03:57 UPnP INFO [16130] Service stop
2025-04-04 00:03:55 QoS INFO [14062] Function enabled
2025-04-04 00:03:54 QoS INFO [14062] Service stop
2025-04-04 00:03:53 NAT NOTICE [12043] Port trigger created succeeded[trigger-port:554 trigger-protocol:all ex-port:1-65535 ex-protocol:all]
2025-04-04 00:03:52 NAT DEBUG [12043] Port triggering:trigger match 1-65535 and trigger relate 554
2025-04-04 00:03:43 NAT NOTICE [12043] Virtual server created succeeded[ex-port:1-65535 ip:192.168.0.90 in-port:8971 protocol:all]
2025-04-04 00:03:32 Remote Management INFO [14211] Service stop
2025-04-04 00:03:18 NAT INFO [12043] Initialization succeeded
2025-04-04 00:03:12 NAT INFO [12043] Initialization succeeded
2025-04-04 00:03:05 Led Controller INFO [1253] Start to run WAN1_ON
2025-04-04 00:03:05 Led Controller INFO [1253] Start to run WAN0_OFF
2025-04-04 00:03:05 Led Controller INFO [1253] Start to run LAN_ON
2025-04-04 00:02:57 DHCPC INFO [11882] receive ack from server with ip 192.168.2.17, options(serverid=192.168.2.1;lease=3600;subnet=255.255.255.0;router=192.168.2.1;dns=31.30.90.11 31.30.90.12;)
2025-04-04 00:02:57 DHCPC INFO [11882] send select request with options(cliid=01/a8:42:a1:xx:xx:xx:;reqip=192.168.2.17;serverid=192.168.2.1;)
2025-04-04 00:02:57 DHCPC INFO [11882] receive offer from server with ip 192.168.2.17, options(serverid=192.168.2.1;lease=2326;subnet=255.255.255.0;router=192.168.2.1;dns=31.30.90.11 31.30.90.12;)
2025-04-04 00:02:57 DHCPC INFO [11882] send discover with ip 0.0.0.0 and flags 80
2025-04-04 00:02:47 Led Controller INFO [1253] Start to run WAN1_OFF
2025-04-04 00:02:47 Led Controller INFO [1253] Start to run WAN0_ON
2025-04-04 00:02:47 Led Controller INFO [1253] Start to run LAN_ON
2025-04-03 23:41:43 DHCPC INFO [28751] receive ack from server with ip 192.168.2.17, options(serverid=192.168.2.1;lease=3600;subnet=255.255.255.0;router=192.168.2.1;dns=31.30.90.11 31.30.90.12;)
2025-04-03 23:41:43 DHCPC INFO [28751] send select request with