Archer AX21-1800 v2.0 Led Controller INFO [1093] Start to run WAN0_OFF

Archer AX21-1800 v2.0 Led Controller INFO [1093] Start to run WAN0_OFF
Archer AX21-1800 v2.0 Led Controller INFO [1093] Start to run WAN0_OFF
2022-07-20 12:01:42 - last edited 2022-07-23 13:14:17
Model: Archer AX21  
Hardware Version: V2
Firmware Version: 2.1.5 Build 20211231 rel.73898(5553)

Router Logs:

2022-07-20 07:16:05 Led Controller INFO [1093] Start to run WAN1_ON

2022-07-20 07:16:05 Led Controller INFO [1093] Start to run WAN0_OFF

2022-07-20 07:16:05 Led Controller INFO [1093] Start to run LAN_ON

2022-07-20 07:15:56 Led Controller INFO [1093] Start to run WAN1_OFF

2022-07-20 07:15:56 Led Controller INFO [1093] Start to run WAN0_ON

2022-07-20 07:15:56 Led Controller INFO [1093] Start to run LAN_ON

2022-07-20 07:15:54 Led Controller INFO [1093] Start to run WAN1_OFF

2022-07-20 07:15:54 Led Controller INFO [1093] Start to run WAN0_OFF

2022-07-20 07:15:54 Led Controller INFO [1093] Start to run LAN_ON

 

 

I purchased the AX21 through Amazon and have been pleased with the router so far. I have a TP-Link AX11000 as my main router and the AX21 is currently working in AP mode. I noticed the numerous WAN0_OFF/ON lines in my log files and became a little concerned. After reading many posts in this forum concerning this issue, I started digging to see if my issue was the same or something different. I do not like unknown or vague logs because they could be signs of failure. First off, my exact error code is 1093. Many reporting disconnects with these routers were showing different error codes. 

 

Here are the steps I tried to resolve the issue:

1) Reboot router

2) Factory Reset router

3) Changed WiFi settings; Channel specifics, etc

4) Ran WiFi Analyzer to pick the best channels for AP and MAIN router that do not overlap.

 

The problem still occurred at least once per day. Because the router was still in the return window, I returned the router and received a new one from Amazon. Same issue. I went through the same steps with the newer router, and received the same results. 

 

I decided to dig a little deeper and try to capture more detailed NETWORK logs during these error messages. I created a Power Shell script to ping Google continuously with a date time stamp and then append the information to a text file: 

 

PS> Start-Transcript -path C:/Script/PingLog.txt -Append

PS> Ping.exe -t www.google.com | ForEach {"{0} - {1}" -f (Get-Date),$_}

 

I matched the date of the error in the log with the time stamp on the pings and found that I was NOT losing connection during WAN0-OFF/ON errors. Pings were still continuous with no break in connection.

 

7/20/2022 7:15:50 AM - Reply from 173.194.219.99: bytes=32 time=16ms TTL=105
7/20/2022 7:15:51 AM - Reply from 173.194.219.99: bytes=32 time=17ms TTL=105
7/20/2022 7:15:52 AM - Reply from 173.194.219.99: bytes=32 time=17ms TTL=105
7/20/2022 7:15:53 AM - Reply from 173.194.219.99: bytes=32 time=17ms TTL=105
7/20/2022 7:15:54 AM - Reply from 173.194.219.99: bytes=32 time=18ms TTL=105
7/20/2022 7:15:55 AM - Reply from 173.194.219.99: bytes=32 time=18ms TTL=105
7/20/2022 7:15:56 AM - Reply from 173.194.219.99: bytes=32 time=17ms TTL=105
7/20/2022 7:15:57 AM - Reply from 173.194.219.99: bytes=32 time=19ms TTL=105
7/20/2022 7:15:58 AM - Reply from 173.194.219.99: bytes=32 time=17ms TTL=105
7/20/2022 7:15:59 AM - Reply from 173.194.219.99: bytes=32 time=19ms TTL=105
7/20/2022 7:16:00 AM - Reply from 173.194.219.99: bytes=32 time=17ms TTL=105
7/20/2022 7:16:01 AM - Reply from 173.194.219.99: bytes=32 time=18ms TTL=105
7/20/2022 7:16:02 AM - Reply from 173.194.219.99: bytes=32 time=18ms TTL=105
7/20/2022 7:16:03 AM - Reply from 173.194.219.99: bytes=32 time=17ms TTL=105
7/20/2022 7:16:04 AM - Reply from 173.194.219.99: bytes=32 time=17ms TTL=105
7/20/2022 7:16:05 AM - Reply from 173.194.219.99: bytes=32 time=18ms TTL=105
7/20/2022 7:16:06 AM - Reply from 173.194.219.99: bytes=32 time=18ms TTL=105
7/20/2022 7:16:07 AM - Reply from 173.194.219.99: bytes=32 time=20ms TTL=105
7/20/2022 7:16:08 AM - Reply from 173.194.219.99: bytes=32 time=17ms TTL=105
7/20/2022 7:16:09 AM - Reply from 173.194.219.99: bytes=32 time=17ms TTL=105
7/20/2022 7:16:10 AM - Reply from 173.194.219.99: bytes=32 time=23ms TTL=105

 

My conclusion is that there is a bug in the firmware concerning the LED controller and the overall function of the router is still fine. However, I am still a little nervous. I would very much like to know what exactly is going on. A response from an engineer at least letting me know that I am correct in my assessment would go a long way in helping me feel a little better about my purchase. It is still in the return window.  

 

Thank you!

 

 

Update 7/23//2022

 

I unplugged the connection from the WAN port on the 1800 to the Main router and plugged into one of the open ports totally bypassing the WAN. Device has been running for 3 days with NO WAN_1ON/OFF in the logs. I can confirm that the issue is in the WAN Port while in AP mode. To be fair, this is probably the recommended scenario with most AP devices.  

 

 

1
1
#1
Options