[SOLVED] AX53 causes broadcast storm in EasyMesh setup after reboot

[SOLVED] AX53 causes broadcast storm in EasyMesh setup after reboot

[SOLVED] AX53 causes broadcast storm in EasyMesh setup after reboot
[SOLVED] AX53 causes broadcast storm in EasyMesh setup after reboot
2025-07-25 21:13:14 - last edited 2025-07-27 19:11:53
Model: Archer AX53  
Hardware Version: V2
Firmware Version: Archer AX53(EU)_V2_1.0.4 Build 20240306

I have an EasyMesh setup with:

  • AX53 (main router, EasyMesh master)

  • AX23 and C6 (mesh clients, default settings, wired backhaul)

  • DHCP and NAT disabled on the AX53

  • AX53 is connected via LAN port to a TP-Link switch (TL-SG1008P), which connects to my ISP router (Technicolor FGA2235)

DHCP is enabled only on the ISP router, and all devices have fixed IPs.


Issue:
After rebooting the AX53 (e.g., power loss), the entire network becomes unusable:

  • Massive traffic flood (all switch and ISP router LEDs blink rapidly)

  • Clients lose connectivity

  • Problem only stops when the AX53 is powered off

  • In AP mode, the problem disappears — but EasyMesh is disabled
     

Logs show the AX53 spamming ARP requests at extreme rate (6000+/minute), e.g.:

16:30:44.424126 ARP, Request who-has 192.168.1.43 tell 192.168.1.30, length 46
(repeated ~100 times per second)

 

Questions:

  1. Is this configuration officially supported (AX53 in router mode, LAN-only, no DHCP/NAT)?

  2. Why does rebooting the AX53 cause a broadcast storm?
     

Network diagram is attached.
Thank you!

File:
infrastructure.pngDownload
https://feriman.com
  0      
  0      
#1
Options
1 Accepted Solution
Re:AX53 causes broadcast storm in EasyMesh setup after reboot-Solution
2025-07-27 19:11:29 - last edited 2025-07-27 19:11:35

@terziyski 

 

Thanks for the link! I have a C6 v4 router, which supports EasyMesh in AP mode. I upgraded the firmware to the latest beta version and set the router up in AP mode and as an EasyMesh master.

 

The AX23 and AX53 have been reset, so they are satellite EasyMesh devices now. The DCHP function stayed at Technicolor device.

 

I tested it by turning the EasyMesh master (C6 v4) off and on again, and simulating a power outage by turning all the routers off and on again at the same time.

This worked in all cases.

 

Thank you for the tip! It solved the issue!

https://feriman.com
Recommended Solution
  0  
  0  
#3
Options
2 Reply
Re:AX53 causes broadcast storm in EasyMesh setup after reboot
2025-07-27 12:58:53

  @Feriman 

 

This probably happens because you use AX53 in router mode and you have disabled its DHCP and NAT features to use it as an AP.

According to your topology diagram AX53 should be used in AP mode as an Easymesh controller.

But since this feature is supported only on AX53 v1 for now (details), try connecting the satellite devices directly to your AX53 and check how it goes.

If this still causes a broadcast storm try splitting your DHCP pool between the ISP router and AX53 (you should enable DHCP and NAT features on AX53 in this case).

Another approach would be to use your ISP router in bridge mode, your AX53 as a main router (DHCP and NAT enabled) and all other  devices connected to the switch.

If this was helpful click on the arrow pointing upward to make it blue. If this solves your issue, click the star to make it blue and mark the post as a "Recommended Solution".
  1  
  1  
#2
Options
Re:AX53 causes broadcast storm in EasyMesh setup after reboot-Solution
2025-07-27 19:11:29 - last edited 2025-07-27 19:11:35

@terziyski 

 

Thanks for the link! I have a C6 v4 router, which supports EasyMesh in AP mode. I upgraded the firmware to the latest beta version and set the router up in AP mode and as an EasyMesh master.

 

The AX23 and AX53 have been reset, so they are satellite EasyMesh devices now. The DCHP function stayed at Technicolor device.

 

I tested it by turning the EasyMesh master (C6 v4) off and on again, and simulating a power outage by turning all the routers off and on again at the same time.

This worked in all cases.

 

Thank you for the tip! It solved the issue!

https://feriman.com
Recommended Solution
  0  
  0  
#3
Options