WAN Disconnects

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Configure router 
2. Use router for some time (30 - 40 minutes)
3. Start clicking on links and notice that the internet is no longer working.
4. Wait 20-30 seconds and internet connection is reestablished.
5. Every few minutes go back to step 3.

What is the expected output? What do you see instead?
The expected output is a wan port that stays connected to the internet. 

What version of the product are you using? On what operating system?
Both the official firmware and p4, p5, and p6 versions exhibit the same 
behavior.

Please provide any additional information below.
Attached is a syslog file showing the disconnects.

Original issue reported on code.google.com by mark.mu...@gmail.com on 24 Dec 2011 at 10:54

Attachments:

• syslog.zip

[GoogleCodeExporter]

yes i have torrents running but they usually don't exceed high bandwidth when 
it does disconnect.  i will post a log the next time i get this issue it has 
only happened once so far so i will keep you posted thanks james =D

Original comment by AndrewMi...@gmail.com on 12 Jul 2012 at 8:41

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Hey guys, just an update, and some tips. Have been using the beta firmware for 
2 days now, and no wan disconnects. I'm getting the router under full load with 
torrents and xbox live simultaneously. It's been handling things quite well!

To be on the safe side, I decided to create a small script that would 
automatically reboot the router every day (just in case). I schedule it to run 
at 5:00AM everyday from my computer, and reboot the N56U, since it stays always 
on.

It's been working well (works on windows 7, but can be adapted for MAC using 
the Sikuli IDE), so I decided I'd share it (check attachment)

Steps to use it:

1) Enable telnet on the router
2) Enable telnet on windows (or MAC)
3) Download and install Sikuli http://sikuli.org/
4) Extract this attached file, it has a folder inside: "reset-n56u.sikuli"
5) Open this folder in the Sikuli IDE. Edit the file with your router's 
authentication data (login and password).
6) Go to File -> Export executable. Save it somewhere like C:\. (Export it 
directly to the place you intend to keep it in. It doesn't seem to work if you 
move it to a different folder afterwards)
7) Make a .bat file in notepad with the following content:
"C:\Program Files (x86)\Sikuli X\Sikuli-IDE.bat" 
"C:\path_to_script\name_of_your_exported_script.skl"
8) Use Windows Task Scheduler to schedule the bat file to be run once a day, or 
once every 2 days.
9) Be happy with a stable internet connection for the whole family, forever and 
ever (hopefully)

Let me know if it works for you!

Cya!

Original comment by rafa.vi...@gmail.com on 13 Jul 2012 at 5:16

Attachments:

• reset-n56u.sikuli.zip

[GoogleCodeExporter]

I'm still getting internet loss hourly.  The problem is between the router and 
the internet, as I'm able to access the router's admin page during the outages.

Since upgrading to the 3.xxx beta firmware I don't get any messages in the 
system log.  I used to get the lease lost message in the log.  Is anyone else 
noticing this problem?  I'm pretty sure the cable modem is okay as I've used it 
for a while with other routers and there haven't been any problems.  I didn't 
have any problems with my Asus n56u until about a month or so ago and then it 
started getting flakey.  That was when I noticed the lease lost messages.  It 
is still flakey, but *no messages* are showing up in the logs during these down 
periods.

Original comment by jhuffa...@gmail.com on 20 Jul 2012 at 1:21

[GoogleCodeExporter]

Hey jhuffa, are you using the modem in bridge mode? I used to have internet 
loss problems when modem did the PPPoE connection and was responsible for DHCP 
and such. Now I have the N56U do all that in the beta firmware, and I have a 
steady internet for about a week.

Maybe you should consider exchanging your unit, it may be faulty.

Original comment by rafa.vi...@gmail.com on 22 Jul 2012 at 3:22

[GoogleCodeExporter]

The unit was great until recently I'm not sure what is going on.  It was the 
very common lease lost issue that numerous other people complained about.  Now 
that I've upgraded I don't get the message anymore but I still get disconnects 
esp. during games or youtube.

The router is not in bridge mode.  The modem is a cable modem.

Original comment by jhuffa...@gmail.com on 23 Jul 2012 at 4:03

[GoogleCodeExporter]

