Menu
What's new
By:
Filters Better Search

Problem w/ Latest Firmwares > .178 (Daily Disconnects from Modem)

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

I have been lurking here for a while. I have the same issue with periodic disconnects. In my case, I power cycle the router, and everything returns to normal. I am not technical, but I believe that this is related somehow to the router and how it interfaces with my cable modem.

I am still on the original firmware (3.0.0.3.155) and had no issues at all. I am on Time Warner and they had provided me a Docsis 2.0 modem. Recently I purchased my own cable modem - Motorola SB6141) and have had almost daily disconnects. All of the lights on the router seem normal, but I cannot get to the Internet until I turn the router off, wait 10 seconds, and then power back up.

I am planning to upgrade to .220 and hopefully get some stability.
 
You really should upgrade, the build you are on only has 32k nvram. If you go over that with settings and scripts your router would reboot.
I forget which fw has the first 64k nvram fix but I do know that .220 has it.
 
Welp , Asus has asked me to RMA my unit. Worried about getting someones trashed one as replacement.
 
xrecar said:
Welp , Asus has asked me to RMA my unit. Worried about getting someones trashed one as replacement.
Click to expand...

If you have the extra $, get an AC66U instead and sell the N66U.

In almost a week since I started using the AC66U....not a single drop-out connection.
 
Pierino said:
You really should upgrade, the build you are on only has 32k nvram. If you go over that with settings and scripts your router would reboot.
I forget which fw has the first 64k nvram fix but I do know that .220 has it.
Click to expand...

Thanks! I updated to .220 yesterday, and so far everything seems stable. Need to give it time to see if this resolved my daily disconnect issue.
 
As an experiment , upgraded back to .260 without a external hd attached. Thought that maybe might be ovewhelming the functionality while scanning 2 tb right on boot. We will see what happens. Posiden , did you have anything attached to your usb ports? I use my router mainly as a media server.
 
No devices connected on USB ports. What's weird in my situation is that the .260 firmware did not resolve the issue in my previous N66U (2 of them), yet the .260 firmware works perfectly in the AC66U.
 
Been up for almost 10 hrs now - new record as of late. Noticed a windows seven laptop flooding the router with dhcp requests in the log. Turned it off for now.
 
If you have a hard disk plugged in, you must go to LAN -> Switch Control and set GRO to "force disable", otherwise your router will randomly reboot itself.
 
mm2531 said:
Thanks! I updated to .220 yesterday, and so far everything seems stable. Need to give it time to see if this resolved my daily disconnect issue.
Click to expand...

Well, so much for that hope. Still getting the daily (2-3) disconnects even with the .220 firmware. Never had a single disconnect until I installed a new cable modem.

Very frustrating having to power cycle the router multiple times every day.
 
mm2531 said:
Well, so much for that hope. Still getting the daily (2-3) disconnects even with the .220 firmware. Never had a single disconnect until I installed a new cable modem.

Very frustrating having to power cycle the router multiple times every day.
Click to expand...

Make sure you are using a Cat5e or Cat6 network cable between the modem and the router. If you upgraded to a new modem that has a gigabit interface but are still using an older Cat5 cable, you will have stability issues.
 
RMerlin said:
Make sure you are using a Cat5e or Cat6 network cable between the modem and the router. If you upgraded to a new modem that has a gigabit interface but are still using an older Cat5 cable, you will have stability issues.
Click to expand...

Thanks, Merlin.

I just changed the cable this morning just to be sure. Not even 15 minutes later, I had my first disconnect. Power cycled the router and 60 seconds later I was back up. I am not sure if there are more disconnects when I don't notice and it self corrects. The next time I am going to wait 5 minutes to see what happens.

It is very frustrating as we are dependent on the internet for our "land line" - Google Voice through a VOIP adapter, and our cellphones have no reception except through a network extender. So, as like this morning, our phone conversation suddenly ends abruptly.

