Archer AX-21 repeat LAN errors

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

Archer AX-21 repeat LAN errors

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Archer AX-21 repeat LAN errors
Archer AX-21 repeat LAN errors
2023-10-30 19:09:09
Model: Archer A20  
Hardware Version:
Firmware Version: 2.1.8 build 20230829 rel 69232

Network trashing is occurring.  Connection on both 2.4 and 5g both have the same issue.  I've updated firmware and restarted both the modem and router multiple times.  ISP has been called multiple times.  They maintain that their connection is stable and logs are clean.  Here are the logs from my router.

 

2023-10-29 16:39:12 Led Controller INFO [1093] Start to run WAN1_ON

2023-10-29 16:39:12 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-29 16:39:11 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-29 16:39:06 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-29 16:39:06 Led Controller INFO [1093] Start to run WAN0_ON

2023-10-29 16:39:06 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-29 16:39:04 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-29 16:39:03 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-29 16:39:03 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-29 13:42:00 Led Controller INFO [1093] Start to run WAN1_ON

2023-10-29 13:42:00 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-29 13:42:00 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-29 13:41:51 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-29 13:41:51 Led Controller INFO [1093] Start to run WAN0_ON

2023-10-29 13:41:51 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-29 13:41:49 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-29 13:41:49 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-29 13:41:49 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-29 13:03:30 Led Controller INFO [1093] Start to run WAN1_ON

2023-10-29 13:03:30 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-29 13:03:30 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-29 13:03:17 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-29 13:03:17 Led Controller INFO [1093] Start to run WAN0_ON

2023-10-29 13:03:17 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-29 13:03:15 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-29 13:03:15 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-29 13:03:15 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-29 09:24:04 Led Controller INFO [1093] Start to run WAN1_ON

2023-10-29 09:24:04 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-29 09:24:04 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-29 09:23:58 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-29 09:23:58 Led Controller INFO [1093] Start to run WAN0_ON

2023-10-29 09:23:58 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-29 09:23:56 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-29 09:23:56 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-29 09:23:56 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-29 03:39:19 Led Controller INFO [1093] Start to run WAN1_ON

2023-10-29 03:39:19 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-29 03:39:19 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-29 03:39:11 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-29 03:39:11 Led Controller INFO [1093] Start to run WAN0_ON

2023-10-29 03:39:11 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-29 03:39:09 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-29 03:39:09 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-29 03:39:09 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-29 02:43:41 Led Controller INFO [1093] Start to run WAN1_ON

2023-10-29 02:43:41 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-29 02:43:41 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-29 02:43:28 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-29 02:43:28 Led Controller INFO [1093] Start to run WAN0_ON

2023-10-29 02:43:28 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-29 02:43:26 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-29 02:43:26 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-29 02:43:26 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-28 20:50:36 Led Controller INFO [1093] Start to run WAN1_ON

2023-10-28 20:50:36 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-28 20:50:36 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-28 20:50:35 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-28 20:50:35 Led Controller INFO [1093] Start to run WAN0_ON

2023-10-28 20:50:35 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-28 20:50:33 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-28 20:50:33 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-28 20:50:33 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-28 13:46:33 Led Controller INFO [1093] Start to run WAN1_ON

2023-10-28 13:46:33 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-28 13:46:33 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-28 13:46:28 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-28 13:46:28 Led Controller INFO [1093] Start to run WAN0_ON

2023-10-28 13:46:28 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-28 13:46:26 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-28 13:46:26 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-28 13:46:26 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-28 07:53:14 Led Controller INFO [1093] Start to run WAN1_ON

2023-10-28 07:53:14 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-28 07:53:14 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-28 07:53:09 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-28 07:53:09 Led Controller INFO [1093] Start to run WAN0_ON

2023-10-28 07:53:08 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-28 07:53:06 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-28 07:53:06 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-28 07:53:06 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-27 15:09:21 Led Controller INFO [1093] Start to run WAN1_ON

2023-10-27 15:09:21 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-27 15:09:21 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-27 15:09:18 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-27 15:09:18 Led Controller INFO [1093] Start to run WAN0_ON

2023-10-27 15:09:18 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-27 15:09:16 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-27 15:09:16 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-27 15:09:16 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-27 06:19:50 Led Controller INFO [1093] Start to run WAN1_ON

