What's new

Asus AC66U goes down under load

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

helprouterbad11

New Around Here
My asus AC66U_B1 keeps going down around the same time when more people come home from work around 8-9pm. It works fine when I'm at home by myself.

Here's the log below. I've updated to the latest Merlin firmware, checked the cable, but I'm having no luck Thanks in advance.

Aug 1 00:00:20 RT-AC66U_B1: start httpd
Aug 1 00:00:21 kernel: gro enabled with interval 2
Aug 1 00:00:21 disk_monitor: be idle
Aug 1 00:00:21 hour_monitor: daemon is starting
Aug 1 00:00:21 hour_monitor: daemon terminates
Aug 1 00:00:23 Samba_Server: daemon is started
Aug 1 00:00:23 jffs2: valid logs(1)
Aug 1 00:00:24 rc_service: udhcpc 551:notify_rc start_firewall
Aug 1 00:00:24 rc_service: udhcpc 551:notify_rc stop_upnp
Aug 1 00:00:24 rc_service: waitting "start_firewall" via udhcpc ...
Aug 1 00:00:24 WAN_Connection: WAN was restored.
Aug 1 00:00:26 kernel: SCSI subsystem initialized
Aug 1 00:00:26 kernel: csw_retry 100
Aug 1 00:00:29 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Aug 1 00:00:30 kernel: nf_conntrack_rtsp v0.6.21 loading
Aug 1 00:00:30 kernel: nf_nat_rtsp v0.6.21 loading
Aug 1 00:00:30 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Aug 1 00:00:31 rc_service: udhcpc 551:notify_rc start_upnp
Aug 1 00:00:31 rc_service: waitting "stop_upnp" via udhcpc ...
Aug 1 00:00:32 dhcp_client: bound 192.168.1.2 via 192.168.1.1 during 86400 seconds.
Aug 1 00:00:33 miniupnpd[802]: HTTP listening on port 51684
Aug 1 00:00:33 miniupnpd[802]: Listening for NAT-PMP/PCP traffic on port 5351
Aug 1 00:00:34 ntp: start NTP update
Jun 7 01:13:33 rc_service: ntp 800:notify_rc restart_upnp
Jun 7 01:13:33 miniupnpd[802]: shutting down MiniUPnPd
Jun 7 01:13:33 miniupnpd[816]: HTTP listening on port 43980
Jun 7 01:13:33 miniupnpd[816]: Listening for NAT-PMP/PCP traffic on port 5351
Jun 7 01:13:34 rc_service: ntp 800:notify_rc restart_diskmon
Jun 7 01:13:34 disk_monitor: Finish
Jun 7 01:13:36 disk_monitor: be idle
Jun 7 01:13:59 crond[479]: time disparity of 2024713 minutes detected
Jun 7 02:00:36 disk_monitor: Got SIGALRM...
Jun 7 13:13:31 ntp: start NTP update
Jun 7 23:00:36 disk_monitor: Got SIGALRM...
Jun 8 01:13:28 ntp: start NTP update
Jun 8 01:52:10 WAN_Connection: Ethernet link down.
Jun 8 01:52:10 DualWAN: skip single wan wan_led_control - WANRED off
Jun 8 01:52:10 stop_nat_rules: apply the redirect_rules!
Jun 8 01:52:21 WAN_Connection: Ethernet link up.
Jun 8 01:52:21 rc_service: wanduck 453:notify_rc restart_wan_if 0
Jun 8 01:52:21 kernel: Attempt to kill tasklet from interrupt
Jun 8 01:52:21 miniupnpd[816]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Jun 8 01:52:21 miniupnpd[816]: Failed to get IP for interface eth0
Jun 8 01:52:21 miniupnpd[816]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Jun 8 01:52:25 WAN_Connection: ISP's DHCP did not function properly.
Jun 8 01:52:31 WAN_Connection: Ethernet link down.
Jun 8 01:52:35 WAN_Connection: Ethernet link up.
Jun 8 01:52:35 rc_service: wanduck 453:notify_rc restart_wan_if 0
Jun 8 01:52:35 kernel: Attempt to kill tasklet from interrupt
Jun 8 01:52:40 WAN_Connection: ISP's DHCP did not function properly.
Jun 8 01:55:28 rc_service: udhcpc 23792:notify_rc start_firewall
Jun 8 01:55:29 miniupnpd[816]: shutting down MiniUPnPd
Jun 8 01:55:29 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jun 8 01:55:30 rc_service: udhcpc 23792:notify_rc stop_upnp
Jun 8 01:55:30 rc_service: waitting "start_firewall" via udhcpc ...
Jun 8 01:55:30 miniupnpd[23828]: HTTP listening on port 42773
Jun 8 01:55:30 miniupnpd[23828]: Listening for NAT-PMP/PCP traffic on port 5351
Jun 8 01:55:30 WAN_Connection: WAN was restored.
Jun 8 01:55:31 rc_service: udhcpc 23792:notify_rc start_upnp
Jun 8 01:55:31 rc_service: waitting "stop_upnp" via udhcpc ...
Jun 8 01:55:31 miniupnpd[23828]: shutting down MiniUPnPd
Jun 8 01:55:32 ntp: start NTP update
Jun 8 01:55:32 dhcp_client: bound 192.168.1.2 via 192.168.1.1 during 86400 seconds.
Jun 8 01:55:34 miniupnpd[23835]: HTTP listening on port 45806
Jun 8 01:55:34 miniupnpd[23835]: Listening for NAT-PMP/PCP traffic on port 5351
Jun 8 02:26:16 WAN_Connection: Ethernet link down.
Jun 8 02:26:16 DualWAN: skip single wan wan_led_control - WANRED off
Jun 8 02:26:16 stop_nat_rules: apply the redirect_rules!
Jun 8 02:26:27 WAN_Connection: Ethernet link up.
Jun 8 02:26:27 rc_service: wanduck 453:notify_rc restart_wan_if 0
Jun 8 02:26:27 kernel: Attempt to kill tasklet from interrupt
Jun 8 02:26:27 miniupnpd[23835]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Jun 8 02:26:27 miniupnpd[23835]: Failed to get IP for interface eth0
Jun 8 02:26:27 miniupnpd[23835]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Jun 8 02:26:31 WAN_Connection: ISP's DHCP did not function properly.
Jun 8 02:29:19 rc_service: udhcpc 24423:notify_rc start_firewall
Jun 8 02:29:20 miniupnpd[23835]: shutting down MiniUPnPd
Jun 8 02:29:20 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jun 8 02:29:21 rc_service: udhcpc 24423:notify_rc stop_upnp
Jun 8 02:29:21 rc_service: waitting "start_firewall" via udhcpc ...
Jun 8 02:29:21 miniupnpd[24459]: HTTP listening on port 47068
Jun 8 02:29:21 miniupnpd[24459]: Listening for NAT-PMP/PCP traffic on port 5351
Jun 8 02:29:22 rc_service: udhcpc 24423:notify_rc start_upnp
Jun 8 02:29:22 rc_service: waitting "stop_upnp" via udhcpc ...
Jun 8 02:29:22 miniupnpd[24459]: shutting down MiniUPnPd
Jun 8 02:29:22 WAN_Connection: WAN was restored.
 
