Home Network Community > Wi-Fi Routers > Archer AX55 V1 Supports Extending Guest Network via EasyMesh and Optimizing Performance in AP Mode
< Wi-Fi Routers

Early Access Archer AX55 V1 Supports Extending Guest Network via EasyMesh and Optimizing Performance in AP Mode

12

Early Access Archer AX55 V1 Supports Extending Guest Network via EasyMesh and Optimizing Performance in AP Mode

16 Reply
Re:Archer AX55 V1 Supports Extending Guest Network via EasyMesh and Optimizing Performance in AP Mode
2 weeks ago

  @Kevin_Z 

 

this still doesn't fix mine, I attempt a download of 10GB video file and the router crashes several times during the process. can't ping the router for 6 seconds everytime.

after 6 seconds it continues to download until it crashes again. Cannot download 2.5GB of 1 video file before it crashes.

  0  
  0  
#13
Options
Re:Archer AX55 V1 Supports Extending Guest Network via EasyMesh and Optimizing Performance in AP Mode
2 weeks ago

  @saiph do you have any usb storage device connected? When the 128gb usb drive I used was full, the router crashed. I removed it and disabled the storage sharing feature and now it does not crash anymore. Just giving an idea, maybe you do not have any and it is caused by another thing

  0  
  0  
#14
Options
Re:Archer AX55 V1 Supports Extending Guest Network via EasyMesh and Optimizing Performance in AP Mode
2 weeks ago - last edited 2 weeks ago

  @persano nothing connected to it but 3 ethernet cables

its 100% firmware issue as when i updated it to the newest one it happened less.

now the router fails about 25% into a download instead of every like 2% 

 

same issue as the user above

can't ping the router for 6 seconds. literally only 6 seconds everytime. after 6 seconds of timing out transpires it reconects. 

  0  
  0  
#15
Options
Re:Archer AX55 V1 Supports Extending Guest Network via EasyMesh and Optimizing Performance in AP Mode
2 weeks ago

Hi @saiph,

Thank you for reporting your issue to our community.

 

May I know if your network topology diagram is as follows:
Cable modem—router )))((( client devices
(Note: — stands for wired connection,)))((( stands for wireless connection )

 

In addition to Archer AX55, do you have other network devices? For example, other routers, switches, etc. What are the client devices in the system?
Are you downloading files through a wired network or a wireless network? How much memory do these files usually take?

 

The video file size you mentioned is 10G, which may be due to excessive load caused by downloading large files. Please compare whether the same problem occurs with small files?
In addition, the following reasons may also cause it:
1. The router is overheated, please pay attention to cooling the router;
2. The power supply is insufficient, please replace the wall socket;
3. Temporarily disable QoS, firewall, UPnP and other functions to test whether the crash frequency is reduced;

 

Check Out the Latest Posts: Connect TP-Link Archer BE550 to Germany's DS-Lite (Dual Stack Lite) Internet via WAN Archer GE550 - BE9300 Tri-Band Wi-Fi 7 Gaming Router Archer BE550 New Firmware Added Support for EasyMesh in AP Mode, DoH&DoT, ECO Mode, and More Archer AX90 New Firmware Added Support for EasyMesh and Ethernet Backhaul
  0  
  0  
#16
Options
Re:Archer AX55 V1 Supports Extending Guest Network via EasyMesh and Optimizing Performance in AP Mode
a week ago

 

Czmazel wrote

  @Kevin_Z 

 

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

 

@Czmazel Apologize for my late response.

 

Have you tried to reset the AX55 to factory defaults and re-add the 3*AX23 to the network via EasyMesh?

Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: Connect TP-Link Archer BE550 to Germany's DS-Lite (Dual Stack Lite) Internet via WAN Enhance Your Experience: Archer BE550's New Pre-Release Firmware Boosts Stability and Performance! Archer GE550 - BE9300 Tri-Band Wi-Fi 7 Gaming Router Archer AX90 New Firmware Added Support for EasyMesh and Ethernet Backhaul If you found a post or response helpful, please click Helpful (arrow pointing upward icon). If you are the author of a topic, remember to mark a helpful reply as the "Recommended Solution" (star icon) so that others can benefit from it.
  0  
  0  
#17
Options
Re:Archer AX55 V1 Supports Extending Guest Network via EasyMesh and Optimizing Performance in AP Mode
Monday

Kevin_Z wrote

 

Coriander wrote

  @Kevin_Z  just the Guest network or also the IoT network?

 

@Coriander That's right. With this new firmware, the satellite AX55 can also extend the main AX55's Guest Network.

 

@Kevin_Z I understand that the Guest network can be extended now, I was asking about the IoT network.

 

Kevin_Z wrote

Regarding Access Control, are you indicating that the settings cannot be synchronized from the main AX55 to the satellite? Please provide more details about the issue so we can investigate further. Thank you.

 

See my post from last year for more details: https://community.tp-link.com/en/home/forum/topic/675314

I haven't tried again since then (I think), but I doubt that anything has changed. At least there's nothing in the release notes that suggests otherwise.

 

My network is reasonably stable at the moment, so I don't really want to play around with the settings. Over the last 2 years I've spent way too much time trying to get the WiFi working again after trying a new version or changing some innocent-looking settings.

Actually I don't think that access control over EasyMesh was ever working and I remember that there were other users in this forum complaining about it too.

Even without any more details from my side this issue shouldn't be too hard to investigate on your side. There's no need to always place the burden on the users.

 

Kevin_Z wrote

As far as I can confirm, EasyMesh does not require support for WPA/WPA2-Enterprise, and AX55 is not planned to support it through EasyMesh.


The AX55 router supports WPA/WPA2-Enterprise and it also supports EasyMesh.
The whole point of EasyMesh is to have a single point to configure all WiFi settings. This should apply to all WiFi settings, no matter what's strictly required by the protocol.

 

But the worst part is, that those settings are just silently ignored. In the case of access control settings, there's a high chance that this goes unnoticed for a long time.

If it works on the main router, there's no reason to assume that it doesn't work for the satellite units. Most users will not explicitly test each satellite separately, if they do test it at all (which shouldn't even be necessary).

 

And if WPA/WPA2-Enterprise is configured on the main router, all devices connected to the satellite are silently exposed to an unsecured WiFi network. Granted, this is much easier to notice than the access control issue. But still, something like this should never happen under any circumstances.

 

I think it's reasonable to expect that two features of a product can be used in conjunction, unless there is a valid reason that it cannot work.

I understand that some features were missing in the beginning. I also understand that EasyMesh is a vendor-agnostic standard and different devices support different features.

But I'm using two identical AX55 devices with the exact same features and it's now 2 years since EasyMesh was introduced. Yet the implementation is still incomplete and progress is extremely slow.

 

Don't get me wrong, I very much appreciate that TP-Link made the effort to support an open protocol instead of yet another proprietary solution. That's why I bought the devices in the first place. But at some point they just have to work properly.

Now I'm starting to look more at "prosumer" grade access points, despite the vendor lock-in. But after this experience it probably won't be anything from TP-Link.

  3  
  3  
#18
Options
12

Tags

Firmware Update EasyMesh Official Guest Network
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.