Both of the ax53’s couldn’t connect, now it happened again, I had update for the main router (ax72) and after the router was updated successfully, both of the ax53 didn’t connect to the internet, the internet light turned orange than flashed orange and then turned off on both of them, only after resetting the whole network it got fixed…

here is the log:

2024-08-09 11:21:38 Led Controller INFO [1126] Start to run WAN1_ON

2024-08-09 11:21:38 Led Controller INFO [1126] Start to run WAN0_OFF

2024-08-09 11:21:38 Led Controller INFO [1126] Start to run LAN_ON

2024-08-09 11:21:07 Led Controller INFO [1126] Start to run WAN1_ON

2024-08-09 11:21:07 Led Controller INFO [1126] Start to run WAN0_OFF

2024-08-09 11:21:07 Led Controller INFO [1126] Start to run LAN_ON

2024-08-09 11:21:00 UPnP INFO [18937] Service start

2024-08-09 11:21:00 UPnP INFO [18937] Service stop

2024-08-09 11:20:59 NAT INFO [17075] IPSEC ALG enabled

2024-08-09 11:20:59 NAT INFO [17075] L2TP ALG enabled

2024-08-09 11:20:59 NAT INFO [17075] PPTP ALG enabled

2024-08-09 11:20:59 NAT INFO [17075] SIP ALG enabled

2024-08-09 11:20:59 NAT INFO [17075] RTSP ALG enabled

2024-08-09 11:20:59 NAT INFO [17075] H323 ALG enabled

2024-08-09 11:20:59 NAT INFO [17075] TFTP ALG enabled

2024-08-09 11:20:59 NAT INFO [17075] FTP ALG enabled

2024-08-09 11:20:56 Remote Management INFO [18197] Service stop

2024-08-09 11:20:55 QoS INFO [17746] Service start

2024-08-09 11:20:55 QoS INFO [17746] Function disabled

2024-08-09 11:20:55 QoS INFO [17746] Service stop

2024-08-09 11:20:54 NAT INFO [17075] Initialization succeeded

2024-08-09 11:20:53 NAT INFO [17075] Initialization succeeded

  @IceScream up, please help!

  @IceScream 

Hi 

I had very similar experience to yourself. 

I had 3 AX72 running in easymesh wired back haul. 

I originally had it as 1xmain and 2x AP. 

When the update come out for the easy  mesh I left it a few months as wanted to see if there was any bugs before trying it. 

Skip few months and thought I'd give it a try 

In my case it was a huge mistake from the start. 

Constant disconnections, crashes ect, I've made posts showing the issues I had. 

Some of the things I noticed that would instantly cause a whole network crash was if I unplugged a ethernet either on the main unit or plugged a ethernet in anywhere in on the network. 

If I tried adjusting Any settings or even editing a name on the client list would send my easymesh setup into a complete meltdown resulting in complete reboots of all 3 units to get it working again.  

I did notice that my cpu load/memory was constantly if not always maxed out even when my network had only me using the network at home alone and just using my phone watching YouTube. 

After a few months of trying to fault find and persevere with help of support team ( not being able to find out why ) I went back to good old faithful 1x main 2x AP and been rock solid since and my cpu load ect  hardly reaching max even with everyone online streaming ect at same time. 

Not sure if having easymesh is causing too much cpu load ect or what ever the issue is but I won't be using it again anytime soon. 

  @Basboi85 

Hey, thanks for sharing, but I don’t really understand what you’re saying, I mean easy mesh is the feature that lets you set the other routers as AP’s connected with ethernet backhaul, so how you do it without easymesh? I’m confused.

  @IceScream 

 Basically it's the same but it was the way it was done before easy mesh was released where the satellite/s acted just as a access point and your main acted as the master doing all the dhcp ect where you can control say your cut off times ect. 

In the settings on the Web gui or on the tether app you can put your satellite routers in Access Point Mode, alot of people can't do it as they don't have ethernet between the satellite routers and main router and can benefit from wireless easy mesh. 

Its Pretty much the same as what the satellite router you have at the moment in easy mesh is doing but you have slightly more control over it. 

There is as always downsides when running in this way as (others may add there views when it comes to this way of set up) to roaming between the units when it comes to transferring to the stronger signal with some devices but on the flip side as far as I'm aware you can still be able to adjust some basic  settings on your satellite routers unlike when they are in easymesh mode

( turn guest wifi on and iot network on if important to you and change the channel the wifi is transmitting on and the transmit power so devices will want to swap to the different units more.)

In the Web GUI it's under advanced > system> operation mode. 

In the tether app  open the main menu scroll down and it says operation mode and then it gives you option to be a main normal router or access point. 

Been a while since I set mine up but off top of my head I think I set my satellite up as normal router but gave it the same log in settings as the main unit (admin log in credentials for when I'm attached to what ever unit and want to log in to the Web GUI for that device as well as the same ssid and password for the main network aswell as for the guest and iot network to save trying to remember loads of different passwords for each unit)

and then went into the settings and then turned on AP mode. 

I also turned my transmit power down on all my units to I think medium so it helped devices want to transfer/roam between the stronger signal from the closer unit. 

Obv this is my preferred way and I'm in no way encouraging you to to go the same it's maybe another option for you to try becuase I believe you said in your post your running a wired backhaul with your satellites  just how I have my network setup and it's working for me