WRT610N v1 unstable

Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware
Goto page Previous  1, 2, 3, 4  Next
View previous topic :: View next topic  
Author Message
drapos
DD-WRT Novice


Joined: 01 Jun 2012
Posts: 19
PostPosted: Fri Nov 14, 2014 21:41    Post subject: Reply with quote
18946M here. Any other newer version always ended giving me problems, so I downgraded to this wellknown working version at one point.
Back to top View user's profile Send private message
Sponsor
kevindd992002
DD-WRT User


Joined: 27 Feb 2009
Posts: 457
PostPosted: Fri Nov 14, 2014 23:50    Post subject: Reply with quote
drapos wrote:
18946M here. Any other newer version always ended giving me problems, so I downgraded to this wellknown working version at one point.


What kind of problems were you experiencing with the higher versions?
Back to top View user's profile Send private message
kevindd992002
DD-WRT User


Joined: 27 Feb 2009
Posts: 457
PostPosted: Mon Dec 08, 2014 3:31    Post subject: Reply with quote
bump!
Back to top View user's profile Send private message
LOM
DD-WRT Guru


Joined: 28 Dec 2008
Posts: 7647
PostPosted: Mon Dec 08, 2014 3:50    Post subject: Re: WRT610N v1 unstable Reply with quote
kevindd992002 wrote:

The problem I'm having is that randomly the 2.4GHz signal of the unit is not detected and I have the erase the nvram and restore from backup to fix it. This happened already many times and I really don't know the problem. I reckon that this was a problem with the initial releases of this unit but the build I have is pretty recent.



Sounds like the problem you get when nvram gets filled up and overflows. Turn off ttraff saving to nvram if nvram overflow is the problem.

You can check nvram usage by entering

nvram show | grep size

in the command box under the Administration tab.
_________________
Kernel panic: Aiee, killing interrupt handler!
Back to top View user's profile Send private message
kevindd992002
DD-WRT User


Joined: 27 Feb 2009
Posts: 457
PostPosted: Mon Dec 08, 2014 4:44    Post subject: Re: WRT610N v1 unstable Reply with quote
LOM wrote:
kevindd992002 wrote:

The problem I'm having is that randomly the 2.4GHz signal of the unit is not detected and I have the erase the nvram and restore from backup to fix it. This happened already many times and I really don't know the problem. I reckon that this was a problem with the initial releases of this unit but the build I have is pretty recent.



Sounds like the problem you get when nvram gets filled up and overflows. Turn off ttraff saving to nvram if nvram overflow is the problem.

You can check nvram usage by entering

nvram show | grep size

in the command box under the Administration tab.


Interesting. It happened to me again yesterday. What is the cause of this? And how can I turn off ttraff saving?

This is the size NOW (after I restored from backup again):

size: 29333 bytes (3435 left)
Back to top View user's profile Send private message
LOM
DD-WRT Guru


Joined: 28 Dec 2008
Posts: 7647
PostPosted: Mon Dec 08, 2014 6:47    Post subject: Reply with quote
You can check the two possible sources for growing nvram with:

nvram show | grep traff

nvram show | grep forward_port

ttraff is under Services - WAN Traffic Counter enable/disable. It is maybe not the reason since it consumes less than 200 bytes/month.

If you have UPnP enabled then there will be many applications knowing how to open a port and not giving a shit about closing the port when the program exits.
There is a setting under NAT/QOS - UPnP - Clear port forwards at startup.
Enable it and the growing list of automatic port forwards will at least be cleared every time router boots.

Otherwise wait until the problem appears next time and check the size of nvram to see if the remaining 3.5KB has been used. Or run the cmd once weekly to see if nvram grows and with how much.
_________________
Kernel panic: Aiee, killing interrupt handler!
Back to top View user's profile Send private message
kevindd992002
DD-WRT User


Joined: 27 Feb 2009
Posts: 457
PostPosted: Mon Dec 08, 2014 7:48    Post subject: Reply with quote
Gotcha, I'll do that. Is this a router limitation though or a dd-wrt firmware version bug?
Back to top View user's profile Send private message
LOM
DD-WRT Guru


Joined: 28 Dec 2008
Posts: 7647
PostPosted: Mon Dec 08, 2014 8:24    Post subject: Reply with quote
It's an nvram limitation, you have only 32KB and that is a limitation the mfgr is responsible for.
Routers with dual radio really need 64KB because there are lots of long radio parameter strings in nvram.
Single radio routers use around 24KB so you have much more headroom in them.
_________________
Kernel panic: Aiee, killing interrupt handler!
Back to top View user's profile Send private message
kevindd992002
DD-WRT User