Same issue here. Seem to happen overnight or when not using the connection that 
often. 
It has happened every day since loading 1.1.2.1-004. I went straight from Asus 
firmware to this one. No disconnect issues with latest Asus firmware.

Jan  1 00:00:13 RT-N56U: wan down (eth3)
Jan  1 00:00:13 kernel: Initializing USB Mass Storage driver...
Jan  1 00:00:13 kernel: usbcore: registered new interface driver usb-storage
Jan  1 00:00:13 kernel: USB Mass Storage support registered.
Jan  1 00:00:13 dhcp client: deconfig: lease is lost

Original comment by carlj...@gmail.com on 24 Jul 2012 at 9:49

[GoogleCodeExporter]

I am having the same problem after updating to 1.1.2.1_1004. 

Original comment by lamad...@gmail.com on 25 Jul 2012 at 4:10

[GoogleCodeExporter]

Based on what I know, only the Beta Firmware corrects the disconnect issue. The 
disconnects are still present even on the new 1.1.2.1_1004 firmware that is 
posted on the frontpage.

Also, I believe the 1.1.2.1_1004 is based off of a different set of coding 
kernal than the Beta 3.0.0.3_135 released by Asus.

Just an update: I've been running the 3.0.0.3_135 beta firmware for almost a 
month now. No disconnects thus far (or at least that I am aware of). I'm able 
to focus more on enjoying the router's functionality and performing my actual 
computing tasks, instead of getting frustrated with constant disconnects. My 
speeds are still out-of-this-world and any bugs have yet to affect me (*knock 
on wood*).

The next test for my router is to stream media from one room to another under 
extended periods of time. Under the old firmware, the WAN Disconnects were due 
to large loads of incoming traffic from the Internet. I hope that 
internal-network traffic does not trigger a Disconnect or Router Crash.

For those curious, my router sits on top of a bookshelf with a lot of airy 
space around it. I wonder if 3.0.0.3_135 users are still getting disconnects 
because of excessive heat. Regardless of firmware, the Asus rt-n56u still runs 
pretty warm (and almost hot to the touch under full load).

Original comment by James.W....@gmail.com on 25 Jul 2012 at 5:26

[GoogleCodeExporter]

Same here, James. The Beta 3.0.0.3_135 by Asus seems to have reached a stable 
state. I keep mine under constant fan ventilation, though, because of the 
natural heat in my country (Brazil).

Original comment by rafa.vi...@gmail.com on 25 Jul 2012 at 5:32

[GoogleCodeExporter]

Thank god this is not a hardware issue . Has any one tried the new 1.1.2.2-005 
is the wan disconnect problem still there ? I won't be able to try it for 
myself for couple of days. Thanks. 

Original comment by lamad...@gmail.com on 27 Jul 2012 at 3:23

[GoogleCodeExporter]

I tried it with 004 version, so far wan disconnect issues seems to be gone
 My setting is to turn on hardware nat but i turn off software nat.

Original comment by yohinom...@gmail.com on 27 Jul 2012 at 3:26

[GoogleCodeExporter]

Damn even with the beta 3.0.0.3_135 I just had a wan disconnect issue in 26 
hours.

Jul 27 09:01:20 pppd[5326]: LCP terminated by peer
Jul 27 09:01:20 pppd[5326]: Connect time 900.1 minutes.
Jul 27 09:01:20 pppd[5326]: Sent 22769622 bytes, received 161091329 bytes.
Jul 27 09:01:20 dnsmasq[5330]: read /etc/hosts - 2 addresses
Jul 27 09:01:20 dnsmasq-dhcp[5330]: read /etc/ethers - 2 addresses
Jul 27 09:01:20 dnsmasq[5330]: using nameserver 202.70.89.171#53
Jul 27 09:01:20 dnsmasq[5330]: using nameserver 202.70.64.33#53
Jul 27 09:01:20 WAN Connection: Fail to connect with some issues.
Jul 27 09:01:20 notify_rc : stop_nat_rules
Jul 27 09:01:20 stop_nat_rules: apply the redirect_rules!
Jul 27 09:01:23 pppd[5326]: Connection terminated.
Jul 27 09:01:23 pppd[5326]: Sent PADT
Jul 27 09:01:23 pppd[5326]: Modem hangup