How many people?

How many devices are on each band?
 
Your log only covers one 24 hour period and contains no errors (or any other messages) around 8-9pm. The Asus appears to be connected to another router at 192.168.1.1 so I would look at that device for any problems.
 
Your log only covers one 24 hour period and contains no errors (or any other messages) around 8-9pm. The Asus appears to be connected to another router at 192.168.1.1 so I would look at that device for any problems.

Yes it's a Fios modem that's connected to the Asus router.

There are around 2-3 more people that come home when the internet seems to come down.

I'm not sure on the how many devices are on each band as I'm not too tech savvy.
 
Yes it's a Fios modem that's connected to the Asus router.
Like I said, check out the log files on the Fios device. I suspect that is where the problem is.

Also, can you just confirm that your LAN IP address range (on the Asus) is not the same as the Fios device? i.e. it is not 192.168.1.x.
 
try power off modem at 5am for 30min., maybe public IP changes at this time and can be shifted
 
Thank you guys for your help.

The Fios log said this:

Jun 9 09:10:24 2019 System Log WAN Coax WAN Coax Link Rate <TX 224Mbps/RX 237Mbps>
Jun 9 09:07:18 2019 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.3, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Wireless)
Jun 9 09:06:55 2019 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.2, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Jun 9 09:06:09 2019 System Log WAN Coax WAN Coax Link Rate <TX 224Mbps/RX 238Mbps>
Jun 9 09:05:55 2019 System Log CWMP Connection Request Inform 204 No Content
Jun 9 09:05:55 2019 System Log CWMP Connection Request Inform challege response with 200 OK from server
Jun 9 09:05:54 2019 System Log CWMP Connection Request Inform initial 401 chanllenge
Jun 9 09:05:38 2019 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.5, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Wireless)
Jun 9 09:05:29 2019 System Log LAN DHCP DHCP LAN Connection IP:192.168.1.4, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Wireless)
 
Is that it then, a log file that only covers 5 minutes? Not too useful :rolleyes:.

That said, we can see what appears to be wireless clients connecting directly to this device and not the Asus. So from that we can conclude that the Fios "modem" is not actually a modem but a modem+wireless router combo.

You never answered my question about what IP address range you are using on the Asus. Also, I'm assuming the Asus is in "router mode", correct?
 

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!

Staff online

Top