What's new

AC3100 rebooting by itself & random disconnects

  • 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!

walkermom

New Around Here
I've been having problems with my wifi setup for a few weeks now. Mostly to do with random & quick disconnects/connects. My cable modem is bridged to an AC3100 router. There is also another ASUS router used as a repeater. It's been stable for over a year. When these disconnects happen, the lights on the modem & router stay on. I've adjusted settings on the router as suggested on this site. Today, the router randomly rebooted itself, all lights off. Firmware is 3.0.0.4.386_41700 Can somebody help interpret the system log for me? I'm assuming the May 5 dates are when it's in reboot mode and anything that happened prior on Feb 5 would tell a story. TIA

Feb 5 18:37:15 rc_service: httpd 425:notify_rc restart_qos;restart_firewall;
Feb 5 18:37:28 kernel: DROP IN=eth0 OUT= MAC=4c:ed:fb:ae:76:98:00:17:10:9a:96:9c:08:00 SRC=194.147.140.24 DST=173.33.102.7 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=35705 PROTO=TCP SPT=43875 DPT=11339 SEQ=4203725109 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0
Feb 5 18:37:32 kernel: The For ALL DEVICES flag of Prof 1 has been set to ENABLE
Feb 5 18:37:32 kernel: Successfully alloc ctrie: state num=22, mem=352
Feb 5 18:37:32 BWDPI: fun bitmap = 4ff
Feb 5 18:37:32 A.QoS: qos_count=0, qos_check=0
Feb 5 18:37:46 kernel: DROP IN=eth0 OUT= MAC=4c:ed:fb:ae:76:98:00:17:10:9a:96:9c:08:00 SRC=84.38.185.109 DST=173.33.102.7 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=56164 PROTO=TCP SPT=44137 DPT=3392 SEQ=1100656675 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0
Feb 5 18:38:08 kernel: DROP IN=eth0 OUT= MAC=4c:ed:fb:ae:76:98:00:17:10:9a:96:9c:08:00 SRC=194.147.140.88 DST=173.33.102.7 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=38915 PROTO=TCP SPT=40422 DPT=4766 SEQ=1039854746 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0
Feb 5 18:38:15 kernel: htb: htb qdisc 13: is non-work-conserving?
Feb 5 18:38:38 kernel: DROP IN=eth0 OUT= MAC=4c:ed:fb:ae:76:98:00:17:10:9a:96:9c:08:00 SRC=194.147.140.109 DST=173.33.102.7 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=29185 PROTO=TCP SPT=56272 DPT=42704 SEQ=648262358 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0
Feb 5 18:38:45 kernel: DROP IN=eth0 OUT= MAC=4c:ed:fb:ae:76:98:00:17:10:9a:96:9c:08:00 SRC=194.147.140.77 DST=173.33.102.7 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=38191 PROTO=TCP SPT=51630 DPT=7271 SEQ=3974164303 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0
Feb 5 18:38:52 kernel: DROP IN=eth0 OUT= MAC=4c:ed:fb:ae:76:98:00:17:10:9a:96:9c:08:00 SRC=194.147.140.40 DST=173.33.102.7 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=51560 PROTO=TCP SPT=40652 DPT=6666 SEQ=2051781989 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0
Feb 5 18:39:03 rc_service: httpd 425:notify_rc reboot
Feb 5 18:39:05 iTunes: daemon is stoped
Feb 5 18:39:05 FTP Server: daemon is stoped
Feb 5 18:39:05 Samba Server: smb daemon is stoped
Feb 5 18:39:05 kernel: gro disabled
Feb 5 18:39:05 Timemachine: daemon is stoped
Feb 5 18:39:05 WEBDAV Server: daemon is stoped
Feb 5 18:39:08 WEBDAV Server: daemon is stoped
Feb 5 18:39:08 Mastiff: Got SIGTERM
Feb 5 18:39:08 Mastiff: Select error
Feb 5 18:39:08 Mastiff: Got SIGTERM
Feb 5 18:39:08 Mastiff: Got SIGTERM
Feb 5 18:39:09 iTunes: daemon is stoped
Feb 5 18:39:09 FTP Server: daemon is stoped
Feb 5 18:39:09 Samba Server: smb daemon is stoped
Feb 5 18:39:09 kernel: gro disabled
Feb 5 18:39:09 Timemachine: daemon is stoped
Feb 5 18:39:09 disk_monitor: Finish
Feb 5 18:39:09 miniupnpd[683]: shutting down MiniUPnPd
Feb 5 18:39:11 ahs: ===Terminate ahs daemon===
Feb 5 18:39:12 kernel: EMF_ERROR: Interface wds0.1 doesn't exist
Feb 5 18:39:12 kernel: EMF_ERROR: Hooks already unregistered
Feb 5 18:39:12 kernel: EMF_ERROR: Hooks already unregistered
Feb 5 18:39:12 kernel: EMF_ERROR: Interface br0 doesn't exist
Feb 5 18:39:13 lldpd[16066]: cannot get ethtool link information with GLINKSETTINGS (requires 4.9+): Operation not permitted
Feb 5 18:39:13 lldpd[16066]: cannot get ethtool link information with GSET (requires 2.6.19+): Operation not permitted
Feb 5 18:39:15 kernel: EMF_ERROR: Interface br0 doesn't exist
May 5 01:05:05 kernel: klogd started: BusyBox v1.25.1 (2021-01-09 03:26:24 CST)
May 5 01:05:05 kernel: Linux version 2.6.36.4brcmarm (root@asus) (gcc version 4.5.3 (Buildroot 2012.02) ) #1 SMP PREEMPT Sat Jan 9 03:32:26 CST 2021
May 5 01:05
 