2023-10-27 06:19:50 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-27 06:19:50 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-27 06:19:38 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-27 06:19:38 Led Controller INFO [1093] Start to run WAN0_ON

2023-10-27 06:19:38 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-27 06:19:36 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-27 06:19:36 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-27 06:19:36 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-27 02:04:54 Led Controller INFO [1093] Start to run WAN1_ON

2023-10-27 02:04:54 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-27 02:04:54 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-27 02:04:41 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-27 02:04:41 Led Controller INFO [1093] Start to run WAN0_ON

2023-10-27 02:04:41 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-27 02:04:39 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-27 02:04:39 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-27 02:04:39 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-26 21:41:25 Led Controller INFO [1093] Start to run WAN1_ON

2023-10-26 21:41:25 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-26 21:41:25 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-26 21:41:19 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-26 21:41:19 Led Controller INFO [1093] Start to run WAN0_ON

2023-10-26 21:41:19 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-26 21:41:17 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-26 21:41:17 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-26 21:41:17 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-26 19:13:42 Led Controller INFO [1093] Start to run WAN1_ON

2023-10-26 19:13:42 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-26 19:13:42 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-26 19:13:28 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-26 19:13:28 Led Controller INFO [1093] Start to run WAN0_ON

2023-10-26 19:13:28 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-26 19:13:26 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-26 19:13:26 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-26 19:13:26 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-26 18:42:45 Led Controller INFO [1093] Start to run WAN1_ON

2023-10-26 18:42:45 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-26 18:42:45 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-26 18:42:41 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-26 18:42:41 Led Controller INFO [1093] Start to run WAN0_ON

2023-10-26 18:42:41 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-26 18:42:39 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-26 18:42:39 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-26 18:42:39 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-26 12:43:23 Led Controller INFO [1093] Start to run WAN1_ON

2023-10-26 12:43:23 Led Controller INFO [1093] Start to run WAN0_OFF

2023-10-26 12:43:23 Led Controller INFO [1093] Start to run LAN_OFF

2023-10-26 12:43:22 Led Controller INFO [1093] Start to run WAN1_OFF

2023-10-26 12:43:22 Led Controller INFO [1093] Start to run WAN0_ON

  0      
  0      
#1
Options
5 Reply
Re:Archer AX-21 repeat LAN errors
2023-10-30 21:20:41

  @jkennedy000,

Are these the only errors that are being presented, or are there other errors besides notices regarding the LED controller?

If the WAN errors are actually errors, you should see problems across all devices, wireless and wired.

 

What behaviors are you seeing on your network? Are connections to the network dropping or to the internet?

How have you configured your network? What modem do you have from your ISP?

 

The first thing to check would be your ethernet cable to make sure that your cable does not have a fault.

  0  
  0  
#2
Options
Re:Archer AX-21 repeat LAN errors
2023-10-31 13:56:29

  @Riley_S 

 

Thanks for reaching out!  I'm not a pro but will try to answer all your questions.  These are the only errors registering on the router.  I'm seeing very brief network drop multiple times per day.  The router stays connected but I lose internet connection for appx 10 to 15 seconds.  
 

My router is setup with default settings.  One 2.4 encrypted channel and on 5.0 encrypted.  
 

We are using spectrums modem.  During these minor drops the online light does not change on the modem and the spectrum app says we're still online.  
 

Single WiFi router.  No repeater.  No slave.  
 

I just ordered a new Ethernet cable.  And I ordered a usb-c Ethernet adapter so I can test directly from the modem.  Will report back.  
 

  0  
  0  
#3
Options
Re:Archer AX-21 repeat LAN errors
2023-10-31 21:11:37

  @jkennedy000,

When your connection drops for that brief period, do you happen to know if it happens to all of your devices at once or only a select few of them? 

There is also an LED light on Archers for indicating its current connection to the internet, have you observed this light go out?

 

I would check to make sure that your ISP modem is not a Gateway and can provide wireless functionality; if it is, then it will need to be placed in Bridge or IP Passthrough Mode to disable the wireless functionality - or the Archer will need to be put into AP mode. Having two routers on your network could potentially cause this behavior.

It would also be beneficial to know if a wired device is disconnecting or only wireless devices - as it may narrow the search for a cause.

 


Lastly, are there any other devices plugged into your ISP's modem, or is it just the Archer?

 

  0  
  0  
