@Sunshine  Hello Sunshine,

Please allow me to ask a few more questions related to EasyMesh/Ethernet backhaul:

1) main router is the EasyMesh controller. When connecting satellite routers, can I connect them as a daisy chain configuration or do they need to be in star topology?

I ask because TP-Link describes the following: " There are three different components in a mesh WiFi network:
Controller: Every EasyMesh network must have one. All agents are connected to it (including through indirect connections). " - https://www.tp-link.com/en/blog/288/

keep in mind there are several users like me that want to have 1 main router and 3-7 satellite routers, all connected via Ethernet backhaul. 

2) will this configuration work?

I have a main router setup as EasyMesh and being the controller (AX72 v1), from LAN port#1 I am connecting TP-Link switch TL-SG105, and from the switch I connect to 3 x AX53 V1 routers as satellite; AX72 LAN ports #2 through #4 connect to 3 x AX53 V1. Totaling 6 satellites. All connections via CAT6 cable for Ethernet backhaul. 
 

 Will EasyMesh be established? What is the controller's limit for maximum number of EasyMesh satellite routers?

Thank you, Eddie. 

I have a question:

If I have a C80 as main router and I plan to add an ax53 as a Satelite router, will the extra (AX) features work on the ax53?
I'm wondering because after adding it in easy mesh, I won't be able to access the ax53's admin page to turn on those features and I don't know what is the status of these features after the recommended factory reset on it.

Why I want to choose the C80 as main router is because its location next to the ISP's modem is where there is no need for as many connected devices as the other location where I want to install the ax53 (for that exact purpose).

  @Sunshine Good afternoon Sunshine,

Hope all is well. I was waiting for Archer AX53 V2 to release the official firmware, as using the BETA version Archer_AX53_V1_1.2.4_Build_20240206 I found instability with EasyMesh Ethernet Backhaul.

Today I decided to run the upgrades, as the official firmware was released (Archer AX53(US)_V1_240509). Ran the EasyMesh setup as per TP-Link website. Once finished, these 2 Archer AX53 were wirelessly connected as ethernet backhaul.

My topology:

Archer AX72 V1 as main.

2 CAT6 network cables from Archer AX72 LANs 1 and 2 connecting directly to Archer AX53 LAN ports.

Once the CAT6 cables are connected, I continue to see in Archer AX72 that the Archers AX53 are wirelessly connected. Hence the ethernet backhaul is not in place!

Clearly is something broken in the firmware, either in AX72 or AX53. Please could you contact support and find out how can they troubleshoot and fix this bug?

Sincerely,

Eddie.

Sunshine wrote

Eddie_G_Kibel wrote

  @Sunshine  Hello Sunshine,

 

Please allow me to ask a few more questions related to EasyMesh/Ethernet backhaul:

1) main router is the EasyMesh controller. When connecting satellite routers, can I connect them as a daisy chain configuration or do they need to be in star topology?

I ask because TP-Link describes the following: " There are three different components in a mesh WiFi network:
Controller: Every EasyMesh network must have one. All agents are connected to it (including through indirect connections). " - https://www.tp-link.com/en/blog/288/

 

keep in mind there are several users like me that want to have 1 main router and 3-7 satellite routers, all connected via Ethernet backhaul. 

 

2) will this configuration work?

 

I have a main router setup as EasyMesh and being the controller (AX72 v1), from LAN port#1 I am connecting TP-Link switch TL-SG105, and from the switch I connect to 3 x AX53 V1 routers as satellite; AX72 LAN ports #2 through #4 connect to 3 x AX53 V1. Totaling 6 satellites. All connections via CAT6 cable for Ethernet backhaul. 
 

 Will EasyMesh be established? What is the controller's limit for maximum number of EasyMesh satellite routers?

 

Thank you, Eddie. 

 

 

  @Eddie_G_Kibel 

 

Hi,

1. Daisy-chaining them can be effective especially when you have the option to connect the routers using Ethernet cables. If you have to use WiFi Backhaul, for optimal performance, it is recommended to limit the number of hops, which is no more than two hops, such as the main router )))((( satellite 1)))((( satellite 2.

2. For EasyMesh Ethernet backhaul or hybrid networks with both Ethernet and Wi-Fi backhaul, there is theoretically no limit to the number of units that can be added. However, we still recommend up to 6 units for better experience and performance. Considering your configuration with 7 units in total, it is worth a try. The topology you have set up is acceptable, but it's important to keep in mind that exceeding the recommended limit of 6 units may impact the overall performance and user experience.

 

By the way, AX53 V1 official firmware doesn't support Ethernet Backhaul yet, you could check the device list here and as you can see there is a beta firmware for AX53 V1: EasyMesh Routers Support Building a EasyMesh Network via Ethernet Backhaul NOW

  @Sunshine, How to confirm whether Ethernet Backhaul is working or not? 

I have successfuly configured Ethernet Backhaul beetween two C6 v4.0 router, but in Connection column I still see a WiFi icon instead an Ethernet one. Both routers have updated firmware. What can be wrong?  

Hi  @fmika 

May I know if your network topology diagram is as follows:

Cable modem—C6 V4 —C6  V4 )))((( client devices

(Note: — stands for wired connection,)))((( stands for wireless connection )

Please double check the hardware version of your routers, confirm it is V4 not V2 for Easymesh network.

Did you refer to the FAQ to set up Ethernet Backhaul between routers?

Build an Ethernet Backhaul Using Two EasyMesh Routers

Please confirm both Archer C6’s firmware is up to date(Archer C6(EU)_V4_1.13.6 Build 240430)

Upgrade the Firmware on the TP-Link Wi-Fi Routers

In addition,how long is the Ethernet cable? Could you try a different Ethernet cable to test it?

Hi @Joseph-TP, 

thanks for your reply. In the meantime I verified Ethernet cables and network components and came to know that the problem was due the D-Link switch. After replacing it by the TP-Link switch the problem has been fixed and the right "LAN" icon is displayed. Works fine!   

 Hi @fmika 

Sounds good~ You did a great job~

Have a good weekend！