Last edited:
I've been having problems with my wifi setup for a few weeks now. Mostly to do with random & quick disconnects/connects. My cable modem is bridged to an AC3100 router. There is also another ASUS router used as a repeater. It's been stable for over a year. When these disconnects happen, the lights on the modem & router stay on. I've adjusted settings on the router as suggested on this site. Today, the router randomly rebooted itself, all lights off. Firmware is 3.0.0.4.386_41700 Can somebody help interpret the system log for me? I'm assuming the May 5 dates are when it's in reboot mode and anything that happened prior on Feb 5 would tell a story. TIA

Feb 5 18:37:15 rc_service: httpd 425:notify_rc restart_qos;restart_firewall;
Feb 5 18:37:28 kernel: DROP IN=eth0 OUT= MAC=4c:ed:fb:ae:76:98:00:17:10:9a:96:9c:08:00 SRC=194.147.140.24 DST=173.33.102.7 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=35705 PROTO=TCP SPT=43875 DPT=11339 SEQ=4203725109 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0
Feb 5 18:37:32 kernel: The For ALL DEVICES flag of Prof 1 has been set to ENABLE
Feb 5 18:37:32 kernel: Successfully alloc ctrie: state num=22, mem=352
Feb 5 18:37:32 BWDPI: fun bitmap = 4ff
Feb 5 18:37:32 A.QoS: qos_count=0, qos_check=0
Feb 5 18:37:46 kernel: DROP IN=eth0 OUT= MAC=4c:ed:fb:ae:76:98:00:17:10:9a:96:9c:08:00 SRC=84.38.185.109 DST=173.33.102.7 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=56164 PROTO=TCP SPT=44137 DPT=3392 SEQ=1100656675 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0
Feb 5 18:38:08 kernel: DROP IN=eth0 OUT= MAC=4c:ed:fb:ae:76:98:00:17:10:9a:96:9c:08:00 SRC=194.147.140.88 DST=173.33.102.7 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=38915 PROTO=TCP SPT=40422 DPT=4766 SEQ=1039854746 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0
Feb 5 18:38:15 kernel: htb: htb qdisc 13: is non-work-conserving?
Feb 5 18:38:38 kernel: DROP IN=eth0 OUT= MAC=4c:ed:fb:ae:76:98:00:17:10:9a:96:9c:08:00 SRC=194.147.140.109 DST=173.33.102.7 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=29185 PROTO=TCP SPT=56272 DPT=42704 SEQ=648262358 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0
Feb 5 18:38:45 kernel: DROP IN=eth0 OUT= MAC=4c:ed:fb:ae:76:98:00:17:10:9a:96:9c:08:00 SRC=194.147.140.77 DST=173.33.102.7 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=38191 PROTO=TCP SPT=51630 DPT=7271 SEQ=3974164303 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0
Feb 5 18:38:52 kernel: DROP IN=eth0 OUT= MAC=4c:ed:fb:ae:76:98:00:17:10:9a:96:9c:08:00 SRC=194.147.140.40 DST=173.33.102.7 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=51560 PROTO=TCP SPT=40652 DPT=6666 SEQ=2051781989 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0
Feb 5 18:39:03 rc_service: httpd 425:notify_rc reboot
Feb 5 18:39:05 iTunes: daemon is stoped
Feb 5 18:39:05 FTP Server: daemon is stoped
Feb 5 18:39:05 Samba Server: smb daemon is stoped
Feb 5 18:39:05 kernel: gro disabled
Feb 5 18:39:05 Timemachine: daemon is stoped
Feb 5 18:39:05 WEBDAV Server: daemon is stoped
Feb 5 18:39:08 WEBDAV Server: daemon is stoped
Feb 5 18:39:08 Mastiff: Got SIGTERM
Feb 5 18:39:08 Mastiff: Select error
Feb 5 18:39:08 Mastiff: Got SIGTERM
Feb 5 18:39:08 Mastiff: Got SIGTERM
Feb 5 18:39:09 iTunes: daemon is stoped
Feb 5 18:39:09 FTP Server: daemon is stoped
Feb 5 18:39:09 Samba Server: smb daemon is stoped
Feb 5 18:39:09 kernel: gro disabled
Feb 5 18:39:09 Timemachine: daemon is stoped
Feb 5 18:39:09 disk_monitor: Finish
Feb 5 18:39:09 miniupnpd[683]: shutting down MiniUPnPd
Feb 5 18:39:11 ahs: ===Terminate ahs daemon===
Feb 5 18:39:12 kernel: EMF_ERROR: Interface wds0.1 doesn't exist
Feb 5 18:39:12 kernel: EMF_ERROR: Hooks already unregistered
Feb 5 18:39:12 kernel: EMF_ERROR: Hooks already unregistered
Feb 5 18:39:12 kernel: EMF_ERROR: Interface br0 doesn't exist
Feb 5 18:39:13 lldpd[16066]: cannot get ethtool link information with GLINKSETTINGS (requires 4.9+): Operation not permitted
Feb 5 18:39:13 lldpd[16066]: cannot get ethtool link information with GSET (requires 2.6.19+): Operation not permitted
Feb 5 18:39:15 kernel: EMF_ERROR: Interface br0 doesn't exist
May 5 01:05:05 kernel: klogd started: BusyBox v1.25.1 (2021-01-09 03:26:24 CST)
May 5 01:05:05 kernel: Linux version 2.6.36.4brcmarm (root@asus) (gcc version 4.5.3 (Buildroot 2012.02) ) #1 SMP PREEMPT Sat Jan 9 03:32:26 CST 2021
May 5 01:05