Original comment by lamad...@gmail.com on 27 Jul 2012 at 5:08

[GoogleCodeExporter]

I am now using the new firmware 1.1.2.2-005. I just noticed yesterday there is 
a adaptive LCP echo interval button . After turning it on so for I haven't have 
any wan disconnect issue. Thanks Andy for your great firmware.

Original comment by lamad...@gmail.com on 1 Aug 2012 at 1:43

[GoogleCodeExporter]

Even after turning on adaptive LCP echo interval. I had two lCP terminated by 
peer issue on the third day of running 1.1.2.2-005 firmware.

Original comment by lamad...@gmail.com on 3 Aug 2012 at 5:36

[GoogleCodeExporter]

Just to follow up on this, my router was sitting on our cable box.  The cable 
box can get hot as can the router.  I moved the router out into the open air 
and I think the disconnects stopped happening.  The reason I say "I think" is 
because I wasn't using the modem as heavily and may not have noticed the issues 
if they were still occurring.  But it was happening pretty frequently before 
that so I think heat may have been the issue.

I'll keep this bug updated as I get firmer confirmation or rejection of this 
hypothesis.  

Original comment by jhuffa...@gmail.com on 10 Aug 2012 at 1:39

[GoogleCodeExporter]

Still on the beta 3.xxx ASUS firmware, and no WAN disconnects. I keep my router 
constantly under fan ventilation to keep it cool, cause I live in a warm 
country.

Original comment by rafa.vi...@gmail.com on 10 Aug 2012 at 1:47

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

This is still occurring in the latest firmware 3.0.2.5-015

I have followed all the upgrades so far and all firmwares exhibit the same 
problem under heavy load.  I have even enabled ARP ping alive of remote gateway 
yes but the issue still exists.  I guess I can try ASUS firmware.

Oct  4 19:31:13 detect_link: WAN link down detected!
Oct  4 19:31:17 detect_link: WAN link restored!
Oct  4 19:31:19 detect_link: Perform WAN DHCP renew...
Oct  4 19:31:29 DHCP WAN Client: nak
Oct  4 19:31:29 RT-N56U: wan down (eth3)
Oct  4 19:31:29 DHCP WAN Client: deconfig: lease is lost
Oct  4 19:31:32 RT-N56U: wan up (eth3)
Oct  4 19:31:33 RT-N56U: Hardware NAT: Enabled, IPoE/PPPoE offload 
[WAN]<->[LAN/Wi-Fi]
Oct  4 19:31:33 DHCP WAN Client: bound (eth3), IP: 192.168.100.11, GW: 
XXX.XX.XXX.X, lease time: 20
Oct  4 19:31:37 NTP Scheduler: Synchronizing time...
Oct  4 19:31:43 RT-N56U: wan up (eth3)
Oct  4 19:31:43 RT-N56U: Hardware NAT: Enabled, IPoE/PPPoE offload 
[WAN]<->[LAN/Wi-Fi]
Oct  4 19:31:43 DHCP WAN Client: renew (eth3), IP: 192.168.100.11, GW: 
XXX.XX.XXX.X, lease time: 20
Oct  4 19:31:53 RT-N56U: wan up (eth3)
Oct  4 19:31:54 RT-N56U: Hardware NAT: Enabled, IPoE/PPPoE offload 
[WAN]<->[LAN/Wi-Fi]
Oct  4 19:31:54 DHCP WAN Client: renew (eth3), IP: 192.168.100.11, GW: 
XXX.XX.XXX.X, lease time: 20
Oct  4 19:32:04 DHCP WAN Client: nak
Oct  4 19:32:04 RT-N56U: wan down (eth3)
Oct  4 19:32:04 DHCP WAN Client: deconfig: lease is lost
Oct  4 19:32:07 RT-N56U: wan up (eth3)
Oct  4 19:32:07 RT-N56U: Hardware NAT: Enabled, IPoE/PPPoE offload 
[WAN]<->[LAN/Wi-Fi]
Oct  4 19:32:07 DHCP WAN Client: bound (eth3), IP: XXX.XX.XXX.XXX, GW: 
XXX.XX.XXX.X, lease time: 282850
Oct  4 19:32:16 NTP Scheduler: Synchronizing time...
Oct  4 19:32:17 RT-N56U: DDNS scheduler: Start update DDNS.

