BE800 Keeps rebooting
BE800 Keeps rebooting
I've gone back DOWN to 1.1.4 for firmware trying to troubleshoot this thing. There have been many reddit threads on this, but this seems the better place to ask. I'm seeing reboots of the RE800 every 30 mins or so today. My main question now is is this normal on reboot in the logs:
####################################################################
# Archer BE800 System Log
# Time = 2024-09-09 09:58:06
# H-Ver = 1.0.0 ; S-Ver = 1.1.4 Build 20240520 rel.55974
# LAN: I = 192.168.0.1 ; M = 255.255.0.0 ; MAC = 20:23:51:EB:8D:12
# WAN: W = dhcp ; I = 168.93.45.200 ; M = 255.255.248.0 ; MAC = 20:23:51:EB:8D:13
# G = 168.93.40.1 ; D1 = 74.51.192.1 ; D2 = 74.51.192.2
# Clients connected: 5 ; WI-FI : 4
####################################################################
2024-09-09 09:55:51 upnp[29812]: <6> 217504 Service start
2024-09-09 09:55:51 upnp[29812]: <6> 217505 Service stop
2024-09-09 09:55:51 remote-management[29528]: <6> 282505 Service stop
2024-09-09 09:55:39 qos[26940]: <6> 259504 Service start
2024-09-09 09:55:39 qos[26940]: <6> 259503 Function disabled
2024-09-09 09:55:39 qos[26940]: <6> 259505 Service stop
2024-09-09 09:55:38 nat[26411]: <6> 211501 Initialization succeeded
2024-09-09 09:55:38 nat[26411]: <6> 211501 Initialization succeeded
2024-09-09 09:55:35 dhcpc[25646]: <6> 210054 receive ack from server with ip 168.93.45.200, options(serverid=168.93.40.3;lease=600235;subnet=255.255.248.0;router=168.93.40.1;dns=74.51.192.1 74.51.192.2;)
2024-09-09 09:55:35 dhcpc[25646]: <6> 210053 send select request with options(cliid=01/20:23:51:eb:8d:13:;reqip=168.93.45.200;serverid=168.93.40.2;)
2024-09-09 09:55:35 dhcpc[25646]: <6> 210052 receive offer from server with ip 168.93.45.200, options(serverid=168.93.40.2;lease=600235;subnet=255.255.248.0;router=168.93.40.1;dns=74.51.192.1 74.51.192.2;)
2024-09-09 09:55:35 dhcpc[25646]: <6> 210051 send discover with ip 0.0.0.0 and flags 80
2024-09-09 09:55:32 dhcpc[25646]: <6> 210051 send discover with ip 0.0.0.0 and flags 80
2024-09-09 09:55:26 led-controller[1350]: <6> 288051 Start to run STATUS_ON
2024-09-09 09:55:25 qos[23721]: <6> 259504 Service start
2024-09-09 09:55:25 qos[23721]: <6> 259503 Function disabled
2024-09-09 09:55:25 led-controller[1350]: <6> 288051 Start to run GENERAL
2024-09-09 09:55:24 nat[23049]: <6> 211501 Initialization succeeded
2024-09-09 09:55:24 nat[23049]: <6> 211501 Initialization succeeded
2024-09-09 09:55:24 dhcpc[7216]: <4> 210153 send dhcp release ip 168.93.45.200
2024-09-09 09:55:24 dhcpc[7216]: <6> 210056 teardown and release
2024-09-09 09:55:24 dhcpc[7216]: <6> 210053 send select request with options(cliid=01/20:23:51:eb:8d:13:;)
2024-09-09 09:55:24 dhcpc[7216]: <6> 210058 1/2 lease passed, enter renewing state
2024-05-20 00:00:44 traffic-stats[22002]: <6> 269504 Service start
2024-05-20 00:00:42 factory-reset[21301]: <6> 284504 Service start
2024-05-20 00:00:42 parental-control[20971]: <6> 229504 Service start
2024-05-20 00:00:42 parental-control[20971]: <6> 229502 Function enabled
2024-05-20 00:00:42 access-control[20521]: <6> 239504 Service start
2024-05-20 00:00:42 access-control[20521]: <6> 239503 Function disabled
2024-05-20 00:00:41 nat[18838]: <6> 211021 IPSEC ALG enabled
2024-05-20 00:00:41 nat[18838]: <6> 211021 L2TP ALG enabled
2024-05-20 00:00:41 nat[18838]: <6> 211021 PPTP ALG enabled
2024-05-20 00:00:41 nat[18838]: <6> 211021 SIP ALG enabled
2024-05-20 00:00:41 nat[18838]: <6> 211021 RTSP ALG enabled
2024-05-20 00:00:41 nat[18838]: <6> 211021 H323 ALG enabled
2024-05-20 00:00:41 nat[18838]: <6> 211021 TFTP ALG enabled
2024-05-20 00:00:41 nat[18838]: <6> 211021 FTP ALG enabled
2024-05-20 00:00:40 nat[18838]: <7> 211001 Flush conntrack
2024-05-20 00:00:40 nat[18838]: <6> 211502 Function enabled
2024-05-20 00:00:40 nat[18838]: <5> 211051 Create NAT chain succeeded
2024-05-20 00:00:39 nat[18838]: <6> 211501 Initialization succeeded
2024-05-20 00:00:39 nat[18838]: <6> 211501 Initialization succeeded
2024-05-20 00:00:39 upnp[18490]: <6> 217504 Service start
2024-05-20 00:00:39 upnp[18490]: <6> 217505 Service stop
2024-05-20 00:00:38 remote-management[18073]: <6> 282505 Service stop
2024-05-20 00:00:34 basic-security[16079]: <6> 219504 Service start
2024-05-20 00:00:34 basic-security[16079]: <5> 219606 Flush conntrack table succeeded
2024-05-20 00:00:33 firewall[15117]: <6> 209504 Service start
2024-05-20 00:00:23 dhcpc[7216]: <6> 210054 receive ack from server with ip 168.93.45.200, options(serverid=168.93.40.2;lease=600270;subnet=255.255.248.0;router=168.93.40.1;dns=74.51.192.1 74.51.192.2;)
2024-05-20 00:00:23 dhcpc[7216]: <6> 210053 send select request with options(cliid=01/20:23:51:eb:8d:13:;reqip=168.93.45.200;serverid=168.93.40.2;)
2024-05-20 00:00:23 dhcpc[7216]: <6> 210052 receive offer from server with ip 168.93.45.200, options(serverid=168.93.40.2;lease=600271;subnet=255.255.248.0;router=168.93.40.1;dns=74.51.192.1 74.51.192.2;)
2024-05-20 00:00:21 dhcpc[7216]: <6> 210051 send discover with ip 0.0.0.0 and flags 80
2024-05-20 00:00:18 dhcpc[7216]: <6> 210051 send discover with ip 0.0.0.0 and flags 80
2024-05-20 00:00:15 dhcpc[7216]: <6> 210051 send discover with ip 0.0.0.0 and flags 80
2024-05-20 00:00:05 remote-management[4771]: <6> 282505 Service stop
2024-05-20 00:00:04 dhcpc[4007]: <6> 210056 teardown and release
2024-05-20 00:00:03 dhcpc[4007]: <6> 210051 send discover with ip 0.0.0.0 and flags 80
2024-05-20 00:00:02 imb[2889]: <6> 218507 Daemon connection succeeded
2024-05-20 00:00:02 imb[2889]: <6> 218012 ARP Binding disabled
2024-05-20 00:00:02 imb[2889]: <6> 218506 Config interface initialization succeeded
2024-05-20 00:00:02 imb[2889]: <6> 218501 Initialization succeeded
2024-05-20 00:00:02 upnp[2628]: <6> 217504 Service start
2024-05-20 00:00:02 upnp[2628]: <6> 217505 Service stop
2024-05-20 00:00:02 remote-management[2329]: <6> 282505 Service stop
2024-05-20 00:00:01 dhcpc[2102]: <6> 210056 teardown and release
2024-05-20 00:00:01 dhcpc[2102]: <6> 210051 send discover with ip 0.0.0.0 and flags 80
2024-05-20 00:00:00 led-controller[1350]: <6> 288051 Start to run STATUS_SAN
2024-05-20 00:00:00 time-settings[1418]: <6> 279504 Service start
1970-01-01 00:00:39 led-controller[1350]: <6> 288504 Service start
why does it reset back to 1970 every time? This is the only anonmaly i can find as there are no advanced debugging logs that i have found, though i haven't tried to SSH in yet.
I've turned off all wifi 7 tech and disabled smart connect just in case. It ran for 5 days solid when. moved down to 1.1.4 from 1.1.6 and then today its rebooted itself 5 times already. I'm at a loss.. thanks.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
I've had this problem with the BE550 (that I returned) and the BE800 that I have now.
I was rebooting almost every other hour (very annoying). I had the lasted firmware and contacted TP Link support. They gave me a beta firmware for the BE550, but I still had the issue.
I think I figured out what was causing the reboots/restarts which was to disable the MLO wifi network. I did this 2 days ago and my router hasn't rebooted/restarted since then.
Hope this helps!
- Copy Link
- Report Inappropriate Content
@lolunix I have been fighting with the BE800 since July 2024.
Mesh support as claimed. Nope according to Tplink support My Tplink "mesh" devices are not supported . Even though they are clearly on the supported list and it says ON TH BOX Easymesh compatible. DHCP implementation is broken , I use a 192.168.1.30 to 192.168.4.252 /16 scope. So I use the 1.1 to 1.30 for static WAP / servers. ect. Well those are not valid IPS on my network so to fix it scope is 192.168.1.1 to 192.168.4.252 /16 then I have to use DHCP to reserve those IPS. Then I can go set them to static.
I have 4 WAP all Tplink for compatibility, they each will randomly not allow nodes connecting to that specific WAP SSID to the internet. Even though looking at the IP settings the IP is correct, subnet mask , gateway / router is correct and DNS. Then it just starts working again.
I have had TPlink support on my network . They hve no clue ho to provide support. They had an L1 call me on phone (whom knew nothing about networking at all) while another L3? got on my system poked around and said looks like it works to me. Even after I explained I basically put everything in a basic non mesh mode and changed the scope, I had to force him to go look at the logs. When he finally did , he hit refresh ,,, LOL boom! crash, it does that all the time,
This thing is sooo broken. Im going to be sending it back somehow. A netgear cheap router is more reliable than this thing.. Im done with it. Too many issues to even begin listing. Just an FYI, if any wifi 7 device logs into the wifi, done! They had me take all the new Apple iPhones off the network and my Galaxy 24-ultra. The mesh will not work at all period. That was the last recommendation by support. Don't use the mesh!
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 680
Replies: 14
Voters 0
No one has voted for it yet.