Posted: Fri Nov 04, 2011 15:52 Post subject: what does nvram show -> size: 32786 bytes (-18 left) mean
I am using Linksys WRT610N V1..
Currently DD-WRT v24-sp2 (12/24/10) mega - build 15962
I recently changed firmware and use the backup scripts
to reload my DHCP static and port forwards etc.
I notice the message in the subject.
What does (-18 left) mean ? Does this mean I am over
the available space ? If so, any way to get more with
a different firmware ? I know I will probably
want to add some more to the configuration in the
future.
I have maybe 20+ static DHCP entries, 15 port forwards rules, plus just basic wireless and wan.
yes, your nvram is more than full. you might loose some data.
a newer firmware build will not remedy this. you either have to load a firmware with fewer features, or disable features in your current firmware. do a 30-30-30 reset first, otherwise the nvram will not shrink.
or you have to buy a router with a larger nvram, like the linksys E4200 ( 60KB ) _________________ now running tomato by shibby
E4200v1 cfe 2010.09.20.0
Thanks. What I meant was if I used a non mega / big
build would I have more nvram space?
Whoops, worry, I misread the previous statement.
Ignore this question.
I have almost everything turned off.. all i need
is wireless, dhcp, basic port forwarding.
I don't even have the USB flash mounted any more.
Again, thanks for the input.. might be time to research the E4200.
Am I crazy, this seems like a major issue for everyone at some point ??
I am sure this will help.. I noticed when I was restoring the traf data being there but was
obviously too tired to remember and make that
association since then.
Of course that last rebuild/firmware upgrade didn't seem to
help as I restored all data including the traff.
So, if I read this correct I can dump the traff and
buy me some more time, at least working router again.
There are many, many DD-WRT users that don't do traffic stuff.
I don't and I don't care. I have other means to know what is going on and many uses, maybe should care, but don't know to care.
I understand why you want this information but your comment "Am I crazy, this seems like a major issue for everyone at some point ??" does not hold true for lots of users.
Last edited by nuke12 on Fri Nov 04, 2011 19:35; edited 1 time in total
I imagine there is more interest than ever in traffic data, with the craze Internet providers are having on capping these days for landlines as well as cellular.
Caps are now hitting 56% of the US landline market
Nothing personal, but I say "so what"? Most of us here, do not live in the USA. I have no data caps and my traffic monitoring has nothing to do with data caps.
As I stated in my earlier post. I do understand people wanting this information but many, many people don't need it, care about it, or some don't even know, about it.
Yes, it is an issue but I'm sure there are many greater problems to be found.
I was advised that using a smaller build (other than mega) will not give me more NVRAM space (in my case, for traffic data)
I remember that.. I may have not explained it properly.
nvram is a specific partition on the flash chip. It does not change in size. It is 32k excluding some of the newer routers that are 60k (one router that I know of is 64k).
A smaller build does not change the nvram size.
The part I may not have explained properly is that a smaller build with features not present in a larger build will not have the variables written to nvram for those features that do not exist. So you will pick up some "free" space in nvram but the total nvram space will still be 32k.
wrt54g V8 (neutered router) has 2mb flash, 32k nvram
RT-16 has 32mb flash, but still only 32k nvram
If a feature exists on a build, all the nvram variables are written to flash even though that feature may not be enabled. However, if enabled the variable may grow.
For instance.. you may have a dhcp connection type but the pppoe variables are still written in nvram
pppoe_username= (15 bytes)
but if you do use pppoe
pppoe_username="howdydoody" (25 bytes)
summary: running a smaller build will yield more "free" nvram space out of the 32k due to variables not being written to nvram by features that do not exist in the build. But... all variables for existing features whether used or not will be written to nvram (and will grow when used). _________________ [Moderator Deleted]
Last edited by barryware on Sat Nov 05, 2011 3:29; edited 1 time in total
Joined: 24 Feb 2009 Posts: 2026 Location: Sol System > Earth > USA > Arkansas
Posted: Fri Nov 04, 2011 21:48 Post subject:
jackster wrote:
Sorry, I thought it was on by default?? Hence my comment about it being a big problem
for most people may indeed be missinformed.
None the less, in my time using DD-WRT I thought
I would have read/heard about this before now.
You have heard about it, but not in its current form. Most people complain about their router suddenly "losing" all of its settings, or even some that may have 'spontaneously bricked'.
Yes there are some people who use traffic data. However, those that do not (and actually delete the extraneous data) have fewer problems as their nvram does not fill up. Those that do not use the traffic data and do not delete the extra, may not have any problems but then they are likely not using all of the features of DD-WRT anyway.
The people who tend to report the most problems are those that are trying to use many if not all of the features of DD-WRT. I myself almost experienced a loss in settings when my nvram space went to less than 300 bytes. Cleared the traffic data and I have over 2k bytes available. _________________ E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]
Try Dropbox for syncing files - get 2.5gb online for free by signing up.
Read! Peacock thread
*PLEASE* upgrade PAST v24SP1 or no support.
That's the irony! you read about hardware that stops working after a while a lot !
I just haven't seen a lot of responses, check your
nvram and make sure it's not toast from traff data !
Maybe I just missed a few.
Lucky for me today I may have the ability to fix
my situation instead of suffering like so many.
Just installed build 17806 mega. Used my backup scripts,
and removed the traff. It still went over.
I cleared the NVRAM and basically restored everything
by hand except for DHCP and port forward assignments.
Only leaving me 480 left.
That is with traff off and only one radio. I think
if I tried the second radio it would tip back over.
Never thought I would have a problem with the 610, but
I didn't know about the fixed nvram. Time to look
at the new models. I could try different firmware
with less variables but doubt it would be significant.
p.s. Knock on wood, router seems to be working great again.
this is exactly why i retired my wrt610nv1. newer dd-wrt builds simply have to many variables to fit in that 32KB. a v2 can be upgraded to an e3000 by flashing an e3000 cfe, but with a v1 you're stuck.
at the moment i'm testing vpnkong - build 17670:17737M with usb storage mounted, running a ftp server, openvpn, traffic daemon and mypage. i've currently 28041 bytes nvram left.... _________________ now running tomato by shibby
E4200v1 cfe 2010.09.20.0
thanks, wish I had a V2 at this point.
I will settle just for a reliable working router
today while I do some research on the next model.
Is a 610V2 better 3000,4000, and all the others?
It's crazy weird how it is so close to the 32K
limit. You either have way too little or
more then enough.
It seems 2K would probably be all the more I
would need.
