Archer C80 reboots automatically
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi,
Recently i bought Archer C80 router and i am facing automatic reboot issue fot the same. When it happens, all LED's of Router are turned off and it restarts automatically.
My router is connected to ONU which is connected to fiber cable.
Initially i thought this issue might be due to connection to VPN but it's happening even if its not in use. My connection type is PPPoE and i don't think there is any power supply issue. I tried to trace this issue without much success.
Can you please suggest what can be the issue here?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@Kevin_Z TP Link technical support hasn't been any much helpful.
I was advised for soft reset, hard reset and tweak in settings as below. Despite all these the issue persists (random disappearance of LAN, 2.4GHz, 5GHz and it automatically comes back in a while), I urge that the core product team investigate more to find a solution. The issue started post the last software release in November, so this definitely is a software bug.
Unfortunately if the router cannot even do its basic function of seamlessly providing connectivity(LAN, 2.4GHz, 5GHz) then it fails to meet its purpose. Due to its interruptions to provide a seamless experience, I have moved back to my old router as Archer C80 continues to have issue.
@Kevin_Z in case you have any powers to let the product team know, please share my message to them. Hopefully we can see a fix for this at the earliest.
notes from technical support team: (all of these are implemented but issue persists)
"Also if you are facing internet connectivity issue i.e. wan gets disconnected then we request you to go to Advanced-> Network -> Wan settings and set connection type connection on demand with max idle time 0 and check.
If you are facing wireless dis-connectivity issue we request you to go to Advanced-> Wireless-> Host network and set mode to 11N only and set channel to 1,6,11 alternatively for 2.4 Ghz band and for 5 Ghz band set mode to 802.11Ac only or 802.11N/AC mixed and channel to 36,40,44 alternatively and check."
- Copy Link
- Report Inappropriate Content
Thank you very much for the detailed feedback, the tech team was made aware of your issue, they will likely reach out to you via email to continue to troubleshoot your issue.
- Copy Link
- Report Inappropriate Content
@Kevin_Z The issue persists, but I now have less frequent disconnects. This may not be a best observation but when I reduced MTU size on the router to 1400 from 1480, it slightly helped. But still, I see at least 4-5 disconnects during my work hours.
- Copy Link
- Report Inappropriate Content
I don't actually think the MTU size has anything to do with the router reboots, while it's glad to know this helps. It is suggested to follow it up via email with our engineers directly, they will try to figure this out, thanks.
- Copy Link
- Report Inappropriate Content
@Kevin_Z I'm facing the same issue with same firmware version. Just bought the router today and upgraded to latest firmware as prompted in router interface. Router is rebooting randomly. Working on PPPoE connection. If any fix has been found, kindly suggest.
- Copy Link
- Report Inappropriate Content
Kindly check all the details, then we will try to investigate this.
Kevin_Z wrote
Hello, thanks for reporting the issue but please provide some details about the auto-reboot issue then we will try to investigate and offer a solution ASAP.
When the router restarts, are all the LEDs turn off then on automatically and the internet on it will temporarily down then recover? How long does this process take?
May I have your network layout, how is the C80 connected to your network? Are there any other range extenders or switch in the network? If yes, try to remove it first and confirm again.
Who is your ISP and what kind of modem are you using? Is it a Dynamic IP setup on the C80 WAN or PPPoE?
How many devices are connected to C80, wired, and wirelessly? What are they? Is there any new device connected to the C80 network recently when the C80 begins to reboot? Or did you upgrade any system in the network before this issue happen?
Is there any other setting or feature in your network that may cause this restart issue, or is there any special operation/activity in your network that causes the C80 to restart, such as high loading or real-time calls?
Is it the original power adapter on the C80? Is the power stable in your house? How about other electrical devices in your house, are they stable?
Does this issue happen when you purchased it or happens recently? Try to reset the router to factory defaults and reconfigure it from scratch, then confirm again.
- Copy Link
- Report Inappropriate Content
@Kevin_Z , I am facing same issue. I updated latest firmware yesterday and it is really annoying. Please get BETA firmware asap from your developers.
- Copy Link
- Report Inappropriate Content
Can you please help provide the above details, which will help our developers to analyze the issue?
- Copy Link
- Report Inappropriate Content
I have similar issues and I didn't want to hijack Your thread, so I made new one - https://community.tp-link.com/en/home/forum/topic/256444?page=1
As newer firmware (version 1.4.7 versus 1.5.3) does not fix the problem, then it must be the hardware problem. The local dealer said the diagnosis would take three weeks. :(
- Copy Link
- Report Inappropriate Content
Sorry, I step in and answer the questions from my perspective as I have same issue, also please read about my Archer C80 crashing issue/details - https://community.tp-link.com/en/home/forum/topic/256444?page=1
Q: When the router restarts, are all the LEDs turn off then on automatically and the internet on it will temporarily down then recover? How long does this process take?
A: As my device is located away in storage room, I can't see the LED-s. Adding latest 4G router gateway ping results, there You can see the timestamps:
Mar 09 21:15:16 64 bytes from 192.168.18.1: icmp_seq=737 ttl=63 time=1.291 ms
Mar 09 21:15:17 64 bytes from 192.168.18.1: icmp_seq=738 ttl=63 time=1.254 ms
Mar 09 21:15:18 64 bytes from 192.168.18.1: icmp_seq=739 ttl=63 time=1.330 ms
Mar 09 21:15:19 64 bytes from 192.168.18.1: icmp_seq=740 ttl=63 time=1.246 ms
Mar 09 21:15:20 64 bytes from 192.168.18.1: icmp_seq=741 ttl=63 time=1.435 ms
Mar 09 21:15:21 64 bytes from 192.168.18.1: icmp_seq=742 ttl=63 time=1.334 ms
Mar 09 21:15:22 64 bytes from 192.168.18.1: icmp_seq=743 ttl=63 time=1.364 ms
Mar 09 21:15:23 64 bytes from 192.168.18.1: icmp_seq=744 ttl=63 time=1.444 ms
Mar 09 21:15:24 64 bytes from 192.168.18.1: icmp_seq=745 ttl=63 time=265.297 ms
Mar 09 21:15:25 64 bytes from 192.168.18.1: icmp_seq=746 ttl=63 time=1.365 ms
Mar 09 21:15:26 64 bytes from 192.168.18.1: icmp_seq=747 ttl=63 time=268.086 ms
Mar 09 21:15:27 64 bytes from 192.168.18.1: icmp_seq=748 ttl=63 time=61.443 ms
Mar 09 21:15:28 64 bytes from 192.168.18.1: icmp_seq=749 ttl=63 time=1.394 ms
Mar 09 21:15:29 64 bytes from 192.168.18.1: icmp_seq=750 ttl=63 time=1.241 ms
Mar 09 21:15:30 64 bytes from 192.168.18.1: icmp_seq=751 ttl=63 time=1.380 ms
Mar 09 21:15:31 64 bytes from 192.168.18.1: icmp_seq=752 ttl=63 time=1.392 ms
Mar 09 21:15:32 64 bytes from 192.168.18.1: icmp_seq=753 ttl=63 time=1.345 ms
Mar 09 21:15:33 64 bytes from 192.168.18.1: icmp_seq=754 ttl=63 time=1.414 ms
Mar 09 21:15:34 64 bytes from 192.168.18.1: icmp_seq=755 ttl=63 time=1.414 ms
Mar 09 21:15:35 64 bytes from 192.168.18.1: icmp_seq=756 ttl=63 time=1.368 ms
Mar 09 21:15:36 64 bytes from 192.168.18.1: icmp_seq=757 ttl=63 time=1.411 ms
Mar 09 21:15:37 64 bytes from 192.168.18.1: icmp_seq=758 ttl=63 time=1.321 ms
Mar 09 21:15:38 64 bytes from 192.168.18.1: icmp_seq=759 ttl=63 time=1.456 ms
Mar 09 21:15:39 64 bytes from 192.168.18.1: icmp_seq=760 ttl=63 time=1.750 ms
Mar 09 21:15:41 Request timeout for icmp_seq 761
Mar 09 21:15:41 64 bytes from 192.168.18.1: icmp_seq=761 ttl=63 time=1611.242 ms
Mar 09 21:15:41 64 bytes from 192.168.18.1: icmp_seq=762 ttl=63 time=621.861 ms
Mar 09 21:15:43 64 bytes from 192.168.18.1: icmp_seq=763 ttl=63 time=1600.220 ms
Mar 09 21:15:44 64 bytes from 192.168.18.1: icmp_seq=764 ttl=63 time=1195.027 ms
Mar 09 21:15:44 64 bytes from 192.168.18.1: icmp_seq=765 ttl=63 time=492.485 ms
Mar 09 21:15:45 64 bytes from 192.168.18.1: icmp_seq=766 ttl=63 time=299.102 ms
Mar 09 21:15:46 64 bytes from 192.168.18.1: icmp_seq=767 ttl=63 time=180.775 ms
Mar 09 21:15:47 64 bytes from 192.168.18.1: icmp_seq=768 ttl=63 time=309.105 ms
Mar 09 21:15:48 64 bytes from 192.168.18.1: icmp_seq=769 ttl=63 time=251.371 ms
Mar 09 21:15:49 64 bytes from 192.168.18.1: icmp_seq=770 ttl=63 time=153.203 ms
Mar 09 21:15:50 64 bytes from 192.168.18.1: icmp_seq=771 ttl=63 time=209.407 ms
Mar 09 21:15:51 64 bytes from 192.168.18.1: icmp_seq=772 ttl=63 time=95.254 ms
Mar 09 21:15:52 64 bytes from 192.168.18.1: icmp_seq=773 ttl=63 time=233.129 ms
Mar 09 21:15:53 64 bytes from 192.168.18.1: icmp_seq=774 ttl=63 time=148.220 ms
Mar 09 21:15:54 64 bytes from 192.168.18.1: icmp_seq=775 ttl=63 time=23.182 ms
Mar 09 21:15:55 64 bytes from 192.168.8192.168.10.1.1: icmp_seq=776 ttl=63 time=1.264 ms
Mar 09 21:15:56 64 bytes from 192.168.18.1: icmp_seq=777 ttl=63 time=64.944 ms
Mar 09 21:15:57 64 bytes from 192.168.18.1: icmp_seq=778 ttl=63 time=44.135 ms
Mar 09 21:15:58 64 bytes from 192.168.18.1: icmp_seq=779 ttl=63 time=52.760 ms
Mar 09 21:15:59 64 bytes from 192.168.18.1: icmp_seq=780 ttl=63 time=76.695 ms
Mar 09 21:16:00 64 bytes from 192.168.18.1: icmp_seq=781 ttl=63 time=35.823 ms
Mar 09 21:16:01 64 bytes from 192.168.18.1: icmp_seq=782 ttl=63 time=70.023 ms
Mar 09 21:16:02 64 bytes from 192.168.18.1: icmp_seq=783 ttl=63 time=58.113 ms
Mar 09 21:16:03 64 bytes from 192.168.18.1: icmp_seq=784 ttl=63 time=95.002 ms
Mar 09 21:16:04 64 bytes from 192.168.18.1: icmp_seq=785 ttl=63 time=78.392 ms
Mar 09 21:16:05 64 bytes from 192.168.18.1: icmp_seq=786 ttl=63 time=71.580 ms
Mar 09 21:16:06 64 bytes from 192.168.18.1: icmp_seq=787 ttl=63 time=75.077 ms
Mar 09 21:16:07 64 bytes from 192.168.18.1: icmp_seq=788 ttl=63 time=97.347 ms
Mar 09 21:16:08 64 bytes from 192.168.18.1: icmp_seq=789 ttl=63 time=1.828 ms
Mar 09 21:16:09 64 bytes from 192.168.18.1: icmp_seq=790 ttl=63 time=114.246 ms
Mar 09 21:16:10 64 bytes from 192.168.18.1: icmp_seq=791 ttl=63 time=136.491 ms
Mar 09 21:16:11 64 bytes from 192.168.18.1: icmp_seq=792 ttl=63 time=94.658 ms
Mar 09 21:16:12 64 bytes from 192.168.18.1: icmp_seq=793 ttl=63 time=89.945 ms
Mar 09 21:16:13 64 bytes from 192.168.18.1: icmp_seq=794 ttl=63 time=1.410 ms
Mar 09 21:16:14 64 bytes from 192.168.18.1: icmp_seq=795 ttl=63 time=1.412 ms
Mar 09 21:16:15 64 bytes from 192.168.18.1: icmp_seq=796 ttl=63 time=1.339 ms
Q: May I have your network layout, how is the C80 connected to your network? Are there any other range extenders or switch in the network? If yes, try to remove it first and confirm again.
A: Network is very simple, Huawei B535-232 4G router > LAN > C80 (192.168.10.0/24) > WiFi 2,4 & 5 Ghz & LAN.
Q: Who is your ISP and what kind of modem are you using? Is it a Dynamic IP setup on the C80 WAN or PPPoE?
A: Local mobile operator, Huawei B535-232 4G router, static IP.
Q: How many devices are connected to C80, wired, and wirelessly? What are they? Is there any new device connected to the C80 network recently when the C80 begins to reboot? Or did you upgrade any system in the network before this issue happen?
A: Total less then 10 devices, 3 LAN and rest WiFi users, no local NAS etc, so traffic is 100% towards to the Internet. Apple phones and desktops, PS4, Lenovo etc. No new devices. No upgrades.
Q: Is there any other setting or feature in your network that may cause this restart issue, or is there any special operation/activity in your network that causes the C80 to restart, such as high loading or real-time calls?
A: No.
Q: Is it the original power adapter on the C80? Is the power stable in your house? How about other electrical devices in your house, are they stable?
A: Original. Power is stable and also all other devices are stable.
Q: Does this issue happen when you purchased it or happens recently? Try to reset the router to factory defaults and reconfigure it from scratch, then confirm again.
A: Bought brand new item 4 day's ago. Happens all the time. Reset does not help.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 6012
Replies: 42
Voters 2
