Ethernet backhaul between ax55 and c80

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Ethernet backhaul between ax55 and c80

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Ethernet backhaul between ax55 and c80
Ethernet backhaul between ax55 and c80
2024-05-30 20:00:57 - last edited 2024-06-01 14:12:37
Model: Archer AX55  
Hardware Version: V1
Firmware Version: Last

Hi, i try to connect two easymesh routers, an ax55 and a c80 but easymesh only start by wireless, any option to change it to ethernet 

 

Any Idea?

 

Regards 

 

Mat

  0      
  0      
#1
Options
1 Accepted Solution
Re:Ethernet backhaul between ax55 and c80-Solution
2024-06-01 14:09:12 - last edited 2024-06-01 14:12:37

  @Marvin_S i previously follow this

 

issue is fixed the archer ax55 v1 support backhaul with the new 1.3.2 firware 

 

with 1.2.6 firware was not working

 

thanks for your help it was just a firware issue

 

regards

Recommended Solution
  1  
  1  
#10
Options
9 Reply
Re:Ethernet backhaul between ax55 and c80
2024-05-30 20:48:44

  @Lespadon 

 

Hi,

 

It should switch to Ethernet backhaul automatically after an Ethernet cable has been connected between the two routers.

 

Is the connection made via a straight cable or is the connection made through a network switch of some sort?
 

  0  
  0  
#2
Options
Re:Ethernet backhaul between ax55 and c80
2024-05-30 21:08:56
Hi, Yes it's a straigh wired cable not throw a Switch, connexion stay AT wireless, i tried to add it as a satellite first, KO then i reset and Linked from l'an port on ax55 to lan port on c80, same end Both are UP to date with latest firmware available Regards
  0  
  0  
#3
Options
Re:Ethernet backhaul between ax55 and c80
2024-05-30 21:10:09
Thé ax55 became instable when connected with ethernet lan to lan, stable when unplugged
  0  
  0  
#4
Options
Re:Ethernet backhaul between ax55 and c80
2024-05-30 21:10:09
Thé ax55 became instable when connected with ethernet lan to lan, stable when unplugged
  0  
  0  
#5
Options
Re:Ethernet backhaul between ax55 and c80
2024-05-30 21:59:17

  @Lespadon 

 

That sounds like the problems people have had with EasyMesh routers that didn't support EasyMesh Ethernet backhaul.

 

So the AX55 V1 is running firmware verison 1.3.2 and the C80 has firmware version 1.13.2 (ow newer), right?
 

Have you tested whether it works any better if you plug the Ethernet cable in the WAN port of the C80?

  0  
  0  
#6
Options
Re:Ethernet backhaul between ax55 and c80
2024-05-30 22:20:48

  @woozle 

No the last firmware available in frznce is https://www.tp-link.com/fr/support/download/archer-ax55/v1/#Firmware is 1.26

 

i just tried the beta firmawre from https://community.tp-link.com/en/home/forum/topic/636954 and it works !!!

 

so the current frech firmware is out of date 

 

can i install us firmware on my ax55 v1 without issue? 

 

Regards

  0  
  0  
#7
Options
Re:Ethernet backhaul between ax55 and c80
2024-05-30 23:51:26

  @Lespadon 

IF you have AX55v1 you can install US firmware without problem: https://www.tp-link.com/us/support/download/archer-ax55/v1/#Firmware

 

BTW. When you update to newst firmware please check if USB stroge works good for you? If you able to send files and make new folders in stroage when you unselect one of subfolders :)

  0  
  0  
#8
Options
Re:Ethernet backhaul between ax55 and c80
2024-05-31 06:21:53

  @Lespadon 

 

Hi, thanks for posting question.

It is suggested to follow the troubleshooting tips in the FAQ and provide detailed feedback if the issue remains: What If I fail to establish EasyMesh network using TP-Link EasyMesh devices? Thank you.

  0  
  0  
#9
Options
Re:Ethernet backhaul between ax55 and c80-Solution
2024-06-01 14:09:12 - last edited 2024-06-01 14:12:37

  @Marvin_S i previously follow this

 

issue is fixed the archer ax55 v1 support backhaul with the new 1.3.2 firware 

 

with 1.2.6 firware was not working

 

thanks for your help it was just a firware issue

 

regards

Recommended Solution
  1  
  1  
#10
Options