Archer C80 crashes constantly.
Hi,
I had Microtik Cap AC which did everything well except wireless part, slow speed and bad coverage. So after reading positive reviews, as my is 4G speed is about 60/40 Mbit link and I don't have any wifi6 devices, I brought four day's ago Archer C80.
Network is very simple, Huawei B535-232 4G router > LAN > C80 (192.168.10.0/24) > 2,4 & 5 Ghz & LAN, total less then 10 devices, 3 Lan and rest wifi users, no local NAS etc, so traffic is 100% towards to the Internet.
Today I noticed, that connection is jumping and the reason is here (pinging from LAN > C80):
64 bytes from 192.168.10.1: icmp_seq=169 ttl=63 time=1.297 ms
64 bytes from 192.168.10.1: icmp_seq=170 ttl=63 time=1.270 ms
64 bytes from 192.168.10.1: icmp_seq=171 ttl=63 time=1.376 ms
64 bytes from 192.168.10.1: icmp_seq=172 ttl=63 time=1.403 ms
64 bytes from 192.168.10.1: icmp_seq=173 ttl=63 time=1.419 ms
64 bytes from 192.168.10.1: icmp_seq=174 ttl=63 time=1.359 ms
64 bytes from 192.168.10.1: icmp_seq=175 ttl=63 time=1.295 ms
64 bytes from 192.168.10.1: icmp_seq=176 ttl=63 time=1.240 ms
64 bytes from 192.168.10.1: icmp_seq=177 ttl=63 time=1.332 ms
64 bytes from 192.168.10.1: icmp_seq=178 ttl=63 time=292.833 ms
64 bytes from 192.168.10.1: icmp_seq=179 ttl=63 time=909.688 ms
Request timeout for icmp_seq 180
Request timeout for icmp_seq 181
Request timeout for icmp_seq 182
Request timeout for icmp_seq 183
64 bytes from 192.168.10.1: icmp_seq=180 ttl=63 time=4117.857 ms
64 bytes from 192.168.10.1: icmp_seq=181 ttl=63 time=3147.291 ms
64 bytes from 192.168.10.1: icmp_seq=182 ttl=63 time=2142.475 ms
64 bytes from 192.168.10.1: icmp_seq=183 ttl=63 time=1141.740 ms
64 bytes from 192.168.10.1: icmp_seq=184 ttl=63 time=140.892 ms
64 bytes from 192.168.10.1: icmp_seq=185 ttl=63 time=685.739 ms
64 bytes from 192.168.10.1: icmp_seq=186 ttl=63 time=3224.804 ms
64 bytes from 192.168.10.1: icmp_seq=187 ttl=63 time=2225.081 ms
64 bytes from 192.168.10.1: icmp_seq=188 ttl=63 time=1223.377 ms
64 bytes from 192.168.10.1: icmp_seq=189 ttl=63 time=226.919 ms
64 bytes from 192.168.10.1: icmp_seq=190 ttl=63 time=64.227 ms
64 bytes from 192.168.10.1: icmp_seq=191 ttl=63 time=148.139 ms
64 bytes from 192.168.10.1: icmp_seq=192 ttl=63 time=95.403 ms
64 bytes from 192.168.10.1: icmp_seq=193 ttl=63 time=124.698 ms
64 bytes from 192.168.10.1: icmp_seq=194 ttl=63 time=1.329 ms
64 bytes from 192.168.10.1: icmp_seq=195 ttl=63 time=100.789 ms
64 bytes from 192.168.10.1: icmp_seq=196 ttl=63 time=252.941 ms
64 bytes from 192.168.10.1: icmp_seq=197 ttl=63 time=63.500 ms
64 bytes from 192.168.10.1: icmp_seq=198 ttl=63 time=154.785 ms
64 bytes from 192.168.10.1: icmp_seq=199 ttl=63 time=61.712 ms
64 bytes from 192.168.10.1: icmp_seq=200 ttl=63 time=1.349 ms
64 bytes from 192.168.10.1: icmp_seq=201 ttl=63 time=90.722 ms
64 bytes from 192.168.10.1: icmp_seq=202 ttl=63 time=127.353 ms
64 bytes from 192.168.10.1: icmp_seq=203 ttl=63 time=26.604 ms
64 bytes from 192.168.10.1: icmp_seq=204 ttl=63 time=189.534 ms
64 bytes from 192.168.10.1: icmp_seq=205 ttl=63 time=186.120 ms
64 bytes from 192.168.10.1: icmp_seq=206 ttl=63 time=135.052 ms
64 bytes from 192.168.10.1: icmp_seq=207 ttl=63 time=164.409 ms
64 bytes from 192.168.10.1: icmp_seq=208 ttl=63 time=91.712 ms
64 bytes from 192.168.10.1: icmp_seq=209 ttl=63 time=152.195 ms
64 bytes from 192.168.10.1: icmp_seq=210 ttl=63 time=115.573 ms
64 bytes from 192.168.10.1: icmp_seq=211 ttl=63 time=69.003 ms
64 bytes from 192.168.10.1: icmp_seq=212 ttl=63 time=82.933 ms
64 bytes from 192.168.10.1: icmp_seq=213 ttl=63 time=89.766 ms
etc
No load in LAN network, C80 is located in unheated storage room, LAN cable is fine (tested with Fluke cable tester), computer is fine, same happens with any connected LAN device, switching C80 ports doesn't help, all LAN ports are 1G full duplex.
As also others are noticing device crashing ( Archer C80 reboots automatically https://community.tp-link.com/en/home/forum/topic/235708 ), seems the product is faulty.
How to proceed?
Edit: According to the logs, the whole device crashes and reboots:
##########################################################################
# Archer C80 System Log
# Time = 2021-03-09 21:22:23 23452s
# H-Ver = Archer C80 1.0 : S-Ver = 1.5.3 Build 210128 Rel.64503n(4555)
# L = 192.168.10.1 : M = 255.255.255.0
# WAN = STATIC IP : W = 192.168.18.252 : M = 255.255.255.0 : G = 192.168.18.1
# Cnt = 10624, Free = 10571, Busy = 53
##########################################################################
0days, 00:00:03, [lan]LAN: Attach mirror0 to stack.
0days, 00:00:04, [lan]LAN: Set interface mirror0 ip=192.168.10.1 netmask 255.255.255.0.
0days, 00:00:21, [wan]Attach interface eth0.
0days, 00:00:21, [wan]STATIC-IP: eth0 set ip 192.168.18.252 mask 255.255.255.0 gateway 192.168.18.1.
0days, 00:00:21, [wan]advanced ddns -wanChanged
0days, 00:00:21, [wan]systool sntpc -sntpRequest
0days, 00:00:21, [dnsproxy]Register Dns Detect
0days, 00:00:21, [dnsproxy]Register primary = 0x8080808, secondary = 0x4040808
0days, 00:00:21, [httpd]Http server start!
0days, 00:00:25, [wan]Wan ethernet port plug on.
0days, 00:00:25, [wan]STATIC-IP: eth0 set ip 192.168.18.252 mask 255.255.255.0 gateway 192.168.18.1.
0days, 00:00:25, [wan]advanced ddns -wanChanged
0days, 00:00:25, [wan]systool sntpc -sntpRequest
0days, 00:00:25, [dnsproxy]Register Dns Detect
0days, 00:00:25, [dnsproxy]Register primary = 0x8080808, secondary = 0x4040808
So this is serious issue, either the hardware is faulty or latest software causes it.