Is everybody saying this is an over heating issue?

Original comment by js28...@gmail.com on 5 Oct 2012 at 12:52

[GoogleCodeExporter]

I had WAN disconnect issues with this router that no firmware or setting could 
fix.
I finally fixed it by getting rid of my cable modem and replacing it with a new 
one. No WAN disconnects since I replaced it (2 weeks)

Original comment by lookma...@gmail.com on 5 Oct 2012 at 9:49

[GoogleCodeExporter]

I ams till experiencing connection drops. I have padavans latest firmware. It 
works for about 2 days after that it starts dropping the connection. I don't 
know maybeit is because it is experiencing heavy load and needs to be reset 
every 2-3 days (I donwload large files, play games etc)? Very frustrating to 
say the least..

Original comment by j-...@hotmail.com on 16 Oct 2012 at 6:53

[GoogleCodeExporter]

To anyone still having the issue: point a desk fan at your router + modem and 
see what happens. Mine would lose the WAN connection whenever it ran too hot, 
and giving it excessive ventilation fixed the issue completely.

To reiterate what others have said, EzQoS can't be on at the same time as 
Hardware NAT. Cheers, all.

Original comment by Onihik...@gmail.com on 1 Nov 2012 at 8:29

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

For some reason this problem started occuring with me over the past few days 
whenever I tried RDP'ing into work. It would disconnect every 10-30 seconds, 
driving me nuts. I tried setting the WAN port to 10mbit/s like mentioned above 
and it seems to have fixed it as no disconnects since.

I'm using the current latest firmware version: 3.0.3.3-040

Original comment by shan...@gmail.com on 31 Jan 2013 at 6:17

[GoogleCodeExporter]

My wan disconnects every 900.1 minutes cycle. Is this from my ISP side, I don't 
know.  I am using 3.0.3.3-042

Original comment by lamad...@gmail.com on 3 Mar 2013 at 11:05

[GoogleCodeExporter]

I'm having the same issues.  drops internet connection ever so often.   Can't 
seem to figure out why.

Original comment by fran...@gmail.com on 10 Mar 2013 at 8:34

[GoogleCodeExporter]

Same issue here. 
DHCP WAN Client: deconfig: lease is lost
after rebooting connection is up for a very short while (staring to ping www 
and after 3-5 pings connection is lost).
Firmware 3.0.3.3-046.

I understand there is a belief that the router gets too warm and this makes to 
malfunction.
To check this I cooled it down in a fridge a bit :-) but unfortunately this did 
not change the situation connection was still lost shortly after router booted.

Then I flashed official firmware v.3.0.0.4_318 and still had the same issue.

However disappointing it is it is probably time to look for a replacement...

Original comment by Victor.P...@gmail.com on 31 Mar 2013 at 11:17

[GoogleCodeExporter]

Well... replacement of the cable at least...
Tried to change the cable as was advised earlier and it seems solved the 
issue... for now.
Back to custom firmware.

Original comment by Victor.P...@gmail.com on 31 Mar 2013 at 11:46

[GoogleCodeExporter]

Talk of a "replacement" router brings up an interesting and somewhat related 
point. Does anyone know if the Asus RT-N66U (essentially the next model up) 
experiences these same WAN disconnect issues? 

Similarly, does the top-end Asus RT-AC66U have any WAN disconnect issues? Based 
on what I've heard, the AC protocol is still a little buggy and that consumers 
should stick with Wireless-N products for the time being.

Any advice offered here is most appreciated, since we seem to be the only 
collective group of folks who are cognizant of these WAN disconnect issues.

Original comment by James.W....@gmail.com on 31 Mar 2013 at 5:00

[GoogleCodeExporter]

I have updated the routed to 3.0.0.4.360 but still face this issue. It happens 
just as described except that is not that frequent. 

1. Configure router 
2. Use router for some time (30 - 40 minutes)
3. Start clicking on links and notice that the internet is no longer working.
4. Wait 20-30 seconds and internet connection is reestablished.
5. Every few minutes go back to step 3.

Original comment by swengeo...@gmail.com on 11 Jun 2013 at 9:19

[GoogleCodeExporter]