So, you have current/386 firmware... have you reset it and configured from scratch?

OE
 
No, I'm lazy. That's the next step this weekend I guess, when we're all not wfh. I've never done that when updating the firmware & things have been fine. Is there anything in the log that stands out to you?
 
No, I'm lazy. That's the next step this weekend I guess, when we're all not wfh. I've never done that when updating the firmware & things have been fine. Is there anything in the log that stands out to you?

No, other than it's restarting like you said... not normal, not right.

Here are some references... the reset FAQ explains how the factory default reset works and why it might be relevant, especially if you've upgraded from old 384 to new 386 firmware without a reset.

Reset FAQ
Reset Button/webUI Restore
WPS Button Hard Reset

A factory default reset is the first step to troubleshooting weirdness.

Also, disconnect LAN and USB connections and then add them back later, one at a time while observing the network... maybe the cat has chewed on an Ethernet cable.

OE
 
Thanks. I'm confused by the following:

Factory default reset: before, or after flashing?
Since the goal is to use the NEW default values that are included in the NEW firmware, the factory default reset must be done while the NEW firmware is already flashed. Doing so before flashing will leave you running the OLD default values.

So if I'm understanding this correctly, once I've installed the latest firmware I then do the factory default reset?
 
Thanks. I'm confused by the following:

Factory default reset: before, or after flashing?
Since the goal is to use the NEW default values that are included in the NEW firmware, the factory default reset must be done while the NEW firmware is already flashed. Doing so before flashing will leave you running the OLD default values.

So if I'm understanding this correctly, once I've installed the latest firmware I then do the factory default reset?

Yes. Install, reset, configure from scratch. Do not restore an old/saved configuration since that would restore old defaults.

I prefer to do the webUI Restore with Initialize... it resets and also wipes logged data.

OE
 

Latest threads

Sign Up For SNBForums Daily Digest

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