#4
Options
Re:Archer AX-21 repeat LAN errors
2023-11-01 19:12:37

  @Riley_S 
Thanks for the response!  I'm hoping I can answer your questions.  

The connection appears to affect multiple devices, but the biggest challenge is my work laptop.  

The lights don't appear to change with the interruptions.  The ISP modem is not a gateway.  Nothing is hard wired.  Only the archer is connected to the ISP modem.  

 

So the latest feedback that I recieved was that latency spikes could be causing my most notable problem on my work laptop.  As that device is sensitive to latency above 100ms.  I have 56 devices connected.  The vast majority are smart devices.  Almost all are on my 2.4ghz network.  I've experienced the problem connected to both 2.4 and 5ghz networks.  

 

Is there something config wise that could pull my ping numbers down?  Or is the Archer-21 simply outdated?  

 

More info.  Here is a 100 ping of google.com, hard wired and not hard wired.  

 

Hard wired: 
 

Pinging google.com [142.250.190.142] with 32 bytes of data:
Reply from 142.250.190.142: bytes=32 time=26ms TTL=115
Reply from 142.250.190.142: bytes=32 time=31ms TTL=115
Reply from 142.250.190.142: bytes=32 time=35ms TTL=115
Reply from 142.250.190.142: bytes=32 time=24ms TTL=115
Reply from 142.250.190.142: bytes=32 time=51ms TTL=115
Reply from 142.250.190.142: bytes=32 time=17ms TTL=115
Reply from 142.250.190.142: bytes=32 time=39ms TTL=115
Request timed out.
Reply from 142.250.190.142: bytes=32 time=38ms TTL=115
Reply from 142.250.190.142: bytes=32 time=16ms TTL=115
Reply from 142.250.190.142: bytes=32 time=14ms TTL=115
Reply from 142.250.190.142: bytes=32 time=15ms TTL=115
Reply from 142.250.190.142: bytes=32 time=19ms TTL=115
Reply from 142.250.190.142: bytes=32 time=23ms TTL=115
Reply from 142.250.190.142: bytes=32 time=31ms TTL=115
Reply from 142.250.190.142: bytes=32 time=14ms TTL=115
Reply from 142.250.190.142: bytes=32 time=15ms TTL=115
Reply from 142.250.190.142: bytes=32 time=16ms TTL=115
Reply from 142.250.190.142: bytes=32 time=14ms TTL=115
Reply from 142.250.190.142: bytes=32 time=15ms TTL=115
Reply from 142.250.190.142: bytes=32 time=15ms TTL=115
Reply from 142.250.190.142: bytes=32 time=23ms TTL=115
Reply from 142.250.190.142: bytes=32 time=14ms TTL=115
Reply from 142.250.190.142: bytes=32 time=16ms TTL=115
Reply from 142.250.190.142: bytes=32 time=16ms TTL=115
Reply from 142.250.190.142: bytes=32 time=17ms TTL=115
Reply from 142.250.190.142: bytes=32 time=13ms TTL=115
Reply from 142.250.190.142: bytes=32 time=31ms TTL=115
Reply from 142.250.190.142: bytes=32 time=14ms TTL=115
Reply from 142.250.190.142: bytes=32 time=18ms TTL=115
Reply from 142.250.190.142: bytes=32 time=16ms TTL=115
Reply from 142.250.190.142: bytes=32 time=15ms TTL=115
Reply from 142.250.190.142: bytes=32 time=16ms TTL=115
Reply from 142.250.190.142: bytes=32 time=16ms TTL=115
Reply from 142.250.190.142: bytes=32 time=16ms TTL=115
Reply from 142.250.190.142: bytes=32 time=19ms TTL=115
Reply from 142.250.190.142: bytes=32 time=14ms TTL=115
Reply from 142.250.190.142: bytes=32 time=16ms TTL=115
Reply from 142.250.190.142: bytes=32 time=14ms TTL=115
Reply from 142.250.190.142: bytes=32 time=18ms TTL=115
Reply from 142.250.190.142: bytes=32 time=14ms TTL=115
Reply from 142.250.190.142: bytes=32 time=14ms TTL=115
Reply from 142.250.190.142: bytes=32 time=14ms TTL=115
Reply from 142.250.190.142: bytes=32 time=15ms TTL=115
Reply from 142.250.190.142: bytes=32 time=14ms TTL=115
Reply from 142.250.190.142: bytes=32 time=14ms TTL=115
Reply from 142.250.190.142: bytes=32 time=14ms TTL=115
Reply from 142.250.190.142: bytes=32 time=16ms TTL=115
Reply from 142.250.190.142: bytes=32 time=15ms TTL=115
Reply from 142.250.190.142: bytes=32 time=25ms TTL=115
Reply from 142.250.190.142: bytes=32 time=28ms TTL=115
Reply from 142.250.190.142: bytes=32 time=13ms TTL=115
Request timed out.
Reply from 142.250.190.142: bytes=32 time=15ms TTL=115
Reply from 142.250.190.142: bytes=32 time=14ms TTL=115
Reply from 142.250.190.142: bytes=32 time=18ms TTL=115
Reply from 142.250.190.142: bytes=32 time=15ms TTL=115
Reply from 142.250.190.142: bytes=32 time=14ms TTL=115
Reply from 142.250.190.142: bytes=32 time=14ms TTL=115
Reply from 142.250.190.142: bytes=32 time=14ms TTL=115
Reply from 142.250.190.142: bytes=32 time=31ms TTL=115
Reply from 142.250.190.142: bytes=32 time=14ms TTL=115
Reply from 142.250.190.142: bytes=32 time=16ms TTL=115
Reply from 142.250.190.142: bytes=32 time=15ms TTL=115
Reply from 142.250.190.142: bytes=32 time=33ms TTL=115
Request timed out.
Reply from 142.250.190.142: bytes=32 time=16ms TTL=115
Reply from 142.250.190.142: bytes=32 time=13ms TTL=115
Reply from 142.250.190.142: bytes=32 time=15ms TTL=115
Reply from 142.250.190.142: bytes=32 time=17ms TTL=115
Reply from 142.250.190.142: bytes=32 time=15ms TTL=115
Reply from 142.250.190.142: bytes=32 time=21ms TTL=115
Reply from 142.250.190.142: bytes=32 time=15ms TTL=115
Reply from 142.250.190.142: bytes=32 time=20ms TTL=115
Reply from 142.250.190.142: bytes=32 time=14ms TTL=115
Reply from 142.250.190.142: bytes=32 time=15ms TTL=115
Reply from 142.250.190.142: bytes=32 time=14ms TTL=115
Reply from 142.250.190.142: bytes=32 time=15ms TTL=115
Reply from 142.250.190.142: bytes=32 time=17ms TTL=115
Reply from 142.250.190.142: bytes=32 time=31ms TTL=115
Reply from 142.250.190.142: bytes=32 time=21ms TTL=115
Reply from 142.250.190.142: bytes=32 time=14ms TTL=115
Reply from 142.250.190.142: bytes=32 time=16ms TTL=115
Reply from 142.250.190.142: bytes=32 time=18ms TTL=115
Reply from 142.250.190.142: bytes=32 time=16ms TTL=115
Reply from 142.250.190.142: bytes=32 time=28ms TTL=115
Reply from 142.250.190.142: bytes=32 time=14ms TTL=115
Reply from 142.250.190.142: bytes=32 time=23ms TTL=115
Reply from 142.250.190.142: bytes=32 time=24ms TTL=115
Reply from 142.250.190.142: bytes=32 time=20ms TTL=115
Reply from 142.250.190.142: bytes=32 time=19ms TTL=115
Reply from 142.250.190.142: bytes=32 time=17ms TTL=115
Reply from 142.250.190.142: bytes=32 time=16ms TTL=115
Reply from 142.250.190.142: bytes=32 time=23ms TTL=115
Reply from 142.250.190.142: bytes=32 time=17ms TTL=115
Reply from 142.250.190.142: bytes=32 time=16ms TTL=115
Reply from 142.250.190.142: bytes=32 time=17ms TTL=115
Reply from 142.250.190.142: bytes=32 time=16ms TTL=115
Reply from 142.250.190.142: bytes=32 time=15ms TTL=115
Reply from 142.250.190.142: bytes=32 time=14ms TTL=115