I'm facing the same kind of issues with my brand new router.
I didn't tried anything wet like custom firmware and so on, but it's a bit 
discouraging for me, and I'm thinking that I'll soon return that router to 
choose an other one, maybe not as good as this one but less buggy with cable 
modems...

Original comment by antoine....@gmail.com on 25 Jun 2013 at 1:36

[GoogleCodeExporter]

I solved the problem by letting the ISP modem down for about 20 minutes, then 
reconnect it and never faced any disconnection since.
Hope this help someone

Original comment by antoine....@gmail.com on 27 Jun 2013 at 3:42

[GoogleCodeExporter]

@Post #85,

Am I correct to bet that you use a Cable Service and a Cable Modem to access 
the Internet?

After a year+ of researching this issue, I found out that the rt-n56u will 
often randomly lose its connectivity (the technical term is it loses the 
"handshake") with the cable modem no matter what firmware you use (custom or 
stock). It seems the only affect cable modem users, as FIOS and other users are 
not impacted. 

The good news is that Asus Firmware 3.0.0.3.135 (it was a beta about a year 
ago) reduces the frequency of the problem; the router will only lose 
connectivity IF you are maxing out the amount of downloaded data for more than 
20-30 minutes. For example, I was downloading a game from Steam last night and 
the router/modem lost their handshake.

However, as long as I don't push my my router by downloading large amounts of 
data, my rt-n56u WILL stay up without reboots for days on end with Firmware 
3.0.0.3.135. 

The easiest fix for me is to:

- Unplug power from the cable modem
- Unplug power from the router
- Wait like 15 seconds
- Go back to the cable modem and replug it in for power
- Go back to the router and replug it in for power

That process re-establishes the handshake protocol that was previously lost. 

Original comment by James.W....@gmail.com on 14 Jul 2013 at 2:50

[GoogleCodeExporter]

RT-56U running 3.4.3.6-064

I have noticed a lot of disconnects in the last few weeks +- 10-15 per day. 
Has this issue perhaps resurfaced in the latest firmwares as it is quite recent.
Seems to happen when the router is being used for gaming etc.
Am thinking of rolling back to older version of firmware to see if this sorts 
the problem.

Original comment by brinkman...@gmail.com on 21 Jul 2013 at 3:57

[GoogleCodeExporter]

Have rolled back to 3.0.3.3-045 and the disconnects seem to have stopped so 
far, has anyone else experienced this problem? 

Original comment by brinkman...@gmail.com on 21 Jul 2013 at 6:11

[GoogleCodeExporter]

Have only had one ADSL disconnect since I downgraded my firmware to 3.0.3.3-045 
(2 days ago), I will upgrade to newer versions and see when the  disconnects 
start again so I can see where the issues began.

Original comment by brinkman...@gmail.com on 23 Jul 2013 at 2:11

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

SOLVED. Update to the latest firmware: 
http://www.asus.com/Networking/RTN56U/#support_Download_30

 Version 3.0.0.4.374.239
Description     ASUS RT-N56U Firmware Version 3.0.0.4.374.239
Fixed:
1. Fixed HK ISP DHCP connection issue.
2. Fixed USB application update related issues.

 Version 3.0.0.4.374.130
Description     ASUS RT-N56U Firmware Version 3.0.0.4.374.130
Fixed:
1. Fixed AiCloud vulnerability related bugs.
2. Underline "_" can now be acceptable in device name and computer name.
3. Hide Broadcast option in PPTP VPN server when it is disabled.
4. Fixed multicast IPTV related issues in PPPoE/PPTP/L2TP connection.
5. Fixed IE related parental control issues.
6. Fixed 3G dongle related issue.
7. Hide ASUS DDNS description when selecting 3rd party service.
8. Fixed script error 'invalid argument on IE'
9. Fixed smart sync JS error
10. Fixed JST time zone issue.
11. Reduced the redundant packets when used 3G/4G dongle as WAN and opened web 
browser.
12. Fixed the traffic monitor related issues when used 3G/4G dongle as WAN,
13. Fixed client duplicated issue in network map
14. removed modem setting button in AP mode
15. 2.4Ghz compatibility issue for some specific devices

Added:
1. Auto adjust time zone in internet setup wizard process.
2. PPTP VPN server status GUI
3. Recognized .rmvb files as video format in media server.
4. Show more detail information in USB application install process.
5. Unmount all disks with 1-click