Joined: 27 Feb 2009
Posts: 457
PostPosted: Mon Dec 08, 2014 8:33    Post subject: Reply with quote
LOM wrote:
It's an nvram limitation, you have only 32KB and that is a limitation the mfgr is responsible for.
Routers with dual radio really need 64KB because there are lots of long radio parameter strings in nvram.
Single radio routers use around 24KB so you have much more headroom in them.


And the 32KB nvram is saturated how? Because of dd-wrt?
Back to top View user's profile Send private message
LOM
DD-WRT Guru


Joined: 28 Dec 2008
Posts: 7647
PostPosted: Tue Dec 09, 2014 3:47    Post subject: Reply with quote
kevindd992002 wrote:
LOM wrote:
It's an nvram limitation, you have only 32KB and that is a limitation the mfgr is responsible for.
Routers with dual radio really need 64KB because there are lots of long radio parameter strings in nvram.
Single radio routers use around 24KB so you have much more headroom in them.


And the 32KB nvram is saturated how? Because of dd-wrt?


dd-wrt with more applications (ie more settings) makes the problem appear earlier than it does on stock firmware.
WRT610v2 which was short lived did also have 32KB available nvram space but got renamed to E3000 with available nvram increased to 60KB.
Mfgrs has learned after having to replace routers under RMA and then finding out that many of them only had an overflowed nvram.
_________________
Kernel panic: Aiee, killing interrupt handler!
Back to top View user's profile Send private message
kevindd992002
DD-WRT User


Joined: 27 Feb 2009
Posts: 457
PostPosted: Tue Dec 09, 2014 4:01    Post subject: Reply with quote
LOM wrote:
kevindd992002 wrote:
LOM wrote:
It's an nvram limitation, you have only 32KB and that is a limitation the mfgr is responsible for.
Routers with dual radio really need 64KB because there are lots of long radio parameter strings in nvram.
Single radio routers use around 24KB so you have much more headroom in them.


And the 32KB nvram is saturated how? Because of dd-wrt?


dd-wrt with more applications (ie more settings) makes the problem appear earlier than it does on stock firmware.
WRT610v2 which was short lived did also have 32KB available nvram space but got renamed to E3000 with available nvram increased to 60KB.
Mfgrs has learned after having to replace routers under RMA and then finding out that many of them only had an overflowed nvram.


Ah ok. Other than that there's no other possible cause for this issue, right?
Back to top View user's profile Send private message
kevindd992002
DD-WRT User


Joined: 27 Feb 2009
Posts: 457
PostPosted: Sun Jan 25, 2015 2:37    Post subject: Reply with quote
LOM wrote:
You can check the two possible sources for growing nvram with:

nvram show | grep traff

nvram show | grep forward_port

ttraff is under Services - WAN Traffic Counter enable/disable. It is maybe not the reason since it consumes less than 200 bytes/month.

If you have UPnP enabled then there will be many applications knowing how to open a port and not giving a shit about closing the port when the program exits.
There is a setting under NAT/QOS - UPnP - Clear port forwards at startup.
Enable it and the growing list of automatic port forwards will at least be cleared every time router boots.

Otherwise wait until the problem appears next time and check the size of nvram to see if the remaining 3.5KB has been used. Or run the cmd once weekly to see if nvram grows and with how much.


I just noticed that my 2.4GHz went off again and I did the commands listed above. Here's what I got:

1.) nvram show | grep traff

size: 32777 bytes (-9 left)
traff-01-2015=13:3 0:0 0:0 0:0 0:0 23:3 0:0 0:0 1566:79 14370:426 7684:281 4918:276 95528:2028 0:0 3869:128 0:0 0:0 0:0 0:0 4662:183 5506:121 14559:402 3077:270 8519:455 2181:165 0:0 0:0 0:0 0:0 0:0 0:0 [166475:4820]
ping_ip=nvram show | grep traff
traff-12-2014=0:0 0:0 0:0 0:0 0:0 0:0 1154:1071 9103:1853 0:0 5201:484 10175:272 0:0 2912:68 3544:84 0:0 0:0 0:0 11145:276 0:0 479:227 3027:824 16689:785 138:32 124:17 20:3 122:51 4601:2887 1647:890 2963:208 0:0 0:0 [73044:10032]
traff-10-2014=0:0 0:0 0:0 0:0 13:0 0:0 0:0 0:0 0:0 0:0 0:0 0:0 0:0 0:0 0:0 0:0 0:0 0:0 0:0 0:0 0:0 0:0 0:0 0:0 0:0 0:0 0:0 0:0 0:0 0:0 0:0 [13:0]
ttraff_enable=1