I am not sure what this means, or if it is helpful, but here is the log (I don't know how to fix the date in the router). Also, the disconnect was just before 9 am.

Dec 1 08:52:45 notify_rc : restart_upnp
Dec 1 08:52:45 miniupnpd[618]: received signal 15, good-bye
Dec 1 08:52:45 syslog: SNet version started
Dec 1 08:52:45 miniupnpd[625]: HTTP listening on port 60571
Dec 1 08:52:45 miniupnpd[625]: Listening for NAT-PMP traffic on port 5351
Dec 1 08:52:47 dnsmasq-dhcp[521]: DHCPREQUEST(br0) 192.168.1.208 50:46:5d:1f:dc:a3
Dec 1 08:52:47 dnsmasq-dhcp[521]: DHCPACK(br0) 192.168.1.208 50:46:5d:1f:dc:a3 android-b34f03e66abed60d
Dec 1 08:52:48 dnsmasq-dhcp[521]: DHCPREQUEST(br0) 192.168.1.11 a4:67:06:6c:ef:8e
Dec 1 08:52:48 dnsmasq-dhcp[521]: DHCPACK(br0) 192.168.1.11 a4:67:06:6c:ef:8e Mu-iPad
Dec 1 08:53:20 dnsmasq-dhcp[521]: DHCPREQUEST(br0) 192.168.1.61 98:fe:94:18:9b:77
Dec 1 08:53:20 dnsmasq-dhcp[521]: DHCPACK(br0) 192.168.1.61 98:fe:94:18:9b:77 Mu-iPhone
Dec 1 08:53:39 dnsmasq-dhcp[521]: DHCPREQUEST(br0) 192.168.1.61 98:fe:94:18:9b:77
Dec 1 08:53:39 dnsmasq-dhcp[521]: DHCPACK(br0) 192.168.1.61 98:fe:94:18:9b:77 Mu-iPhone
Dec 1 08:55:23 dnsmasq-dhcp[521]: DHCPREQUEST(br0) 192.168.1.61 98:fe:94:18:9b:77
Dec 1 08:55:23 dnsmasq-dhcp[521]: DHCPACK(br0) 192.168.1.61 98:fe:94:18:9b:77 Mu-iPhone
Dec 1 08:55:44 dnsmasq-dhcp[521]: DHCPREQUEST(br0) 192.168.1.61 98:fe:94:18:9b:77
Dec 1 08:55:44 dnsmasq-dhcp[521]: DHCPACK(br0) 192.168.1.61 98:fe:94:18:9b:77 Mu-iPhone
Dec 1 08:56:01 dnsmasq-dhcp[521]: DHCPREQUEST(br0) 192.168.1.61 98:fe:94:18:9b:77
Dec 1 08:56:01 dnsmasq-dhcp[521]: DHCPACK(br0) 192.168.1.61 98:fe:94:18:9b:77 Mu-iPhone
Dec 1 08:56:26 dnsmasq-dhcp[521]: DHCPREQUEST(br0) 192.168.1.172 8c:58:77:72:47:bc
Dec 1 08:56:26 dnsmasq-dhcp[521]: DHCPACK(br0) 192.168.1.172 8c:58:77:72:47:bc Ls-iPhone
Dec 1 09:00:51 dnsmasq-dhcp[521]: DHCPREQUEST(br0) 192.168.1.172 8c:58:77:72:47:bc
Dec 1 09:00:51 dnsmasq-dhcp[521]: DHCPACK(br0) 192.168.1.172 8c:58:77:72:47:bc Ls-iPhone
Dec 1 09:02:55 dnsmasq-dhcp[521]: DHCPREQUEST(br0) 192.168.1.172 8c:58:77:72:47:bc
Dec 1 09:02:55 dnsmasq-dhcp[521]: DHCPACK(br0) 192.168.1.172 8c:58:77:72:47:bc Ls-iPhone
Dec 1 09:08:21 dnsmasq-dhcp[521]: DHCPREQUEST(br0) 192.168.1.172 8c:58:77:72:47:bc
Dec 1 09:08:21 dnsmasq-dhcp[521]: DHCPACK(br0) 192.168.1.172 8c:58:77:72:47:bc Ls-iPhone
Dec 1 09:20:58 dnsmasq-dhcp[521]: DHCPREQUEST(br0) 192.168.1.172 8c:58:77:72:47:bc
Dec 1 09:20:58 dnsmasq-dhcp[521]: DHCPACK(br0) 192.168.1.172 8c:58:77:72:47:bc Ls-iPhone
Dec 1 09:23:05 dnsmasq-dhcp[521]: DHCPREQUEST(br0) 192.168.1.63 00:11:d9:0e:30:77
Dec 1 09:23:05 dnsmasq-dhcp[521]: DHCPACK(br0) 192.168.1.63 00:11:d9:0e:30:77 TIVO-6520001805B18AC
Dec 1 09:35:52 dnsmasq-dhcp[521]: DHCPREQUEST(br0) 192.168.1.172 8c:58:77:72:47:bc
Dec 1 09:35:52 dnsmasq-dhcp[521]: DHCPACK(br0) 192.168.1.172 8c:58:77:72:47:bc Ls-iPhone
Dec 1 09:37:38 dnsmasq-dhcp[521]: DHCPREQUEST(br0) 192.168.1.172 8c:58:77:72:47:bc
Dec 1 09:37:38 dnsmasq-dhcp[521]: DHCPACK(br0) 192.168.1.172 8c:58:77:72:47:bc Ls-iPhone
Dec 1 09:42:50 dnsmasq-dhcp[521]: DHCPREQUEST(br0) 192.168.1.151 00:1d:e0:9f:71:99
Dec 1 09:42:50 dnsmasq-dhcp[521]: DHCPACK(br0) 192.168.1.151 00:1d:e0:9f:71:99 mu-hp
Dec 1 09:49:13 dnsmasq-dhcp[521]: DHCPREQUEST(br0) 192.168.1.172 8c:58:77:72:47:bc
Dec 1 09:49:13 dnsmasq-dhcp[521]: DHCPACK(br0) 192.168.1.172 8c:58:77:72:47:bc Ls-iPhone
 
Well , I made it 24 hrs without disconnect. All I've noticed in the log are DHCPACK and DHCPREQUEST lines after everything got running.
 
Those DHCP messages are all related to devices on the LAN side, not to your WAN interface.

Also, I recommend running build 246 or 260 (or one of my builds if you have wireless issues with these two), and making sure you have GRO set to forced disabled on the LAN -> Switch page. Otherwise, your router might randomly reboot itself.
 
RMerlin said:
Those DHCP messages are all related to devices on the LAN side, not to your WAN interface.

Also, I recommend running build 246 or 260 (or one of my builds if you have wireless issues with these two), and making sure you have GRO set to forced disabled on the LAN -> Switch page. Otherwise, your router might randomly reboot itself.
Click to expand...

I will upgrade to .260 and see what happens.

I just had a disconnect a few minutes ago. This time I waited and the router reconnected to the internet. I am not sure if these messages in the log are meaningful, but here they are. Thanks for taking the time to look at this and give me advice!

Dec 1 18:03:27 dnsmasq[521]: read /etc/hosts - 3 addresses
Dec 1 18:03:27 notify_rc : start_nat_rules
Dec 1 18:03:27 start_nat_rules: apply the nat_rules!
Dec 1 18:03:27 notify_rc : stop_upnp
Dec 1 18:03:27 miniupnpd[764]: received signal 15, good-bye
Dec 1 18:03:27 notify_rc : start_upnp
Dec 1 18:03:27 syslog: SNet version started
Dec 1 18:03:27 miniupnpd[790]: HTTP listening on port 54982
Dec 1 18:03:27 miniupnpd[790]: Listening for NAT-PMP traffic on port 5351
Dec 1 18:03:27 WAN Connection: Ethernet link up.
Dec 1 18:03:27 notify_rc : restart_wan_if 0
Dec 1 18:03:27 dnsmasq[521]: read /etc/hosts - 3 addresses
Dec 1 18:03:27 dhcp client: bound 192.168.100.10 via 0.0.0.0
Dec 1 18:03:27 stop_wan(): perform DHCP release
Dec 1 18:03:27 dnsmasq[521]: read /etc/hosts - 3 addresses
Dec 1 18:03:27 kernel: br0: port 1(vlan1) entering disabled state
Dec 1 18:03:27 kernel: br0: topology change detected, propagating
Dec 1 18:03:27 kernel: br0: port 1(vlan1) entering listening state
Dec 1 18:03:27 kernel: br0: port 1(vlan1) entering learning state
Dec 1 18:03:27 kernel: br0: topology change detected, propagating
Dec 1 18:03:27 kernel: br0: port 1(vlan1) entering forwarding state
Dec 1 18:03:29 dnsmasq[521]: read /etc/hosts - 3 addresses
Dec 1 18:03:29 dnsmasq[521]: read /etc/hosts - 3 addresses
Dec 1 18:03:29 notify_rc : start_nat_rules
Dec 1 18:03:29 start_nat_rules: apply the nat_rules!
Dec 1 18:03:29 notify_rc : stop_upnp
Dec 1 18:03:29 miniupnpd[790]: received signal 15, good-bye
Dec 1 18:03:29 notify_rc : start_upnp
Dec 1 18:03:29 syslog: SNet version started
Dec 1 18:03:29 miniupnpd[820]: HTTP listening on port 36967
Dec 1 18:03:29 miniupnpd[820]: Listening for NAT-PMP traffic on port 5351
Dec 1 18:03:30 dhcp client: bound 192.168.100.10 via 0.0.0.0
Dec 1 18:03:40 dnsmasq[521]: read /etc/hosts - 3 addresses
Dec 1 18:03:40 notify_rc : start_nat_rules
Dec 1 18:03:40 start_nat_rules: apply the nat_rules!
Dec 1 18:03:40 notify_rc : stop_upnp
Dec 1 18:03:40 miniupnpd[820]: received signal 15, good-bye
Dec 1 18:03:40 notify_rc : start_upnp
Dec 1 18:03:40 syslog: SNet version started
Dec 1 18:03:40 miniupnpd[845]: HTTP listening on port 56200
Dec 1 18:03:40 miniupnpd[845]: Listening for NAT-PMP traffic on port 5351
Dec 1 18:03:40 dhcp client: bound 192.168.100.10 via 0.0.0.0
Dec 1 18:03:59 dnsmasq[521]: read /etc/hosts - 3 addresses
Dec 1 18:03:59 dnsmasq[521]: read /etc/hosts - 3 addresses
Dec 1 18:03:59 dnsmasq[521]: using nameserver 209.18.47.62#53
Dec 1 18:03:59 dnsmasq[521]: using nameserver 209.18.47.61#53
Dec 1 18:03:59 notify_rc : start_nat_rules
Dec 1 18:03:59 start_nat_rules: apply the nat_rules!
Dec 1 18:03:59 notify_rc : stop_upnp
Dec 1 18:03:59 miniupnpd[845]: received signal 15, good-bye
Dec 1 18:03:59 notify_rc : start_upnp
Dec 1 18:03:59 syslog: SNet version started
Dec 1 18:03:59 miniupnpd[875]: HTTP listening on port 39511
Dec 1 18:03:59 miniupnpd[875]: Listening for NAT-PMP traffic on port 5351
Dec 1 18:03:59 dhcp client: bound 71.75.238.188 via 71.75.224.1
Dec 1 18:04:00 WAN Connection: WAN was restored.
 
Nothing unusual in that log, in fact it shows no sign of disconnection, only of the actual connection.

Check your router's uptime value on the System Log page. If you see it's only a few mins old, then it means your problem is your router is crashing and rebooting itself. Setting the GRO option as I mentioned should resolve your problem.
 
RMerlin said:
Nothing unusual in that log, in fact it shows no sign of disconnection, only of the actual connection.

Check your router's uptime value on the System Log page. If you see it's only a few mins old, then it means your problem is your router is crashing and rebooting itself. Setting the GRO option as I mentioned should resolve your problem.
Click to expand...

I am now pretty sure my issues are with the modem and the TWC signal. In checking the modem log, I see T3 and T4 timeouts. I have googled this and there are a lot of discussions about people having issues with the SB6141 modem with both TWC and Comcast. I don't understand all of the technical discussion, but this apparently has to do with the upstream signal strength and this particular modem (along with the older SB6121). The Ubee modem provided by TWC is rock solid, but these modems tend to have these timeouts and reboot. Would explain why my disconnects started right after I bought my own modem.

For others getting intermittent timeouts, you may want to check the modem logs as well.
 
RMerlin previously stated that the N66U and the AC66U both use identical firmwares (latest .260 version). Then how can it be explained that when I was using the N66U (.260 firmware), I would get these daily disconnects - but as soon as I changed to the AC66U (also using .260 firmware), I have NOT had a single disconnect in almost 2 weeks now???

Same SB6121 router; Same Ethernet cables; Same Asus firmware version....just different Asus router.

Can this be explained....possibly hardware-related (N66U vs AC66U)?
 
My issues went away (I say away with the past 4 days) when I reflashed and rebooted the router WITHOUT anything attached to the usb ports (usually my 2*2TB media drives). Perhaps this was causing the n66u to choke somhow? I am now on edge running 260 after having multiple disconnects each day. One other change is a windows 7 laptop has been turned off; I noticed an absurd amount of dhcp requests from it when online. (Anyone else notice this with windows 7?)
 
You must log in or register to reply here.

Similar threads

mekki
WAN Reconnect Problems Across ASUS Routers / Firmware Versions
Replies
10
Views
3K
brummygit
brummygit
RHPT
RT-AX88U constantly unable to see modem
Replies
8
Views
1K
RHPT
RHPT
Enceladus
RT-AC88U w/ 2 x ZenWifi CT8 AiMesh - Gaming Nightmare!
Replies
19
Views
3K
BreakingDad
BreakingDad
I
Frequent WAN Disconnects on Asus Router
Replies
5
Views
11K
SoCalReviews
S
M
RT-AC68P stops giving out DHCP and can't login to Admin GUI randomly
Replies
1
Views
987
ColinTaylor
C

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: 677 (members: 23, guests: 654)
Top