IPv6
1. Fixed PPP IPv6 global address retrieval
2. added DHCP-PD option
3. Added LAN DHCPv6 server
4. Added network status GUI.
5. Added option domain name if available

3G/4G dongles
1. Support Yota LTE dongle LU150
2. Support ZTE LTE dongle MF821
3. Support 3G dongle Q110
4. Support Huawei EC306

Original comment by mateusz....@gmail.com on 2 Sep 2013 at 3:00

[GoogleCodeExporter]

I am running the most recent Padavan firmware 3.4.3.6-068. I have the WAN 
disconnect issue and it is driving me nuts. My router was rock solid for almost 
2 years. I didn't have to reset it until a month ago when the WAN disconnects 
started.

Should I just go back to the most recent ASUS firmware that the comment above 
states resolves the issue? I haven't tried a different router or modem yet. 
Modem (Cisco DSP3010) is probably about as old as the router.

Thanks for any feedback.

Here is my log from today. The router was fine for about 12 hours and then the 
WAN disconnects came back. I have already tried a new cable between router and 
modem and unplugged both for about an hour last night to get a good reset with 
my ISP.

Sep  5 09:15:20 inadyn[549]: Checking for IP# change, connecting to 
checkip.dyndns.org(216.146.38.70)
Sep  5 09:15:21 inadyn[549]: No IP# change detected, still at 68.
Sep  5 10:59:17 detect_link: WAN link down detected!
Sep  5 10:59:29 detect_link: WAN link restored!
Sep  5 10:59:33 detect_link: Perform WAN DHCP renew...
Sep  5 11:48:11 detect_link: WAN link down detected!
Sep  5 11:48:29 detect_link: WAN link restored!
Sep  5 11:48:33 detect_link: Perform WAN DHCP renew...
Sep  5 11:48:33 DHCP WAN Client: Received NAK for eth3
Sep  5 11:48:33 RT-N56U: wan down (eth3)
Sep  5 11:48:33 DHCP WAN Client: deconfig: lease is lost
Sep  5 11:48:37 RT-N56U: wan up (eth3)
Sep  5 11:48:37 DHCP WAN Client: bound (eth3), IP: 192.168.100.10, GW: 
192.168.100.1, lease time: 30
Sep  5 11:48:37 inadyn[1250]: Inadyn version 1.99.2 -- Dynamic DNS update 
client.
Sep  5 11:48:37 inadyn[1250]: Cached IP# 68. from previous invocation.
Sep  5 11:48:47 NTP Scheduler: Synchronizing time to time.nist.gov.
Sep  5 11:49:01 detect_link: WAN link down detected!
Sep  5 11:49:13 detect_link: WAN link restored!
Sep  5 11:49:17 detect_link: Perform WAN DHCP renew...
Sep  5 11:49:18 RT-N56U: wan down (eth3)
Sep  5 11:49:18 DHCP WAN Client: deconfig: lease is lost
Sep  5 11:49:19 RT-N56U: wan up (eth3)
Sep  5 11:49:19 DHCP WAN Client: bound (eth3), IP: 68., GW: 68., lease time: 
86400
Sep  5 11:49:24 inadyn[1250]: Checking for IP# change, connecting to 
checkip.dyndns.org(216.146.38.70)
Sep  5 11:49:24 inadyn[1250]: No IP# change detected, still at 68.
Sep  5 11:49:24 inadyn[1310]: Inadyn version 1.99.2 -- Dynamic DNS update 
client.
Sep  5 11:49:24 inadyn[1310]: Cached IP# 68. from previous invocation.
Sep  5 11:49:24 inadyn[1310]: Checking for IP# change, connecting to 
checkip.dyndns.org(91.198.22.70)
Sep  5 11:49:24 inadyn[1310]: No IP# change detected, still at 68.
Sep  5 11:49:33 NTP Scheduler: Synchronizing time to pool.ntp.org.

Original comment by hg8rd...@gmail.com on 5 Sep 2013 at 10:26

[GoogleCodeExporter]

Tried the latest Asus firmware. Installed it in morning and internet was down 
in evening. Going back to Padavan, at-least it will be stable for 1-2 days

