Archer C7 becomes un-usable every few hours/minutes
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Archer C7 becomes un-usable every few hours/minutes
Model :
Hardware Version :
Firmware Version :
ISP :
Hi,
I'm having the following problem with Archer C7. After reboot, ping to router's internal IP looks like this:
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=1.532 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.190 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.119 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.945 ms
After a few minutes or hours of normal use, ping to the router's internal IP starts looking like this:
PING 192.168.1.1 (192.168.1.1): 56 data bytes
Request timeout for icmp_seq 0
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=1558.793 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=557.861 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=990.563 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=90.227 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=108.897 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1051.264 ms
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=3735.454 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=2730.617 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=1729.204 ms
At this point, the router is completely un-usable. It's impossible to use the Internet, and even logging into the router's web interface in order to reboot it is a struggle. Needless to say, I'm about 2 meters away from the router with full line of sight. The router is running the latest official firmware. How can I fix this problem, or even debug it?
Hardware Version :
Firmware Version :
ISP :
Hi,
I'm having the following problem with Archer C7. After reboot, ping to router's internal IP looks like this:
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=1.532 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.190 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.119 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.945 ms
After a few minutes or hours of normal use, ping to the router's internal IP starts looking like this:
PING 192.168.1.1 (192.168.1.1): 56 data bytes
Request timeout for icmp_seq 0
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=1558.793 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=557.861 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=990.563 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=90.227 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=108.897 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1051.264 ms
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=3735.454 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=2730.617 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=1729.204 ms
At this point, the router is completely un-usable. It's impossible to use the Internet, and even logging into the router's web interface in order to reboot it is a struggle. Needless to say, I'm about 2 meters away from the router with full line of sight. The router is running the latest official firmware. How can I fix this problem, or even debug it?
