goolee-jch / rt-n56u

Automatically exported from code.google.com/p/rt-n56u
0 stars 0 forks source link

WAN Disconnects #23

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
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:

GoogleCodeExporter commented 9 years ago
RE: #100

Before you do anything drastic like,
 - upgrade equipment
 - or flashing the firmware
 - or call the tech guy if it isn't free
 - or send a complaint email to Asus before doing your homework (which I now regret), make sure you understand every level of your network first.

Signal-to-Noise ratio, rule of thumb: the higher the better, I don't it's an 
issue for you. You should look at your power levels and check the modem's 
manual and see what the norm is. 

Before my setup change my upstream power level was at 52.0 dBmV - 56 dBmV, 
which was way too high. So the tech guy found a room in the apartment where he 
was able to drop it to 46 - 47 dBmV. 

My current setup is still without any issues.
Modem: CISCO dpc3008 
Router: Asus RT-n56u, Padavan firmware 3.4.3.6-068

Original comment by rey...@gmail.com on 28 Sep 2013 at 1:19

GoogleCodeExporter commented 9 years ago
RE: #101

My Power Levels and SnR Levels are fine and within optimal ranges.

As a matter of fact, I have my PC *directly connected* to the Cable Modem as I 
type this and am downloading heavy data (18gb worth of games through Steam). NO 
disconnects so far and it's been an hour+.