2.) nvram show | grep forward_port

forward_port10=3722-3722>192.168.1.210:3722-3722,udp,on,Skype UDP at 192.168.1.210:3722 (2908)
forward_port11=3722-3722>192.168.1.210:3722-3722,tcp,on,Skype TCP at 192.168.1.210:3722 (2908)
forward_port12=36233-36233>192.168.1.211:36233-36233,udp,on,Skype UDP at 192.168.1.211:36233 (2908)
forward_port13=36233-36233>192.168.1.211:36233-36233,tcp,on,Skype TCP at 192.168.1.211:36233 (2908)
forward_port14=26645-26645>192.168.1.144:26645-26645,udp,on,Skype UDP at 192.168.1.144:26645 (2917)
forward_port15=26645-26645>192.168.1.144:26645-26645,tcp,on,Skype TCP at 192.168.1.144:26645 (2917)
forward_port16=64615-64615>192.168.1.210:64615-64615,udp,on,Teredo
forward_port17=33878-33878>192.168.1.144:33878-33878,udp,on,Skype UDP at 192.168.1.144:33878 (2919)
forward_port18=33878-33878>192.168.1.144:33878-33878,tcp,on,Skype TCP at 192.168.1.144:33878 (2919)
forward_port19=25611-25611>192.168.1.113:25611-25611,udp,on,Skype UDP at 192.168.1.113:25611 (2919)
forward_port20=25611-25611>192.168.1.113:25611-25611,tcp,on,Skype TCP at 192.168.1.113:25611 (2919)
forward_port21=63245-63245>192.168.1.212:63245-63245,udp,on,Teredo
forward_port22=26645-26645>192.168.1.144:26645-26645,udp,on,Skype UDP at 192.168.1.144:26645 (2927)
forward_port23=26645-26645>192.168.1.144:26645-26645,tcp,on,Skype TCP at 192.168.1.144:26645 (2927)
forward_port24=55629-55629>192.168.1.212:55629-55629,udp,on,Teredo
forward_port25=26645-26645>192.168.1.144:26645-26645,udp,on,Skype UDP at 192.168.1.144:26645 (2931)
forward_port0=14660-14660>192.168.1.113:14659-14659,udp,on,Skype UDP at 192.168.1.113:14659 (2898)
forward_port26=26645-26645>192.168.1.144:26645-26645,tcp,on,Skype TCP at 192.168.1.144:26645 (2931)
forward_port1=14659-14659>192.168.1.113:14659-14659,udp,on,Skype UDP at 192.168.1.113:14659 (2898)
forward_port27=3722-3722>192.168.1.210:3722-3722,udp,on,Skype UDP at 192.168.1.210:3722 (2931)
forward_port2=14659-14659>192.168.1.113:14659-14659,tcp,on,Skype TCP at 192.168.1.113:14659 (2898)
forward_port28=3722-3722>192.168.1.210:3722-3722,tcp,on,Skype TCP at 192.168.1.210:3722 (2931)
forward_port3=49556-49556>192.168.1.210:49556-49556,udp,on,Teredo
forward_port4=3722-3722>192.168.1.210:3722-3722,udp,on,Skype UDP at 192.168.1.210:3722 (2901)
forward_port29=3722-3722>192.168.1.210:3722-3722,udp,on,Skype UDP at 192.168.1.210:3722 (2932)
forward_port5=3722-3722>192.168.1.210:3722-3722,tcp,on,Skype TCP at 192.168.1.210:3722 (2901)
forward_port6=26645-26645>192.168.1.144:26645-26645,udp,on,Skype UDP at 192.168.1.144:26645 (2901)
forward_port7=26645-26645>192.168.1.144:26645-26645,tcp,on,Skype TCP at 192.168.1.144:26645 (2901)
forward_port8=26645-26645>192.168.1.144:26645-26645,udp,on,Skype UDP at 192.168.1.144:26645 (2903)
forward_port9=26645-26645>192.168.1.144:26645-26645,tcp,on,Skype TCP at 192.168.1.144:26645 (2903)
ping_ip=nvram show | grep forward_port
forward_port30=3722-3722>192.168.1.210:3722-3722,tcp,on,Skype TCP at 192.168.1.210:3722 (2932)
forward_port31=50182-50182>192.168.1.212:50182-50182,udp,on,Teredo
forward_port32=54464-54464>192.168.1.212:54464-54464,udp,on,Teredo
forward_port33=58540-58540>192.168.1.212:58540-58540,udp,on,Teredo
forward_port34=58076-58076>192.168.1.212:58076-58076,udp,on,Teredo
forward_port35=25611-25611>192.168.1.113:25611-25611,udp,on,Skype UDP at 192.168.1.113:25611 (2933)
forward_port36=25611-25611>192.168.1.113:25611-25611,tcp,on,Skype TCP at 192.168.1.113:25611 (2933)
forward_port37=25611-25611>192.168.1.113:25611-25611,udp,on,Skype UDP at 192.168.1.113:25611 (2936)
forward_port38=25611-25611>192.168.1.113:25611-25611,tcp,on,Skype TCP at 192.168.1.113:25611 (2936)
forward_port39=3722-3722>192.168.1.210:3722-3722,udp,on,Skype UDP at 192.168.1.210:3722 (2936)
forward_port40=3722-3722>192.168.1.210:3722-3722,tcp,on,Skype TCP at 192.168.1.210:3722 (2936)
forward_port41=3722-3722>192.168.1.210:3722-3722,udp,on,Skype UDP at 192.168.1.210:3722 (2941)
forward_port42=3722-3722>192.168.1.210:3722-3722,tcp,on,Skype TCP at 192.168.1.210:3722 (2941)
forward_port43=52559-52559>192.168.1.212:52559-52559,udp,on,Teredo
forward_port44=3722-3722>192.168.1.210:3722-3722,udp,on,Skype UDP at 192.168.1.210:3722 (2944)size: 32768 bytes (0 left)
forward_port45=3722-3722>192.168.1.210:3722-3722,tcp,on,Skype TCP at 192.168.1.210:3722 (2944)
forward_port46=48528-48528>192.168.1.115:48528-48528,udp,on,Skype UDP at 192.168.1.115:48528 (2945)
forward_port47=48528-48528>192.168.1.115:48528-48528,tcp,on,Skype TCP at 192.168.1.115:48528 (2945)
forward_port48=26645-26645>192.168.1.144:26645-26645,udp,on,Skype UDP at 192.168.1.144:26645 (2945)
forward_port49=26645-26645>192.168.1.144:26645-26645,tcp,on,Skype TCP at 192.168.1.144:26645 (2945)
forward_port=
forward_port50=25611-25611>192.168.1.113:25611-25611,udp,on,Skype UDP at 192.168.1.113:25611 (2945)
forward_port51=25611-25611>192.168.1.113:25611-25611,tcp,on,Skype TCP at 192.168.1.113:25611 (2945)

