EasyMesh prefers wireless backhaul

EasyMesh prefers wireless backhaul

EasyMesh prefers wireless backhaul
EasyMesh prefers wireless backhaul
2025-08-05 04:09:16
Hardware Version:
Firmware Version:

Hello!

 

I have an EasyMesh system made up of three Tp_Link routers.

BE800 (main)

   |

(switch)

   |

(switch)

|           |

AX55   BE9300

(satellites)

 

Everything's on the mast recent (as of right now) firmware.

 

Switches are working fine, and usually everything is well, but every time one of the satellite routers (particularly the AX55) reboots, it insists on using WiFi for the backhaul connection. The other satellite then reconnects to AX55 over the Ethernet. Sometimes both satellites connect over WiFi, create a loop between the two switches, and knock half the network offline. A few reboots of the satellite(s) usually fixes things but why do they insist on a WiFi backhaul after reboot? Both satellites are configured for wired backhaul, it works just fine at the time one reboots (usually because kids turn on too many things in one room and the circuit breaker trips)? Switches, bith on big fat UPS's are most definitely online at the time.

 

Thanks!

  0      
  0      
#1
Options
4 Reply
Re:EasyMesh prefers wireless backhaul
2025-08-06 08:29:41

Hello @BorisM ,

Welcome to our community.

 

What are the models of the switches? Are there two switches between the main router and the satellite routers?
If so, please remove one switch for comparison. In other words, connect the satellite routers directly to the first switch.

 

Are both the Archer BE9300 and Archer AX55 connected directly to the second switch? Or is the Archer BE9300 connected to the Archer AX55?


When setting up Ethernet backhaul, please confirm that the main router is connected to the LAN ports of the satellite routers.

 

If there are other devices on the network that may cause significant interference, please temporarily remove them for comparison.

 

  0  
  0  
#2
Options
Re:EasyMesh prefers wireless backhaul
2025-08-06 18:48:33

  @Joseph-TP thank you!

 

Switches are ZyXEL XGS1250-12, both are the same, and yes, there are two switches between main and satellite nodes. Both satellites are plugged into the switch #2 while main is in switch #1.

 

Distasnce between switches makes bypassing one difficult without just unplugging everything and bringing satellites up to the same room as where the main is.

 

What do you mean nby "significant interference"? Switches are connected with 10Gb fiber, network activity appears normal, and there isn't really anything at least on the switch#2 side that coupld possibly saturate the link to switch#1.

 

As it does start working randomly after some reboots, with nothing else being changed, this does not appear to be a persistent issue on the network itself, but rather however EasyMesh decides which connection to use.

 

I believe there are already feature request to allow the user to specify to only use Ethernet backhaul, so I would add my vote to those.

 

Thanks!

  0  
  0  
#3
Options
Re:EasyMesh prefers wireless backhaul
2025-08-07 08:11:19

Hello@BorisM,

Thanks for getting back to me.

 

We recommend sending an email to support.usa@tp-link.com with the following information:

 

  • Description: 

​​​​​​​When the satellite router AX55 restarts, it automatically switches to WiFi backhaul, affecting other satellites that will reconnect to the AX55 via Ethernet.

Switch model is ZyXEL XGS1250-12, both satellite routers are connected to the second switch.
 

Network topology is as below:

BE800 (main)

   |

(switch)

   |

(switch)

|           |

AX55   BE9300

(satellites)

  0  
  0  
#4
Options
Re:EasyMesh prefers wireless backhaul
2025-08-07 23:07:01

  @Joseph-TP 

Thank you! I have emailed it.

  0  
  0  
#5
Options