@Kevin_Z 

hey there, i'm trying to build an easymesh topology like this

XX530V (A) --Wired-- HX220 (B) -- Wireless -- HX220 (C)

But I have this problem, when I'm on A or B node range I can connect in no time and I still having connection if i move to range of C node, but, if i turn off my WiFi and turn it on in C range I can't get IP, the phone just wait for an IP until it says it can't connect.

I think there's some kind of DHCP problem but I can't do any kind of setup on the Agents Nodes becasue when they're setup like agents their config menu is so basic, it just let you check the network map and upgrade firmware or factory reset.

When I connect to the Agent through Aginet I see it says it is in router mode and not AP mode. So I think their DHCP it still on and that's the problem. Is there anything I can do to fix this? or is this topology not allowed for the protocol?

HX220 
Hardware version: v1.0 
Firmware Version: 0.17.0 2.0.0 v605f.0 Build 240923 Rel.23368n

XX530V2 
Hardware Version v2.0 00000000
Firmware Version Datecode2507281059
 

  @Kevin_Z 

Do you have a Archer AX55 V1 Pro 1.3.3 beta firmware version available? I have the 

I want to configure EasyMesh R2 AP Bind and Client Bind and I have the firmware version 1.3.1 Build 20240426 rel.31941(5553) for Archer AX55 Pro v1.0

Thanks!

Does latest firmware 1.4.3 Build 20250813 rel.63911 add support of mesh wi-fi for guest network to AX55 Pro v1 ?

In my setups it works as satellite with 2,5 GBs ethernet backhaul to AX73, everything fine but lack of extending guest wi-fi is really annoying.

Router: Tp-Link AX55 Pro V1
Firmware: 1.4.3 Build 20250813 rel.63911

  @Kevin_Z hey there! curious if the new EX521 has this ability or not, I was not able to find any information. I'd like to use it as a satellite with a XX530V V2. Thanks!

  @АлександрП2 

Hello! I want to inform everyone who wants to repeat my actions to create a home network 2.5 Gbit\s that it works great in this configuration. Good luck!

AleksandrP2 wrote

  @Кевин_З Hello! I have read all the pages of the conference and I have a question for you: I use Archer AX72 Pro v1.0 1.3.1 Build 20240426 rel.40133(4555) as the main router, I use the WAN/LAN 2.5 Gb/c port to connect the slave router, the slave router is Archer C80 v.1 1.13.15 Build 240812 Rel.53634n(4555), the network operates in EasyMesh with ethernet backhaul mode. The routers are connected by a 10 m long category 6 cable. I am going to buy and install a SWITCH TP-LINK TL-SG105-M2 next to the slave router, connect the network cable from the main router to the switch (it provides connections at a speed of 2.5 Gbps), and connect the slave router Archer C80 to one of the ports of the SWITCH TP-LINK TL-SG105-M2. Do you think that connecting the SWITCH TP-LINK TL-SG105-M2 will not disrupt the operation of EasyMesh with ethernet backhaul? Best regards, Alexander

Hello, @Kevin_Z, TP-Link development team and community,

I am writing from Brazil to commend you on the continuous improvements to the EasyMesh technology, especially the Ethernet Backhaul feature, which is extremely useful. I would like to report a specific behavior I have observed and suggest an improvement for future firmware versions.

Background and Scenario:

In Brazil, local regulations permit the use of channel 13 on the 2.4 GHz frequency. In the area where I live, there is a large number of neighboring Wi-Fi networks, and the vast majority operate on channels 1, 6, and 11. Channel 13 is rarely used, making it ideal for obtaining a cleaner, interference-free signal. 

With this in mind, I have configured my main router, an Archer C80, to operate on channel 13.

The Identified Issue:

I have observed that when using the EasyMesh network with Ethernet Backhaul, the satellite routers (three Archer C64 units) do not follow the main router's configuration. While the Archer C80 correctly broadcasts on channel 13, the Archer C64s, which are connected via wired backhaul, automatically operate on channel 11.

Interestingly, I ran a test: when I disable the Ethernet Backhaul and create a purely Wi-Fi-based EasyMesh network, the satellite routers and extenders respect the main router's setting and all operate correctly on channel 13, as expected. The issue seems to be specific to the wired backhaul implementation.

My Setup:

• Main Router: 1x Archer C80 (Hardware Version V2.20)
• Satellite Routers (via Ethernet Backhaul): 3x Archer C64 (Hardware Version V1)
• Extenders (via Wi-Fi): 2x RE200 (Hardware Version V5)
• Firmware: All devices are updated to the latest firmware version available on the official TP-Link website.
• Compatibility: All devices are EasyMesh compatible.

Request to the Developers:

I kindly request that the TP-Link development team investigate this issue. The ability to set a specific channel on the main router and have all network nodes—especially those connected via Ethernet Backhaul—adhere to that setting is crucial for optimizing network performance in environments with high Wi-Fi density.

Fixing this behavior would allow users in regions like mine to take full advantage of less congested channels, such as channel 13, resulting in a more stable and robust connection for the entire mesh system.

Thank you very much for your attention and for your excellent work in developing these products. I am confident that this improvement would benefit many users of the EasyMesh platform.

Sincerely,
Fernando Cardoso