It does really look like an nvram problem, no? It says -9 left above. So should I just disable wan traffic counter and do clean port forwards at startup?

What does the wan traffic counter do anyway?
Back to top View user's profile Send private message
kevindd992002
DD-WRT User


Joined: 27 Feb 2009
Posts: 457
PostPosted: Mon Mar 23, 2015 9:41    Post subject: Reply with quote
It happened again just now after I turned on the router from a powered off state for 2 days. I tried checking the nvram size and here's what I got:

size: 29131 bytes (3637 left)
ping_ip=nvram show | grep size
olsrd_pollsize=0.1

So there's a lot left in nvram because I already turned off traff and enabled "clear port forward at startup".

The only difference now is that I detect both radios but when I connect to them, it is failing. Wired connections are always fine. Restarting the router fixes the problem.

Can anyone please help me here? LOM?
Back to top View user's profile Send private message
kevindd992002
DD-WRT User


Joined: 27 Feb 2009
Posts: 457
PostPosted: Wed May 20, 2015 23:54    Post subject: Reply with quote
BUMP!
Back to top View user's profile Send private message
EWiZaRD
DD-WRT Novice


Joined: 22 Dec 2013
Posts: 6
PostPosted: Sun May 24, 2015 17:10    Post subject: Reply with quote
I cleared (via nvram unset) all uninitialized(empty) nvram variables on WRT610Nv1. Don't know is it safe though. This saved ~5kb on nvram.
Back to top View user's profile Send private message
Goto page Previous  1, 2, 3, 4  Next Display posts from previous:    Page 2 of 4
Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum