What's new

RT AC66U rebooting issue

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

FUBAR183

New Around Here
I'm now on my second AC66U for this same issue. ASUS support has been no help at all. New AC66U and new comcast bridged gateway installed today, flashed to latest firmware, and within 10 minutes it started rebooting every 10 to 15 minutes. I'm at my wits end trying to fix this. Help please!

syslog after each reboot is as follows:

Dec 31 19:00:11 syslogd started: BusyBox v1.17.4
Dec 31 19:00:11 kernel: klogd started: BusyBox v1.17.4 (2015-01-10 19:34:47 CST)
Dec 31 19:00:11 kernel: start_kernel
Dec 31 19:00:11 kernel: Linux version 2.6.22.19 (root@asus) (gcc version 4.2.3) #1 Sat Jan 10 19:37:50 CST 2015
Dec 31 19:00:11 kernel: CPU revision is: 00019749
Dec 31 19:00:11 kernel: Found an ST compatible serial flash with 32 64KB blocks; total size 2MB
Dec 31 19:00:11 kernel: Determined physical RAM map:
Dec 31 19:00:11 kernel: memory: 07fff000 @ 00000000 (usable)
Dec 31 19:00:11 kernel: memory: 08000000 @ 87fff000 (usable)
Dec 31 19:00:11 kernel: Built 1 zonelists. Total pages: 585216
Dec 31 19:00:11 kernel: Kernel command line: root=/dev/mtdblock3 console=ttyS0,115200 init=/sbin/preinit
Dec 31 19:00:11 kernel: Primary instruction cache 32kB, physically tagged, 4-way, linesize 32 bytes.
Dec 31 19:00:11 kernel: Primary data cache 32kB, 4-way, linesize 32 bytes.
Dec 31 19:00:11 kernel: PID hash table entries: 2048 (order: 11, 8192 bytes)
Dec 31 19:00:11 kernel: CPU: BCM5300 rev 1 pkg 0 at 600 MHz
Dec 31 19:00:11 kernel: Using 300.000 MHz high precision timer.
Dec 31 19:00:11 syslog: module ledtrig-usbdev not found in modules.dep
Dec 31 19:00:11 syslog: module leds-usb not found in modules.dep
Dec 31 19:00:11 kernel: Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Dec 31 19:00:11 kernel: Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Dec 31 19:00:11 kernel: Mount-cache hash table entries: 512
Dec 31 19:00:11 kernel: PCI: Initializing host
Dec 31 19:00:12 kernel: PCI: Reset RC
Dec 31 19:00:12 kernel: PCI: Initializing host
Dec 31 19:00:12 kernel: PCI: Reset RC
Dec 31 19:00:12 kernel: PCI: Fixing up bus 0
Dec 31 19:00:12 kernel: PCI/PCIe coreunit 0 is set to bus 1.
Dec 31 19:00:12 kernel: PCI: Fixing up bridge
Dec 31 19:00:12 kernel: PCI: Fixing up bridge
Dec 31 19:00:12 kernel: PCI: Enabling device 0000:01:00.1 (0004 -> 0006)
Dec 31 19:00:12 kernel: PCI: Fixing up bus 1
Dec 31 19:00:12 kernel: PCI/PCIe coreunit 1 is set to bus 2.
Dec 31 19:00:12 kernel: PCI: Fixing up bridge
Dec 31 19:00:12 kernel: PCI: Fixing up bridge
Dec 31 19:00:12 kernel: PCI: Enabling device 0000:02:00.1 (0004 -> 0006)
Dec 31 19:00:12 kernel: PCI: Fixing up bus 2
Dec 31 19:00:12 kernel: IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
Dec 31 19:00:12 kernel: TCP established hash table entries: 16384 (order: 5, 131072 bytes)
Dec 31 19:00:12 kernel: TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
Dec 31 19:00:12 kernel: highmem bounce pool size: 64 pages
Dec 31 19:00:12 kernel: pflash: found no supported devices
Dec 31 19:00:12 kernel: Boot partition size = 262144(0x40000)
Dec 31 19:00:12 kernel: Creating 2 MTD partitions on "sflash":
Dec 31 19:00:12 kernel: 0x00000000-0x00040000 : "pmon"
Dec 31 19:00:12 kernel: 0x001f0000-0x00200000 : "nvram"
Dec 31 19:00:12 kernel: Found a Zentel NAND flash with 2048B pages or 128KB blocks; total size 128MB
Dec 31 19:00:12 kernel: lookup_nflash_rootfs_offset: offset = 0x0
Dec 31 19:00:12 kernel: nflash: squash filesystem with lzma found at block 9
Dec 31 19:00:12 kernel: Creating 4 MTD partitions on "nflash":
Dec 31 19:00:12 kernel: 0x00000000-0x02000000 : "linux"
Dec 31 19:00:12 kernel: 0x00134ec0-0x02000000 : "rootfs"
Dec 31 19:00:12 kernel: 0x04000000-0x06000000 : "linux2"
Dec 31 19:00:12 kernel: 0x04134ec0-0x06000000 : "rootfs2"
Dec 31 19:00:12 kernel: Creating 3 MTD partitions on "brcmnand":
Dec 31 19:00:12 kernel: 0x00000000-0x02000000 : "trx"
Dec 31 19:00:12 kernel: 0x04000000-0x06000000 : "asustrx2"
Dec 31 19:00:12 kernel: 0x06000000-0x07f00000 : "brcmnand"
Dec 31 19:00:12 kernel: dev_nvram_init: _nvram_init
Dec 31 19:00:12 kernel: u32 classifier
Dec 31 19:00:12 kernel: OLD policer on
Dec 31 19:00:12 kernel: Netfilter messages via NETLINK v0.30.
Dec 31 19:00:12 kernel: nf_conntrack version 0.5.0 (2048 buckets, 16384 max)
Dec 31 19:00:12 kernel: ipt_time loading
Dec 31 19:00:12 kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Dec 31 19:00:12 kernel: net/ipv4/netfilter/tomato_ct.c [Jan 10 2015 19:37:13]
Dec 31 19:00:12 kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Dec 31 19:00:12 kernel: VFS: Mounted root (squashfs filesystem) readonly.
Dec 31 19:00:12 kernel: Warning: unable to open an initial console.
Dec 31 19:00:12 kernel: Failed to execute /sbin/preinit. Attempting defaults...
Dec 31 19:00:12 kernel: Algorithmics/MIPS FPU Emulator v1.5
Dec 31 19:00:12 kernel: et: module license 'Proprietary' taints kernel.
Dec 31 19:00:12 kernel: et_module_init: passivemode set to 0x0
Dec 31 19:00:12 kernel: et_module_init: et_txq_thresh set to 0x400
Dec 31 19:00:12 kernel: bcm_robo_enable_switch: EEE is disabled
Dec 31 19:00:12 kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 6.30.163.2002 (r382208)
Dec 31 19:00:12 kernel: wl_module_init: passivemode set to 0x0
Dec 31 19:00:12 kernel: PCI: Enabling device 0000:01:01.0 (0000 -> 0002)
Dec 31 19:00:12 kernel: eth1: Broadcom BCM4331 802.11 Wireless Controller 6.30.163.2002 (r382208)
Dec 31 19:00:12 kernel: PCI: Enabling device 0000:02:01.0 (0000 -> 0002)
Dec 31 19:00:12 kernel: eth2: Broadcom BCM4360 802.11 Wireless Controller 6.30.163.2002 (r382208)
Dec 31 19:00:12 kernel: SCSI subsystem initialized
Dec 31 19:00:12 kernel: ufsd: driver (8.6 U86_r187446_b122, LBD=ON, acl, ioctl, rwm, ws, sd) loaded at c01f8000
Dec 31 19:00:12 kernel: NTFS (with native replay) support included
Dec 31 19:00:12 kernel: optimized: speed
Dec 31 19:00:12 kernel: Build_for__asus_n66u_2011-10-27_U86_r187446_b122
Dec 31 19:00:15 kernel: wlc_phy_cal_init_acphy: NOT Implemented
Dec 31 19:00:15 stop_nat_rules: apply the redirect_rules!
Dec 31 19:00:15 WAN Connection: ISP's DHCP did not function properly.
Dec 31 19:00:21 dnsmasq[353]: warning: interface ppp1* does not currently exist
Dec 31 19:00:21 RT-AC66U: start httpd
Dec 31 19:00:21 syslog: Generating SSL certificate...
Dec 31 19:00:21 disk monitor: be idle
Dec 31 19:00:23 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Dec 31 19:00:24 kernel: nf_conntrack_rtsp v0.6.21 loading
Dec 31 19:00:24 kernel: nf_nat_rtsp v0.6.21 loading
Dec 31 19:00:25 rc_service: udhcpc 397:notify_rc stop_upnp
Dec 31 19:00:25 rc_service: udhcpc 397:notify_rc start_upnp
Dec 31 19:00:25 WAN Connection: WAN was restored.
Dec 31 19:00:28 ntp: start NTP update
Jan 17 14:16:41 rc_service: ntp 447:notify_rc restart_upnp
Jan 17 14:16:41 rc_service: ntp 447:notify_rc restart_diskmon
Jan 17 14:16:41 rc_service: waitting "restart_upnp" via ntp ...
Jan 17 14:16:42 disk monitor: be idle
Jan 17 14:16:42 dhcp client: bound 50.160.146.79 via 50.160.144.1 during 341321 seconds.
Jan 17 14:17:14 crond[356]: time disparity of 2128036 minutes detected
Jan 17 14:30:23 kernel: eth1: received packet with own address as source address
 
What is the "latest firmware" that you flashed to?

What gateway are you using on your Comcast cable?

I also suspect that the issue lies in the lines I've highlighted below:

Dec 31 19:00:12 kernel: Build_for__asus_n66u_2011-10-27_U86_r187446_b122
Dec 31 19:00:15 kernel: wlc_phy_cal_init_acphy: NOT Implemented
Dec 31 19:00:15 stop_nat_rules: apply the redirect_rules!
Dec 31 19:00:15 WAN Connection: ISP's DHCP did not function properly.
Dec 31 19:00:21 dnsmasq[353]: warning: interface ppp1* does not currently exist
Dec 31 19:00:21 RT-AC66U: start httpd
Dec 31 19:00:21 syslog: Generating SSL certificate...
Dec 31 19:00:21 disk monitor: be idle
Dec 31 19:00:23 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Dec 31 19:00:24 kernel: nf_conntrack_rtsp v0.6.21 loading
Dec 31 19:00:24 kernel: nf_nat_rtsp v0.6.21 loading
Dec 31 19:00:25 rc_service: udhcpc 397:notify_rc stop_upnp
Dec 31 19:00:25 rc_service: udhcpc 397:notify_rc start_upnp
Dec 31 19:00:25 WAN Connection: WAN was restored.
Dec 31 19:00:28 ntp: start NTP update
Jan 17 14:16:41 rc_service: ntp 447:notify_rc restart_upnp
Jan 17 14:16:41 rc_service: ntp 447:notify_rc restart_diskmon
Jan 17 14:16:41 rc_service: waitting "restart_upnp" via ntp ...
Jan 17 14:16:42 disk monitor: be idle
Jan 17 14:16:42 dhcp client: bound 50.160.146.79 via 50.160.144.1 during 341321 seconds.
Jan 17 14:17:14 crond[356]: time disparity of 2128036 minutes detected
Jan 17 14:30:23 kernel: eth1: received packet with own address as source address

