Menu
What's new
By:
Filters Better Search

RT-AC87R AC2400 Random Reboots

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

kryptto

kryptto

Regular Contributor
Good day all,

I am experiencing random reboots from my router. I am going to include as much relevant info I can, and happily will answer questions I can when asked.

Symptoms: Random reboots, cant pin to any one network function being performed. Since I work from home, these reboots are really noticeable when I lose my corp VPN, and all my apps stop working. I know its a reboot I sit in front of it, lose switch connectivity to other devices. Attached hard drive, that works fine and is brand new reboots as well. Definitely going through a POST.

Logs are below:

Running the latest 380.69
Has been happening randomly for a few firmware upgrades so NOT particular to this one.
Currently using DMZplus or bridged with the AT&T 5268AC gateway.

It looks like the log is telling me my hard drive has an issue, would that be causing my reboots, or is there something else I am missing?

Jan 9 08:28:16 rc_service: ntp 1070:notify_rc restart_upnp
Jan 9 08:28:17 kernel: tfat: fail_safe is enabled
Jan 9 08:28:17 kernel: tfat: cluster_heap_lbo 0x7474800
Jan 9 08:28:17 kernel: tfat: 11 blkbits for normal inodes
Jan 9 08:28:17 kernel: tfat: fat start lbo 0x4000
Jan 9 08:28:17 kernel: tfat: 10 blkbits for main FAT32 inode
Jan 9 08:28:17 kernel: tfat: cluster size 65536
Jan 9 08:28:19 kernel: tfat info: FAT32 volume name 'ASUS-AI', version 0.0.
Jan 9 08:28:19 kernel: tfat warning (device sda1, pid 1085): fat_fill_super(): FAT volume ASUS-AI is dirty. You should unmount and repair it.
Jan 9 08:28:19 hotplug[1074]: USB vfat fs at /dev/sda1 mounted on /tmp/mnt/ASUS-AI
Jan 9 08:28:19 usb: USB vfat fs at /dev/sda1 mounted on /tmp/mnt/ASUS-AI.
Jan 9 08:28:19 miniupnpd[1071]: shutting down MiniUPnPd
Jan 9 08:28:19 miniupnpd[1096]: HTTP listening on port 46963
Jan 9 08:28:19 miniupnpd[1096]: Listening for NAT-PMP/PCP traffic on port 5351
Jan 9 08:28:19 rc_service: ntp 1070:notify_rc restart_diskmon
Jan 9 08:28:20 disk_monitor: Finish
Jan 9 08:28:20 rc_service: udhcpc 617:notify_rc start_vpnserver1
Jan 9 08:28:20 rc_service: waitting "restart_diskmon" via ntp ...
Jan 9 08:28:20 rc_service: hotplug 1074:notify_rc restart_nasapps
Jan 9 08:28:20 iTunes: daemon is stopped
Jan 9 08:28:20 FTP_Server: daemon is stopped
Jan 9 08:28:21 Samba_Server: smb daemon is stopped
Jan 9 08:28:21 kernel: gro disabled
Jan 9 08:28:21 disk_monitor: be idle
Jan 9 08:28:21 Timemachine: daemon is stopped
Jan 9 08:28:21 miniupnpd[1096]: shutting down MiniUPnPd
Jan 9 08:28:21 kernel: gro enabled with interval 2
Jan 9 08:28:22 crond[486]: time disparity of 1285287 minutes detected
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPREQUEST(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPACK(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPREQUEST(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPACK(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPREQUEST(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPACK(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 Samba_Server: daemon is started
Jan 9 08:28:23 kernel: RPC: Registered udp transport module.
Jan 9 08:28:23 kernel: RPC: Registered tcp transport module.
Jan 9 08:28:23 kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
Jan 9 08:28:24 kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Jan 9 08:28:24 statd[1156]: Version 1.1.6 Starting
Jan 9 08:28:24 statd[1156]: statd running as root. chown /var/lib/nfs/sm to choose different user
Jan 9 08:28:24 kernel: svc: failed to register lockdv1 RPC service (errno 97).
Jan 9 08:28:25 qtn: bootcfg.tgz exists
Jan 9 08:28:25 miniupnpd[1178]: HTTP listening on port 41957
Jan 9 08:28:25 miniupnpd[1178]: Listening for NAT-PMP/PCP traffic on port 5351
Jan 9 08:28:27 kernel: tun: Universal TUN/TAP device driver, 1.6
Jan 9 08:28:27 kernel: tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jan 9 08:28:28 ddns_update: ez-ipupdate: starting...
Jan 9 08:28:28 ddns_update: connected to updates.dnsomatic.com (67.215.92.215) on port 80.
Jan 9 08:28:28 kernel: ADDRCONF(NETDEV_UP): tun21: link is not ready
Jan 9 08:28:28 kernel: device tun21 entered promiscuous mode
Jan 9 08:28:29 ddns_update: request successful
Jan 9 08:28:29 ddns_update: asusddns_update: 0
Jan 9 08:28:29 ddns: ddns update ok
 
kryptto said:
Good day all,

I am experiencing random reboots from my router. I am going to include as much relevant info I can, and happily will answer questions I can when asked.

Symptoms: Random reboots, cant pin to any one network function being performed. Since I work from home, these reboots are really noticeable when I lose my corp VPN, and all my apps stop working. I know its a reboot I sit in front of it, lose switch connectivity to other devices. Attached hard drive, that works fine and is brand new reboots as well. Definitely going through a POST.

Logs are below:

Running the latest 380.69
Has been happening randomly for a few firmware upgrades so NOT particular to this one.
Currently using DMZplus or bridged with the AT&T 5268AC gateway.

It looks like the log is telling me my hard drive has an issue, would that be causing my reboots, or is there something else I am missing?

Jan 9 08:28:16 rc_service: ntp 1070:notify_rc restart_upnp
Jan 9 08:28:17 kernel: tfat: fail_safe is enabled
Jan 9 08:28:17 kernel: tfat: cluster_heap_lbo 0x7474800
Jan 9 08:28:17 kernel: tfat: 11 blkbits for normal inodes
Jan 9 08:28:17 kernel: tfat: fat start lbo 0x4000
Jan 9 08:28:17 kernel: tfat: 10 blkbits for main FAT32 inode
Jan 9 08:28:17 kernel: tfat: cluster size 65536
Jan 9 08:28:19 kernel: tfat info: FAT32 volume name 'ASUS-AI', version 0.0.
Jan 9 08:28:19 kernel: tfat warning (device sda1, pid 1085): fat_fill_super(): FAT volume ASUS-AI is dirty. You should unmount and repair it.
Jan 9 08:28:19 hotplug[1074]: USB vfat fs at /dev/sda1 mounted on /tmp/mnt/ASUS-AI
Jan 9 08:28:19 usb: USB vfat fs at /dev/sda1 mounted on /tmp/mnt/ASUS-AI.
Jan 9 08:28:19 miniupnpd[1071]: shutting down MiniUPnPd
Jan 9 08:28:19 miniupnpd[1096]: HTTP listening on port 46963
Jan 9 08:28:19 miniupnpd[1096]: Listening for NAT-PMP/PCP traffic on port 5351
Jan 9 08:28:19 rc_service: ntp 1070:notify_rc restart_diskmon
Jan 9 08:28:20 disk_monitor: Finish
Jan 9 08:28:20 rc_service: udhcpc 617:notify_rc start_vpnserver1
Jan 9 08:28:20 rc_service: waitting "restart_diskmon" via ntp ...
Jan 9 08:28:20 rc_service: hotplug 1074:notify_rc restart_nasapps
Jan 9 08:28:20 iTunes: daemon is stopped
Jan 9 08:28:20 FTP_Server: daemon is stopped
Jan 9 08:28:21 Samba_Server: smb daemon is stopped
Jan 9 08:28:21 kernel: gro disabled
Jan 9 08:28:21 disk_monitor: be idle
Jan 9 08:28:21 Timemachine: daemon is stopped
Jan 9 08:28:21 miniupnpd[1096]: shutting down MiniUPnPd
Jan 9 08:28:21 kernel: gro enabled with interval 2
Jan 9 08:28:22 crond[486]: time disparity of 1285287 minutes detected
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPDISCOVER(br0) 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPOFFER(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPREQUEST(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPACK(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPREQUEST(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPACK(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPREQUEST(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 dnsmasq-dhcp[477]: DHCPACK(br0) 192.168.2.37 44:61:32:84:06:b1
Jan 9 08:28:23 Samba_Server: daemon is started
Jan 9 08:28:23 kernel: RPC: Registered udp transport module.
Jan 9 08:28:23 kernel: RPC: Registered tcp transport module.
Jan 9 08:28:23 kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
Jan 9 08:28:24 kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Jan 9 08:28:24 statd[1156]: Version 1.1.6 Starting
Jan 9 08:28:24 statd[1156]: statd running as root. chown /var/lib/nfs/sm to choose different user
Jan 9 08:28:24 kernel: svc: failed to register lockdv1 RPC service (errno 97).
Jan 9 08:28:25 qtn: bootcfg.tgz exists
Jan 9 08:28:25 miniupnpd[1178]: HTTP listening on port 41957
Jan 9 08:28:25 miniupnpd[1178]: Listening for NAT-PMP/PCP traffic on port 5351
Jan 9 08:28:27 kernel: tun: Universal TUN/TAP device driver, 1.6
Jan 9 08:28:27 kernel: tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jan 9 08:28:28 ddns_update: ez-ipupdate: starting...
Jan 9 08:28:28 ddns_update: connected to updates.dnsomatic.com (67.215.92.215) on port 80.
Jan 9 08:28:28 kernel: ADDRCONF(NETDEV_UP): tun21: link is not ready
Jan 9 08:28:28 kernel: device tun21 entered promiscuous mode
Jan 9 08:28:29 ddns_update: request successful
Jan 9 08:28:29 ddns_update: asusddns_update: 0
Jan 9 08:28:29 ddns: ddns update ok
Click to expand...
 
fatfsck 3014.9.11
Checking boot region...
Checking fsinfo region...
Checking FAT tables...
Checking root directory...
Checking directory structure and allocations...
Checking FAT table allocation...
Using 10/15259992 clusters.
Clearing dirty flag...
Repair finished with no repaired inconsistencies.
File system is clean.
 
I'm experiencing the same with RT-AC87U. I have my IPTV routed through and it just hanged twice so far. Once happened while I was on a PC.
 
I also have had many random reboots since I got the router RT-AC87U Oct 2016.
I’ve had reboots sometimes a couple of times/week and sometimes several/day.
But I think it is now fixed!
I now have 12 day uptime which is best ever.
I have been playing with many different settings and firmwares the last year. Cannot remember if I ever made a factory reset.

Not sure what fixed it. what I did was:
1. I first made factory reset of the router and set it up again from scratch (not using a backup settings file).
2. Then I found and read the below thread and installed the test firmware 380.69_1 (a download link can be found in the thread under reply #11). Did not make a new factory reset after updating to this one.

https://www.snbforums.com/threads/rt-ac87u-reboot-when-netword-is-satured.42908/
 
Last edited:
OlaP said:
I also have had many random reboots since I got the router RT-AC87U Oct 2016.
I’ve had reboots sometimes a couple of times/week and sometimes several/day.
But I think it is now fixed!
I now have 12 day uptime which is best ever.
I have been playing with many different settings and firmwares the last year. Cannot remember if I ever made a factory reset.

Not sure what fixed it. what I did was:
1. I first made factory reset of the router and set it up again from scratch (not using a backup settings file).
2. Then I found and read the below thread and installed the test firmware 380.69_1 (a download link can be found in the thread under reply #11). Did not make a new factory reset after updating to this one.

https://www.snbforums.com/threads/rt-ac87u-reboot-when-netword-is-satured.42908/
Click to expand...

I will try this out, still looking for any other input as well. Thanks OlaP
 
Can I assume that the fix for this reboot will arrive in an update post 380.69 ? I'm not in a mood to install a test firmware...
 
RMerlin said:
Device Discovery has nothing to do with the firmware.
Click to expand...

- Increase stability and removed vulnerable driver. This was what I was thinking, I am hard resetting and seeing if there is better stability with reboots. No loading previous settings etc. Gonna stay with as many defaults as possible etc. Could be my hardware dont know.
 
try disable email notification in aiprotection settings (if you use this)
 
VANT said:
try disable email notification in aiprotection settings (if you use this)
Click to expand...

Never had that enabled, but appreciate the advise.

***UPDATE*** Performed a Hard Reset manually set my settings. NOT all items configured like my USB hard drive and portal, taking baby steps. SO for now up 4 hours no issues with reboots or dropping wireless.
 
Two damn reboots in 1 day. Went back to stock latest ASUS for RT-AC87U and its doing the same thing. What the frigging hell?! This is annoying as hell. Want to do something on my latop and the damn net disappears and then I have to wait like 2 minutes for it to come back online.
 
RejZoR said:
Two damn reboots in 1 day. Went back to stock latest ASUS for RT-AC87U and its doing the same thing. What the frigging hell?! This is annoying as hell. Want to do something on my latop and the damn net disappears and then I have to wait like 2 minutes for it to come back online.
Click to expand...

SOOO, I have been out buying and returning Asus latest routers.... BUT yesterday I saw this article in my newsfeed: https://www.theverge.com/2018/1/16/16897426/wi-fi-google-home-chromecast-archer-router

THEN searched here in these forums and found this: https://www.snbforums.com/threads/chromecast-might-be-causing-connectivity-issues.43924/#post-373043

Hopefully these are all related I happen to have 2 chromecast and 2 google home speakers. I am leaving them OFF my network for now.

ALSO when testing the ASUS AC5300 ROG and ASUS AC88R I was having huge issues joining those google cast/speaker devices to the wireless, constantly throwing an error about AP Isolation being set... to be honest I am sure its just a wireless setting that needs to be tweaked according to this: https://productforums.google.com/forum/#!topic/chromecast/pzpgXAtuDZ0

Nonetheless, I am rambling.... if you have a Google device like an Assistant or Chromecast, these might be our culprits.

I returned the AC5300 ROG, according to Merlin the processor is not the same used for the rest of their lines.

The AC88 was a dud, wouldnt boot the wireless on startup. Just the power light and nothing loaded. I had a hard reset work, but after a reboot would cause it post to power light then die.
 
I don't. I got 1x PC, 2x laptop, 1x SmartTV and 1x IPTV setup box. I don't use any "assistants". I've gone back to stock ASUS firmware and haven't had a single reboot for couple of days now...
 
Looks like these reboots might be addressed in this release: 380_69.2

- CHANGED: Quantenna watchdog is less likely now to
incorrectly assume the QTN CPU has crashed
(which can lead to router reboots). (RT-AC87U)

Thanks Eric!
 
Last edited:
Is it possible that having 5GHz radio disabled affects the stability? I have no purpose for 5GHz since it has garbage range so I keep it disabled.
 
You must log in or register to reply here.

Similar threads

C
Router trouble RT-AX88U
Replies
11
Views
2K
Srekcus49
S
P
Skynet show inbound block on Digital TV Vlan300
Replies
4
Views
928
poudenes
P
W
RT-AX86U with latest version 3004.388.8_2 always crash and reboot
2
Replies
35
Views
4K
Ripshod
Ripshod
P
Issues with RT-AX92U running 388.2_2_0-gnuton1
Replies
6
Views
2K
tom.moughan
T
M
Time not sequential in log since upgrade to 386.4
Replies
9
Views
2K
ColinTaylor
C
Similar threads
Thread starter Title Forum Replies Date
fafot Solved Constant Apple Home random disconnections Asuswrt-Merlin 2
B FYI: AM 386.12 on AC86u - how to decrease # of random reboots Asuswrt-Merlin 4

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Total: 662 (members: 26, guests: 636)
Top