Solution Solved-Archer AX73 V1&V2 might reboot automatically when working together with some Range Extenders
This Article Applies to:
Archer AX73 V2 with firmware version 1.0.11 Build 20230829 rel.37304
Archer AX73 V1 with firmware version 1.3.5
Phenomenon Description:
After upgrading to the firmware of AX73 that supports EasyMesh, some AX73 might reboot automatically when it is working with some models of Range Extender, such as RE650, RE605X v2, etc.
Workground:
Jul 18th, 2024 Update:
New official firmware for Archer AX73 V1&V2 has fixed the issue finally, please check for update on the web GUI or Tether App. Or you could also download it from TP-Link official website.
Archer AX73 V2 Firmware Download for Archer AX73_V2_1.1.0 Build 20240323
Archer AX73(US) Firmware Download for Archer AX73(US)_V1_1.3.6 Build 20240325
Archer AX73(EU) Firmware Download for Archer AX73(EU)_V1_1.3.6 Build 20240407
Update:
New official firmware for AX73 V2 has already been released, please check for update on the web GUI or Tether App. Or you could also download Archer AX73_V2_1.0.12 Build 20231023 manually from TP-Link official website:
Firmware Download for Archer AX73 V2
For Archer AX73 V1, please try the beta firmware below:
US version: Archer_AX73(US)_V1_1.3.5_Build_20231213
EU version: Archer_AX73(EU)_V1_1.3.5_Build_20231213
Note: Please be sure you have read the Terms and Conditions for TP-Link Beta Firmware before proceeding.
If there is any further issue after installing the above newest firmware, please leave comments on this thread and provide the following information:
1. Detailed problem description and your whole network topology
2. Your router’s configuration file and login password, you could save it on Advanced->System Tools->Backup&Restore->Click Backup
3. Model no., hardware and firmware version of your router and also the range extenders
4. How many client devices are usually connected and what are they.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Thanks a lot for all the feedbacks, glad to hear that the problem has been resolved.
- Copy Link
- Report Inappropriate Content
As an update, I have now had a solid internet connection for over 2 days: AX73 V1
What I did was the following:
Disconnect the RE550 (which was the farthest location from the base router – about 100ft) and replace with an ethernet backhaul TP-link router.
I believe the issue was that the RE550 was so far away that although it connected, it was creating stress on the new easymesh network somehow and caused it to reboot.
- Copy Link
- Report Inappropriate Content
Thanks a lot.
For my case, AX73 after last random reboot. AX73 online for 2 days. I do everything as usual. I don't understand now.
But if AX73 reboot again. I will find new location for range extender.
- Copy Link
- Report Inappropriate Content
Archer AX73 V1, using Archer C80 as sattelite device in EasyMesh netwrok, even after updating to the beta version it keeps restarting even more often I feel like.
- Copy Link
- Report Inappropriate Content
Hi, may I know how often it happens now? and are you using Ethernet backhaul or wireless backhaul to build the EasyMesh network?
Please also let us know how many client devices are usually connected and what are they.
- Copy Link
- Report Inappropriate Content
It happens at least every 12 hours, sometimes it restarts multiple times in row, like 10 minutes inbetween, sometimes it restarts after 7 hours running, etc.. I am using Ethernet to connect them, around 5 clients connected on the Archer C80 and 5 on the Archer AX73 V1, Archer 73 V1 clients are (Wifi: Smart TV, One laptop, two mobiles) (Ethernet:1 Desktop, one of the laptops always uses Ethernet) I also use simple Netgear switch inbetween my room and the router.
Archer C80 clients are (Wifi: Mobile, Two IoT devices, Chromecast) (Ethernet: Desktop)
- Copy Link
- Report Inappropriate Content
Thanks a lot for those information, we've seen your new thread and has forwarded your case to senior engineer for debugging via email.
https://community.tp-link.com/en/home/forum/topic/653028?replyId=1312742
- Copy Link
- Report Inappropriate Content
@Sunshine I have the same problem with my AX5400 connected with RE505X
2024-03-11 19:05:51 Led Controller INFO [1192] Start to run WAN1_ON
2024-03-11 19:05:51 Led Controller INFO [1192] Start to run WAN0_OFF
2024-03-11 19:05:51 Led Controller INFO [1192] Start to run LAN_ON
2024-03-11 19:05:46 Time Settings INFO [17978] Service restart
2024-03-11 19:05:44 Led Controller INFO [1192] Start to run WAN1_ON
2024-03-11 19:05:44 Led Controller INFO [1192] Start to run WAN0_OFF
2024-03-11 19:05:44 Led Controller INFO [1192] Start to run LAN_ON
2024-03-11 19:05:15 UPnP INFO [14684] Service start
2024-03-11 19:05:15 UPnP INFO [14684] Service stop
2024-03-11 19:05:11 Remote Management INFO [13774] Service stop
2024-03-11 19:05:02 Time Settings INFO [12892] Service restart
2024-03-11 19:05:01 NAT INFO [11520] IPSEC ALG enabled
2024-03-11 19:05:01 NAT INFO [11520] L2TP ALG enabled
2024-03-11 19:05:01 NAT INFO [11520] PPTP ALG enabled
2024-03-11 19:05:01 NAT INFO [11520] SIP ALG enabled
2024-03-11 19:05:01 NAT INFO [11520] RTSP ALG enabled
2024-03-11 19:05:01 NAT INFO [11520] H323 ALG enabled
2024-03-11 19:05:01 NAT INFO [11520] TFTP ALG enabled
2024-03-11 19:05:01 NAT INFO [11520] FTP ALG enabled
2024-03-11 19:04:57 3G4G DEBUG [1613] backup: switch network to WIRED.
2024-03-11 19:04:57 NAT INFO [11520] Initialization succeeded
2023-09-19 00:00:53 NAT INFO [11520] Initialization succeeded
2023-09-19 00:00:51 3G4G DEBUG [1613] backup: switch network to WIRED.
2023-09-19 00:00:50 Led Controller INFO [1192] Start to run WAN1_OFF
2023-09-19 00:00:50 Led Controller INFO [1192] Start to run WAN0_ON
2023-09-19 00:00:50 Led Controller INFO [1192] Start to run LAN_ON
2023-09-19 00:00:48 Led Controller INFO [1192] Start to run STATUS_ON
2023-09-19 00:00:47 QoS INFO [10956] Service start
2023-09-19 00:00:47 QoS INFO [10956] Function disabled
2023-09-19 00:00:46 Led Controller INFO [1192] Start to run GENERAL
2023-09-19 00:00:40 Traffic Statistics INFO [9536] Service start
2023-09-19 00:00:29 Factory Reset INFO [7367] Service start
2023-09-19 00:00:27 Parental Controls INFO [7000] Service start
2023-09-19 00:00:27 Parental Controls INFO [7000] Function enabled
2023-09-19 00:00:26 Access Control INFO [6860] Service start
2023-09-19 00:00:26 Access Control INFO [6860] Function disabled
2023-09-19 00:00:24 NAT DEBUG [6075] Flush conntrack
2023-09-19 00:00:24 NAT INFO [6075] Function enabled
2023-09-19 00:00:24 NAT NOTICE [6075] Create NAT chain succeeded
2023-09-19 00:00:22 NAT INFO [6075] Initialization succeeded
2023-09-19 00:00:21 NAT INFO [6075] Initialization succeeded
2023-09-19 00:00:21 Basic Security INFO [5772] Service start
2023-09-19 00:00:21 Basic Security NOTICE [5772] Flush conntrack table succeeded
2023-09-19 00:00:19 Firewall INFO [4467] Service start
2023-09-19 00:00:17 IP & MAC Binding INFO [5464] Daemon connection succeeded
2023-09-19 00:00:17 IP & MAC Binding INFO [5464] ARP Binding disabled
2023-09-19 00:00:17 IP & MAC Binding INFO [5464] Config interface initialization succeeded
2023-09-19 00:00:17 IP & MAC Binding INFO [5464] Initialization succeeded
2023-09-19 00:00:16 UPnP INFO [5203] Service start
2023-09-19 00:00:16 UPnP INFO [5203] Service stop
2023-09-19 00:00:15 Led Controller ERROR [1192] Config importing failed
2023-09-19 00:00:15 Led Controller DEBUG [1192] Failed to read _ON
2023-09-19 00:00:14 Led Controller ERROR [1192] Config importing failed
2023-09-19 00:00:14 Led Controller DEBUG [1192] Failed to read _ON
2023-09-19 00:00:13 Remote Management INFO [4674] Service stop
2023-09-19 00:00:12 Led Controller ERROR [1192] Config importing failed
2023-09-19 00:00:12 Led Controller DEBUG [1192] Failed to read _ON
2023-09-19 00:00:11 Led Controller INFO [1192] Start to run WIFI2G_ON
2023-09-19 00:00:11 Led Controller INFO [1192] Start to run WIFI5G_ON
2023-09-19 00:00:11 Led Controller ERROR [1192] Config importing failed
2023-09-19 00:00:11 Led Controller DEBUG [1192] Failed to read _ON
2023-09-19 00:00:11 Led Controller ERROR [1192] Config importing failed
2023-09-19 00:00:11 Led Controller DEBUG [1192] Failed to read _ON
2023-09-19 00:00:10 Led Controller ERROR [1192] Config importing failed
2023-09-19 00:00:10 Led Controller DEBUG [1192] Failed to read _ON
2023-09-19 00:00:10 Led Controller ERROR [1192] Config importing failed
2023-09-19 00:00:10 Led Controller DEBUG [1192] Failed to read _ON
2023-09-19 00:00:09 Led Controller ERROR [1192] Config importing failed
2023-09-19 00:00:09 Led Controller DEBUG [1192] Failed to read _ON
2023-09-19 00:00:09 Led Controller ERROR [1192] Config importing failed
2023-09-19 00:00:09 Led Controller DEBUG [1192] Failed to read _ON
2023-09-19 00:00:08 Led Controller ERROR [1192] Config importing failed
2023-09-19 00:00:08 Led Controller DEBUG [1192] Failed to read _ON
2023-09-19 00:00:08 Led Controller ERROR [1192] Config importing failed
2023-09-19 00:00:08 Led Controller DEBUG [1192] Failed to read _ON
2023-09-19 00:00:07 Led Controller ERROR [1192] Config importing failed
2023-09-19 00:00:07 Led Controller DEBUG [1192] Failed to read _ON
2023-09-19 00:00:07 Led Controller ERROR [1192] Config importing failed
2023-09-19 00:00:07 Led Controller DEBUG [1192] Failed to read _ON
2023-09-19 00:00:00 Time Settings INFO [1232] Service start
1970-01-01 00:00:20 Led Controller INFO [1192] Service start
- Copy Link
- Report Inappropriate Content
Hi, for different models, please refer to this thread for troubleshooting first: What can I do if my Router keeps Rebooting randomly?
If the problem still exists, please start a new thread to provide the detailed network topology and client devices as well.
- Copy Link
- Report Inappropriate Content
Hi,
Same issue here Archer AX73 V1 1.3.5 Build 20230919 rel.12938(4555) in EasyMesh with RE550 with wireless backhaul.
Sometimes it's rebooting multiple times a day. I have around 25 devices- light bulbs, relays, motion sensors, phones, laptops, tablets and TVs. 1 wired connection to the AX73 (Raspberry Pi 5) and 1 wired connection to the RE550 (Chromecast with Google TV). On the AX I have 6 open ports (port forwarding) for WireGuard VPN, NGINX, Plex and one another app.
Will try now how it will be without the RE550 and if the random reboots will continue.
Log from last reboot:
2024-03-29 07:53:06 Led Controller INFO [1167] Start to run WAN1_ON 2024-03-29 07:53:06 Led Controller INFO [1167] Start to run WAN0_OFF 2024-03-29 07:53:06 Led Controller INFO [1167] Start to run LAN_ON 2024-03-29 07:53:00 Led Controller INFO [1167] Start to run WAN1_ON 2024-03-29 07:53:00 Led Controller INFO [1167] Start to run WAN0_OFF 2024-03-29 07:53:00 Led Controller INFO [1167] Start to run LAN_ON 2024-03-29 07:52:28 UPnP INFO [15715] Service start 2024-03-29 07:52:27 UPnP INFO [15715] Service stop 2024-03-29 07:52:25 Remote Management INFO [15401] Service stop 2024-03-29 07:52:20 NAT INFO [12651] IPSEC ALG enabled 2024-03-29 07:52:20 NAT INFO [12651] L2TP ALG enabled 2024-03-29 07:52:20 NAT INFO [12651] PPTP ALG enabled 2024-03-29 07:52:20 NAT INFO [12651] SIP ALG disabled 2024-03-29 07:52:20 NAT INFO [12651] RTSP ALG disabled 2024-03-29 07:52:20 NAT INFO [12651] H323 ALG disabled 2024-03-29 07:52:20 NAT INFO [12651] TFTP ALG disabled 2024-03-29 07:52:19 NAT INFO [12651] FTP ALG disabled 2024-03-29 07:52:18 NAT NOTICE [12651] Virtual server created succeeded[ex-port:443 ip:192.168.0.3 in-port:443 protocol:tcp] 2024-03-29 07:52:18 NAT NOTICE [12651] Virtual server created succeeded[ex-port:80 ip:192.168.0.3 in-port:80 protocol:all]
2024-03-29 07:52:17 NAT NOTICE [12651] Virtual server created succeeded[ex-port:32400 ip:192.168.0.3 in-port:32400 protocol:all]
2024-03-29 07:52:17 NAT NOTICE [12651] Virtual server created succeeded[ex-port:59595 ip:192.168.0.3 in-port:59595 protocol:all] 2024-03-29 07:52:16 NAT NOTICE [12651] Virtual server created succeeded[ex-port:6882 ip:192.168.0.3 in-port:6882 protocol:all] 2024-03-29 07:52:16 NAT NOTICE [12651] Virtual server created succeeded[ex-port:51820 ip:192.168.0.3 in-port:51820 protocol:udp] 2024-03-29 07:52:12 NAT INFO [12651] Initialization succeeded
2024-03-29 07:52:12 NAT INFO [12651] Initialization succeeded
- Copy Link
- Report Inappropriate Content
Information
Helpful: 12
Views: 9388
Replies: 69
Voters 5