If I went through the router, the WAN disconnects would happen around the 20-30 
minute marker (or 40 minutes if I'm lucky).

In other words, the rt-n56u router IS AND HAS BEEN THE ISSUE -- it simply can't 
handle heavy data downloads without disconnecting/losing its DHCP handshake 
with the cable modem.

I've tried multiple firmwares (Stock Asus, Padavan, Asus Betas) and simply 
can't take it anymore. Time to shop for a new router...

Original comment by James.W....@gmail.com on 6 Oct 2013 at 11:34

GoogleCodeExporter commented 9 years ago
RE: #101 (update to my post #102)

I'm now going on 2+ hours of straight downloading with the Cable Modem that's 
directly connected to the PC. NO DISCONNECTS.

Original comment by James.W....@gmail.com on 7 Oct 2013 at 12:27

GoogleCodeExporter commented 9 years ago
RE: #103 

It's good to hear that something is working.

Email Asus and explain your trouble-shooting methodology. They responded to me 
even though I ended up being wrong.
cl-celeste@asus.com 

Original comment by rey...@gmail.com on 10 Oct 2013 at 2:44

GoogleCodeExporter commented 9 years ago
Hey #103, thanks for the reply! I might have found a solution.

The Asus firmware from earlier this year (version 3.0.0.4.342) seemed to have 
done the trick. I was able to download a 9gb game from Steam last night with no 
issues. I will continue testing this firmware and hope for the best.

Although Asus has removed the link in favor of newer firmware revisions 
(3.0.0.4.360 and 3.0.0.4.372), those versions seem to have common issues.

.360 - folks on SmallNetBuilder.com commonly reported disconnects and a slightd 
drop in speed
.372 - folks on SmallNetBuilder.com commonly reported a drastic drop in 
wireless signal as reported through programs like InSSIDer (even for devices 
that sit next to the router).

Let's hope that the .342 revision is the last firmware I'll need before getting 
the upgrade itch (those 802.11ac are sure tempting...)!

Original comment by James.W....@gmail.com on 10 Oct 2013 at 2:57

GoogleCodeExporter commented 9 years ago
huzzah

Original comment by rey...@gmail.com on 21 Oct 2013 at 3:30

GoogleCodeExporter commented 9 years ago
Thanks, James! version 3.0.0.4.342 seems to be working fine! 

Original comment by rafa.vi...@gmail.com on 13 Nov 2013 at 11:19

GoogleCodeExporter commented 9 years ago
I'd like to try firmware version 3.0.0.4.342, but it's no longer on the asus 
website. Can someone please tell me where to find a copy?

Original comment by beery...@gmail.com on 19 Nov 2013 at 2:43

GoogleCodeExporter commented 9 years ago
Here you go: 
http://202.221.139.247/pub/asustw/wireless/RT-N56U/FW_RT_N56U_3004342.zip

Original comment by rafa.vi...@gmail.com on 19 Nov 2013 at 2:49

GoogleCodeExporter commented 9 years ago
Thank you very much!!

Original comment by beery...@gmail.com on 19 Nov 2013 at 2:57

GoogleCodeExporter commented 9 years ago
Let us know if it worked out for you

Original comment by rafa.vi...@gmail.com on 19 Nov 2013 at 2:59

GoogleCodeExporter commented 9 years ago
Two weeks with no lease losses, yay!

Firmware version 3.0.0.4.342 seems to have fixed my problems. I was previously 
losing my lease 2-3 times a week, Charter cable, SB6121 modem, and Asus RT-N56U.

Thanks again.

Original comment by beery...@gmail.com on 6 Dec 2013 at 4:05

GoogleCodeExporter commented 9 years ago
I had the same problem here for almost two years! Looking at the log, every 
time I had a WAN connection drop I could see message "WAN down".

The solution for it came looking at issue #398: In router's web GUI, simply go 
to menu path Administration --> Console and issue the following two commands, 
clicking the Refresh button right after typing each one:

nvram set detectWan=0
nvram commit

I'm no sure if case matters, so stick exactly with the above.

The first command disables the WAN detect logic and the second one commits the 
changes to the router's NVRAM.

After that I have not experienced any WAN connection drops anymore, for one 
week now.

Ahhh, I have also disabled Green Ethernet using router's menu path LAN --> 
Ethernet Switch.

I hope that helps...

Cheers!

Original comment by lino2...@gmail.com on 19 Apr 2014 at 1:50

GoogleCodeExporter commented 9 years ago
With Asus RT-N56U running firmware RT-N56U_3.0.3.7-079_base.trx and a Zyxel 
P-2812HNU-F1 VDSL modem running firmware version V3.11(TUE.5)-2_20130819 and 
set to bridge, the Asus RT-N56U suffers from the dreaded " detect_link: WAN 
link down detected!" issue at intervals of exactly 5 minutes and 26 seconds.

Even when "ARP Ping Alive of Remote Gateway?" is turned off.
======
Wireless & Wired Info - WAN
======
Port Link           : 1000 Mbps, Full Duplex

MIB Counters
----------------------------------------
ifInOctets          : 23346524330
ifOutOctets         : 2200895611
etherStatsMcastPkts     : 30950
etherStatsBcastPkts     : 4223
etherStatsFragments     : 8
etherStatsDropEvents        : 0
etherStatsUndersizePkts     : 0
etherStatsOversizePkts      : 0
etherStatsCollisions        : 0
dot3StatsFCSErrors      : 25039
dot3StatsSymbolErrors       : 6288
dot3ControlInUnknownOpcodes : 0
dot3InPauseFrames       : 0
dot3OutPauseFrames      : 0
======

Log with 3 events at 5 minute 26 seconds intervals:
======
Apr 26 23:10:54 detect_link: WAN link down detected!
Apr 26 23:11:06 detect_link: WAN link restored!
Apr 26 23:11:10 detect_link: Perform WAN DHCP renew...
Apr 26 23:11:14 detect_link: WAN link down detected!
Apr 26 23:11:16 detect_link: WAN link restored!
Apr 26 23:11:28 RT-N56U: wan down (eth3)
Apr 26 23:11:28 DHCP WAN Client: deconfig: lease is lost
Apr 26 23:12:03 RT-N56U: wan up (eth3)
Apr 26 23:16:20 detect_link: WAN link down detected!
Apr 26 23:16:34 detect_link: WAN link restored!
Apr 26 23:16:38 detect_link: Perform WAN DHCP renew...
Apr 26 23:16:40 detect_link: WAN link down detected!
Apr 26 23:16:42 detect_link: WAN link restored!
Apr 26 23:16:56 RT-N56U: wan down (eth3)
Apr 26 23:16:56 DHCP WAN Client: deconfig: lease is lost
Apr 26 23:17:31 RT-N56U: wan up (eth3)
Apr 26 23:21:48 detect_link: WAN link down detected!
Apr 26 23:22:00 detect_link: WAN link restored!
Apr 26 23:22:04 detect_link: Perform WAN DHCP renew...
Apr 26 23:22:08 detect_link: WAN link down detected!
Apr 26 23:22:10 detect_link: WAN link restored!
Apr 26 23:22:22 RT-N56U: wan down (eth3)
Apr 26 23:22:22 DHCP WAN Client: deconfig: lease is lost
Apr 26 23:22:58 RT-N56U: wan up (eth3)
=======
And suddenly the issue is gone after this logged line:
=======
Apr 28 03:24:50 RT-N56U: wan up (eth3)
=======

Original comment by i...@vakantieland.nl on 28 Apr 2014 at 4:14

GoogleCodeExporter commented 9 years ago
Hey Guys,

I've been experiencing a frustrating problem with my N56U for several months.  
Although it isn't precisely the same issue as the one described here, I am 
sharing it in case it sheds any light on the problem.

My N56U is configured in Access Point mode, with a static IP address.  Several 
times every day, wireless clients lose connectivity for a few minutes.  I can 
provoke the problem (though not every time) by running a speed test using 
speedtest.net (website or Android app).  I have disabled pretty much everything 
other than the 2.4GHz signal, and even tried cooling the device with a fan! 
(I've seen posts describing overheating problems.)  I have considered the 
ultimate solution several times - a large hammer.  Getting an N66U is the next 
option, though this whole experience has made me think twice about buying 
another Asus router.

I'm running Padavan's latest firmware (3.0.3.8-081), but I have seen the 
problem with at least the last 2 or 3 releases (I'm not pointing the finger at 
the firmware here).

There is nothing in the system log indicating any problem.  Is there a way to 
switch on additional logging to help diagnose the problem?

Any suggestions would be much appreciated.

Alan.

Original comment by ogilv...@gmail.com on 15 Jun 2014 at 1:59

GoogleCodeExporter commented 9 years ago
Hello,
Could you please add some details... What do you mean by "wireless clients lose 
connectivity for a few minutes."? A client can't connect to the internet or it 
can't connect to wireless network at all?
What device is N56U connected to (I guess there is some router before it)?

Original comment by d...@soulblader.com on 16 Jun 2014 at 9:37

GoogleCodeExporter commented 9 years ago
Hi,

Thanks for the reply.

The router itself (and, I guess (but cannot absolutely confirm), other systems 
on the local network) is still contactable, i.e. it is possible to login to the 
web interface from a wireless client, even though the client is unable to 
access the internet.

The N56U is ethernet-connected to a (crappy) Technicolor TG582n, but the 
problem also occurred with my previous (equally crappy) Sky SR101 router.

Interestingly, this evening I downgraded the firmware to 3.4.3.7-072, and have 
yet to see the problem since... but it's only been a couple of hours, so let's 
give it a little longer before pointing the finger at the firmware...

Original comment by ogilv...@gmail.com on 16 Jun 2014 at 10:25

GoogleCodeExporter commented 9 years ago
For "The router itself", read "The N56U itself".

Original comment by ogilv...@gmail.com on 16 Jun 2014 at 10:28

GoogleCodeExporter commented 9 years ago
Oh dear... forget that!  I just reproduced the problem with firmware 
3.4.3.7-072  :-(

<Step away from the hammer...>

Original comment by ogilv...@gmail.com on 16 Jun 2014 at 10:44

GoogleCodeExporter commented 9 years ago
OK, another update... (sorry)

I'm not sure if this is anything to do with the older firmware or if I was just 
hallucinating with the newer versions, but when I just reproduced the issue 
again I was unable to contact the N56U *at all* from the wireless client.  
After about a minute, the N56U came back to life again (same behaviour as with 
the newer firmwares).

Original comment by ogilv...@gmail.com on 16 Jun 2014 at 10:54

GoogleCodeExporter commented 9 years ago
Have you checked syslog after that? Any "strange" records?...

Original comment by d...@soulblader.com on 17 Jun 2014 at 5:41

GoogleCodeExporter commented 9 years ago
There's nothing in the system log, apart from the messages from the most recent 
boot and the daily ntp clock updates.

Original comment by ogilv...@gmail.com on 17 Jun 2014 at 6:00

GoogleCodeExporter commented 9 years ago
I have the same problem here. After 30-40 min my N56u lost connection. Im using 
last firmware 3.0.3.8-081. This appears when I download some large files, like 
4 GB. After some time, my router lost connection. I tried to connect moden 
directly to my computer and no problem.

Original comment by horst.ma...@gmail.com on 4 Jul 2014 at 5:23

GoogleCodeExporter commented 9 years ago
Hi there. Just for notice: I followed post " #113 lino2...@gmail.com " 
instructions, and appears to be functional here. Now my router doesnt lost 
connection, even with huge and sequentional downloads. Thanks!

Original comment by horst.ma...@gmail.com on 9 Jul 2014 at 8:10

GoogleCodeExporter commented 9 years ago
I am having similar problems although my setup is much more complicated.
I need to cover a 3 levels building with wireless signal and I bought 4 of 
these routers.
On the ground floor there is one with DHCP enabled, working on wireless channel 
1 + 5
It gets the WAN from a wired network, on a static IP. It has the LAN IP 
192.168.1.1
Also on the ground floor I have another router, DHCP disabled, IP 192.168.1.2 
and wireless channel 4 + 8. This router is configured as a wireless access 
point.
First floor, another router configured as a wireless access point, on IP 
192.168.1.3, wireless channels 7 + 11
Second floor, configured as a wireless access point, IP 192.168.1.4, wireless 
channels 13 + 9
All the routers have the same encryption, SSID, password.
The configuration is highly unstable, the wireless clients (lots of them) get 
disconnected each minute for a few seconds.
I tried many things, disconnected some of the routers one by one, disabled the 
5 GHz wireless, disabled Green Ethernet, etc, but situation doesn't change too 
much.
I tried latest Padavan firmware (right now I have it the routers) but the error 
still persists.
In the log I see only the usual stuff: NTP connections, etc.
This topic made me wondering if I don't have the same problem: WAN disconnects.

Please advise,

Janos

Original comment by janos...@gmail.com on 23 Jul 2014 at 11:05

GoogleCodeExporter commented 9 years ago
Hi I am using 3.0.3.8-081 now and I don't exactly know if this is router 
firmware problem or my crappy ISPs problem. I am using a adsl modem in bridge 
mode. Even though wan is connected but every 10 minutes or so I loose internet 
connection or 10 seconds ( no wan disconnect). My voip calls gets disconnected, 
my vpn and rdp takes a little time to reconnect. It is driving me nuts. Today I 
have downgraded to 3.0.3.8-080, I will update the results. ( only problem with 
the 3.0.3.8-080 is when wan is not connected cup usage is 100% 

Original comment by lamad...@gmail.com on 5 Aug 2014 at 11:40

GoogleCodeExporter commented 9 years ago
This problem doesn't exist on the OpenWRT firmware which you can download from 
http://downloads.openwrt.org/barrier_breaker/14.07-rc2/ramips/rt3883/ . I've 
used it successfully and did not experience any problems for so long:

root@OpenWrt:/proc# uptime
 20:38:10 up 3 days,  6:48,  load average: 0.00, 0.01, 0.04

When using Asus RT-N56U stock firmware or any versions of Padavan up to 
3.0.3.8-081, all experienced disconnects in less than a day.

Original comment by chu...@gmail.com on 5 Aug 2014 at 12:39

GoogleCodeExporter commented 9 years ago
sorry for my previous comment. It was my shitty ISP's doing. Switching back to 
3.0.3.8-081 and changing ISP ASAP.

Original comment by lamad...@gmail.com on 8 Aug 2014 at 1:27

GoogleCodeExporter commented 9 years ago
Also thanks for the openwrt suggestion, way too complex for us laymen.  

Original comment by lamad...@gmail.com on 8 Aug 2014 at 1:35

GoogleCodeExporter commented 9 years ago
Well, my problem with disconnects come back =/. When I use directcly without 
router thats not happen.

Original comment by horst.ma...@gmail.com on 8 Aug 2014 at 8:53

GoogleCodeExporter commented 9 years ago
Good afternoon everyone, I'm not an expert but I am somewhat tech savvy. I've 
been suffering from this issue for years. I've tried replacing modem and using 
other routers and only have this issue on rt-n56u. I tried playing with some 
settings and one setting change that seemed to work for me was lowering the TX 
power of the 2.4 band to 80 (was 100 by default). I believe 5 GHz band was at 
30 by default. If others could give this a try to verify if what I'm seeing is 
accurate, it would be appreciated. I went 3 weeks before seeing another WAN 
disconnect. 

Original comment by bttan...@gmail.com on 25 Aug 2014 at 7:49

GoogleCodeExporter commented 9 years ago
To the above. I still get the issues. Nothing seems to have worked after 
installing the newest firmware on this or official. Not as frequent but still 
happening.

Original comment by VineetKM...@gmail.com on 16 Sep 2014 at 4:56

GoogleCodeExporter commented 9 years ago
Try this, been using it since Jul 10, 2012 flawlessly: 
http://202.221.139.247/pub/asustw/wireless/RT-N56U/FW_RT_N56U_3004342.zip

Original comment by rafa.vi...@gmail.com on 16 Sep 2014 at 6:41

GoogleCodeExporter commented 9 years ago
Mine is the 65U Version. I didn't see a topic for it separately. So I posted it 
here.

Original comment by VineetKM...@gmail.com on 20 Sep 2014 at 11:15

GoogleCodeExporter commented 9 years ago
I try tu use the last version of official rom, and no way. Having internet 
drops again. I try to switch eth cables too, but no lucky, no hope, no feith. 
Damm it!

Original comment by horst.ma...@gmail.com on 22 Sep 2014 at 3:03

GoogleCodeExporter commented 9 years ago
I am having a similar issue with the ac68U I am using a Merlin Build (I think 
Asus uses his builds to beta there builds) which is as easy as the regular 
firmware with a couple of tweaks.  Based on what I have read here: 
http://forums.smallnetbuilder.com/showthread.php?t=8433
I am to turn off the router for 10 minutes then try again.  This will force the 
router, modem to reread everything...

Original comment by gl.newh...@gmail.com on 22 Sep 2014 at 11:34

GoogleCodeExporter commented 9 years ago
Well well well. I received a technical operator from ISP in my house and he 
make some changes in signal. Know, my router still rock solid after 4 days. 
Sorry about previous messages, and thats a suggestion for those with problems.

Original comment by horst.ma...@gmail.com on 18 Dec 2014 at 9:55