Original comment by sreedhar...@gmail.com on 6 Sep 2013 at 4:21

[GoogleCodeExporter]

Latest firmware did nothing for me. Disconnect issue still occurs.

Original comment by TheSte...@gmail.com on 8 Sep 2013 at 12:42

[GoogleCodeExporter]

Follow up to comment #94...

Sept 6 - I had disconnects for about an hour solid, but that was due to ISP. I 
sat there and watched my modem go up and down.

Sept 7 - DHCP lease renewed and then the WAN disconnects happened for about a 
minute.

Sept 8 & 9 - NO WAN DISCONNECTS!! Going on approximately 70 hours of up time 
and no issues.

Still running Padavan firmware 3.4.3.6-068

Hopefully this is the start of a new trend. 

Original comment by hg8rd...@gmail.com on 10 Sep 2013 at 3:55

[GoogleCodeExporter]

Still having WAN disconnect issues on ADSL but have noticed that when I 
switched my connection to a USB 3G dongle there are no disconnects on 
3.4.3.6-068

Original comment by brinkman...@gmail.com on 12 Sep 2013 at 5:39

[GoogleCodeExporter]

<SOLVED so far...>
Previous Equipment
Modem: Motorola Surboard SB5101u
Router: Asus RT-n56u, Padavan firmware 3.4.3.6-068 

Now
Modem: CISCO dpc3008 
Router: Asus RT-n56u, Padavan firmware 3.4.3.6-068

Similar issue to comment #94, I dug a little deeper into the problem and 
thought I should check my modem logs by typing 192.168.100.1 into the address 
bar and saw revealed a whole new can of google searches.

This link comes to mind:
http://forums.cox.com/forum_home/internet_forum/f/5/t/2042.aspx

Before my internet would go down, it would do the following:

(3x)
<Started Unicast Maintenance Ranging - No Response received - T3 time-out>
<DCC-ACK not received>

then
<Modem Is Shutting Down and Rebooting...>

The link said to upgrade the modem's firmware but I wouldn't recommend that.

Then I came across this link:
http://forums.comcast.com/t5/Basic-Internet-Connectivity-And/Cable-modem-resets-
extremely-often-under-heavy-and-no-traffic/td-p/1162555

the EG - Connection Expert says,
"Re: Cable modem resets extremely often under heavy and no traffic [ Edited ]
Options
‎01-12-2012 05:45 PM - edited ‎01-12-2012 05:46 PM

The upstream power is too high and may be intermittently fluctuating even 
higher out of spec.That will cause random disconnects and spontaneous 
re-booting of the modem. Are there any excess/unneeded coax cable splitters in 
that line leading to the modem that can be eliminated/re-configured ? If not, 
perhaps another tech visit is in order to investigate and correct."

I called the Comcast tech guy and explained what was happening, so he switch 
the location of the modem to a different room and switched out the modem ("I 
don't that was the cause but he is the tech guy") so the upstream level wasn't 
so high.

Because I don't feel like paying the $7 monthly rental fee, I will eventually 
switch out their modem with mine if this new fix is stable. 

So far so good.

Original comment by rey...@gmail.com on 24 Sep 2013 at 8:13

[GoogleCodeExporter]

#99, interesting though, you may be onto something. I have the Scientific 
Atlanta Webstar DCP2100 but my levels seem within range, according to the 
192.168.100.1 system panel.

Receive Power Level: 1.3 dBmV
Transmit Power Level: 54.0 dBmV

The panel doesn't tell me Signal-to-Noise ratio though. Is there any other way 
I can check the SnR?

FWIW, my disconnects typically happen when I download something intense for an 
extended amount of time (e.g. a 6gb game through Steam that requires at least 
an hour+ of downloading). The disconnects will happen around the 20-30 minute 
marker.

If I DON'T download anything, the router pretty much stays online without any 
qualms. I am running an older Asus 3.0.0.3.135 beta firmware - it has been the 
most stable for me (believe it or not). 

Does anyone know if the bigger brother Asus rt-n66u is affected by this WAN 
disconnect problem? I am thinking about upgrading because I've dealt with this 
WAN disconnect issue for nearly two years now.

Original comment by James.W....@gmail.com on 26 Sep 2013 at 2:43