Ping statistics for 142.250.190.142:
    Packets: Sent = 100, Received = 97, Lost = 3 (3% loss),
Approximate round trip times in milli-seconds:
    Minimum = 13ms, Maximum = 51ms, Average = 18ms

 

Using wifi - right next to the router.

C:\Users\jkenn>ping google.com -n 100

Pinging google.com [142.251.32.14] with 32 bytes of data:
Reply from 142.251.32.14: bytes=32 time=22ms TTL=55
Reply from 142.251.32.14: bytes=32 time=28ms TTL=55
Reply from 142.251.32.14: bytes=32 time=43ms TTL=55
Reply from 142.251.32.14: bytes=32 time=18ms TTL=55
Reply from 142.251.32.14: bytes=32 time=18ms TTL=55
Reply from 142.251.32.14: bytes=32 time=24ms TTL=55
Reply from 142.251.32.14: bytes=32 time=18ms TTL=55
Reply from 142.251.32.14: bytes=32 time=21ms TTL=55
Reply from 142.251.32.14: bytes=32 time=24ms TTL=55
Reply from 142.251.32.14: bytes=32 time=31ms TTL=55
Reply from 142.251.32.14: bytes=32 time=23ms TTL=55
Reply from 142.251.32.14: bytes=32 time=19ms TTL=55
Reply from 142.251.32.14: bytes=32 time=19ms TTL=55
Reply from 142.251.32.14: bytes=32 time=48ms TTL=55
Reply from 142.251.32.14: bytes=32 time=38ms TTL=55
Reply from 142.251.32.14: bytes=32 time=33ms TTL=55
Reply from 142.251.32.14: bytes=32 time=24ms TTL=55
Reply from 142.251.32.14: bytes=32 time=26ms TTL=55
Reply from 142.251.32.14: bytes=32 time=80ms TTL=55
Reply from 142.251.32.14: bytes=32 time=54ms TTL=55
Reply from 142.251.32.14: bytes=32 time=68ms TTL=55
Reply from 142.251.32.14: bytes=32 time=62ms TTL=55
Reply from 142.251.32.14: bytes=32 time=75ms TTL=55
Reply from 142.251.32.14: bytes=32 time=37ms TTL=55
Reply from 142.251.32.14: bytes=32 time=34ms TTL=55
Reply from 142.251.32.14: bytes=32 time=35ms TTL=55
Reply from 142.251.32.14: bytes=32 time=38ms TTL=55
Reply from 142.251.32.14: bytes=32 time=61ms TTL=55
Reply from 142.251.32.14: bytes=32 time=273ms TTL=55
Reply from 142.251.32.14: bytes=32 time=71ms TTL=55
Reply from 142.251.32.14: bytes=32 time=76ms TTL=55
Reply from 142.251.32.14: bytes=32 time=90ms TTL=55
Reply from 142.251.32.14: bytes=32 time=57ms TTL=55
Reply from 142.251.32.14: bytes=32 time=54ms TTL=55
Reply from 142.251.32.14: bytes=32 time=63ms TTL=55
Reply from 142.251.32.14: bytes=32 time=64ms TTL=55
Reply from 142.251.32.14: bytes=32 time=63ms TTL=55
Reply from 142.251.32.14: bytes=32 time=34ms TTL=55
Reply from 142.251.32.14: bytes=32 time=31ms TTL=55
Reply from 142.251.32.14: bytes=32 time=79ms TTL=55
Reply from 142.251.32.14: bytes=32 time=47ms TTL=55
Reply from 142.251.32.14: bytes=32 time=42ms TTL=55
Reply from 142.251.32.14: bytes=32 time=77ms TTL=55
Reply from 142.251.32.14: bytes=32 time=49ms TTL=55
Reply from 142.251.32.14: bytes=32 time=59ms TTL=55
Reply from 142.251.32.14: bytes=32 time=82ms TTL=55
Reply from 142.251.32.14: bytes=32 time=35ms TTL=55
Reply from 142.251.32.14: bytes=32 time=70ms TTL=55
Reply from 142.251.32.14: bytes=32 time=55ms TTL=55
Reply from 142.251.32.14: bytes=32 time=87ms TTL=55
Reply from 142.251.32.14: bytes=32 time=78ms TTL=55
Reply from 142.251.32.14: bytes=32 time=32ms TTL=55
Reply from 142.251.32.14: bytes=32 time=51ms TTL=55
Reply from 142.251.32.14: bytes=32 time=20ms TTL=55
Reply from 142.251.32.14: bytes=32 time=45ms TTL=55
Reply from 142.251.32.14: bytes=32 time=49ms TTL=55
Reply from 142.251.32.14: bytes=32 time=32ms TTL=55
Reply from 142.251.32.14: bytes=32 time=63ms TTL=55
Reply from 142.251.32.14: bytes=32 time=52ms TTL=55
Reply from 142.251.32.14: bytes=32 time=72ms TTL=55
Reply from 142.251.32.14: bytes=32 time=64ms TTL=55
Reply from 142.251.32.14: bytes=32 time=39ms TTL=55
Reply from 142.251.32.14: bytes=32 time=68ms TTL=55
Reply from 142.251.32.14: bytes=32 time=38ms TTL=55
Reply from 142.251.32.14: bytes=32 time=53ms TTL=55
Reply from 142.251.32.14: bytes=32 time=48ms TTL=55
Reply from 142.251.32.14: bytes=32 time=20ms TTL=55
Reply from 142.251.32.14: bytes=32 time=24ms TTL=55
Reply from 142.251.32.14: bytes=32 time=31ms TTL=55
Reply from 142.251.32.14: bytes=32 time=21ms TTL=55
Reply from 142.251.32.14: bytes=32 time=117ms TTL=55
Reply from 142.251.32.14: bytes=32 time=109ms TTL=55
Reply from 142.251.32.14: bytes=32 time=131ms TTL=55
Reply from 142.251.32.14: bytes=32 time=19ms TTL=55
Reply from 142.251.32.14: bytes=32 time=31ms TTL=55
Reply from 142.251.32.14: bytes=32 time=26ms TTL=55
Reply from 142.251.32.14: bytes=32 time=16ms TTL=55
Reply from 142.251.32.14: bytes=32 time=17ms TTL=55
Reply from 142.251.32.14: bytes=32 time=20ms TTL=55
Reply from 142.251.32.14: bytes=32 time=24ms TTL=55
Reply from 142.251.32.14: bytes=32 time=19ms TTL=55
Reply from 142.251.32.14: bytes=32 time=18ms TTL=55
Reply from 142.251.32.14: bytes=32 time=25ms TTL=55
Reply from 142.251.32.14: bytes=32 time=17ms TTL=55
Reply from 142.251.32.14: bytes=32 time=18ms TTL=55
Reply from 142.251.32.14: bytes=32 time=16ms TTL=55
Reply from 142.251.32.14: bytes=32 time=16ms TTL=55
Reply from 142.251.32.14: bytes=32 time=31ms TTL=55
Reply from 142.251.32.14: bytes=32 time=20ms TTL=55
Reply from 142.251.32.14: bytes=32 time=18ms TTL=55
Reply from 142.251.32.14: bytes=32 time=17ms TTL=55
Reply from 142.251.32.14: bytes=32 time=24ms TTL=55
Reply from 142.251.32.14: bytes=32 time=24ms TTL=55
Reply from 142.251.32.14: bytes=32 time=43ms TTL=55
Reply from 142.251.32.14: bytes=32 time=17ms TTL=55
Reply from 142.251.32.14: bytes=32 time=18ms TTL=55
Reply from 142.251.32.14: bytes=32 time=22ms TTL=55
Reply from 142.251.32.14: bytes=32 time=17ms TTL=55
Reply from 142.251.32.14: bytes=32 time=23ms TTL=55
Reply from 142.251.32.14: bytes=32 time=20ms TTL=55

Ping statistics for 142.251.32.14:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 16ms, Maximum = 273ms, Average = 44ms

  0  
  0  
#5
Options
Re:Archer AX-21 repeat LAN errors
2023-11-01 22:21:09

jkennedy000 wrote

I have 56 devices connected.  The vast majority are smart devices.

 

  @jkennedy000 

 

Hmm, that is a LOT of devices, even if 1/2 are on each SSID...

 

The is an old document from TP-Link that mentions 25 in real life, https://community.tp-link.com/en/home/forum/topic/201748 but I don't know if that is still true?

 

Having the ability to connect a device may not also work in terms of the number active at one time? Could be too many active could overload the router?

 

I'd try only using 1/2 of the devices, power the 1/2 off or disconnect them and see if you still have the problem?

 

If all of them are live feed camera's for instance, vs. devices not alway on and using the SSID's it could make a difference. Theoretically, one can have a lot of devices, 250+ assigned an IP Address, but not working all at once.

  0  
  0  
#6
Options

Information

Helpful: 0

Views: 359

Replies: 5

Related Articles