A couple of things: Are you sure you flashed firmware for the AC66U? Or did you flash the N66U's firmware accidentally?

Are you sure that you have DHCP turned off in whatever cable modem/router device you're using in "bridged" mode? You need to turn it off in the router since all DHCP is going to be handled by your AC66U.

Are you sure you've turned off NAT as well in the cable modem? If not, do it otherwise you'll wind up double NATting.

Also, turn off the Firewall in the cable modem. Your AC66U will handle that.

Next, be sure to disconnect any USB devices from the AC66U, and be sure that all the USB services are turned off in the GUI. This means making sure DLNA is set to off, FTP is off, and SAMBA is off, and so are any NFS shares. Once you get basic connectivity up and running, you can mess with the "extras".

Also, in the AC66U's GUI, make sure that you set the time zone the correct time zone where you are located. It sometimes defaults to GMT and you need to apply the correct time zone.

Finally, the line that reads "eth1: received packet with own address as source address" would suggest that perhaps you have dual WAN also enabled. If so, turn it off.

My guess though is that this has more to do with either (a) the gateway's settings not being set properly (you want to turn off everything in the gateway so that it essentially is functioning just as a cable router and nothing more than that), or (b) with an improper flash of firmware to the AC66U.

One other thing: Did you clear your NVRAM after upgrading your firmware? I'm guessing no, so you need to do that (assuming you flashed the right FW version). To clear NVRAM, you can either hold in the reset button for 15-30 seconds while you power the router back on, or you can go to the "Administration" page, and look in "Restore/Save/Upload Settings" page and hit the factory restore. Reboot and then re-enter your settings by hand, again making sure to turn off all of the USB services until you are sure you have connectivity established.
 
Last edited:
Dec 31 19:00:12 kernel: Build_for__asus_n66u_2011-10-27_U86_r187446_b122

That part is normal. Asus uses the same Paragon module for all the MIPS models (the N66 just happened to be the first model for which they got a license from Paragon, and a compiled binary blob from them).
 
That part is normal. Asus uses the same Paragon module for all the MIPS models (the N66 just happened to be the first model for which they got a license from Paragon, and a compiled binary blob from them).

Thanks Merlin. Good to know.

Any other insights on what the issue might be with the OP's AC66U rebooting?
 
Thanks Merlin. Good to know.

Any other insights on what the issue might be with the OP's AC66U rebooting?

The main causes of spontaneous reboots:

- Router running out of RAM because you are running DownloadMaster or other memory-intensive apps
- Corrupted media file on a plugged USB disk that causes minidlna to spin out of control
- Compatibility issue between ISP and NAT acceleration
- Power issue (using a quality power bar resolved the issue for at least one user in the past)
- Overheating if the router is hidden in a tight, closed area or sitting on top of your cablemodem
- Defective hardware
 

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