Request: move custom_clientlist, dhcp_staticlist, and dhcp_hostnames from NVRAM to jffs

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

James Olsen

New Around Here
Is it possible to move custom_clientlist and dhcp_hostnames from NVRAM to jffs in a future enhancement to AsusWrt-Merlin?? I just upgraded my RT-AC68P to AsusWrt-Merlin 384.17 and I'm now getting the following message in the UI:

"Your router is running low on free NVRAM, which might affect its stability.
Review long parameter lists (like DHCP reservations), or consider doing a factory default reset and reconfiguring."

I'm not sure what has increased in the NVRAM usage with this upgrade, perhaps it was somewhat coincidental, but I haven't made any explicit configuration changes lately (my config is pretty old)

My top 10 items in NVRAM taking space are (bytes followed by item):
  1. 1400 custom_clientlist
  2. 1089 sshd_hostkey
  3. 991 sshd_authkeys
  4. 822 dhcp_staticlist
  5. 810 nc_setting_conf
  6. 628 sshd_dsskey
  7. 539 client_info_tmp
  8. 527 rc_support
  9. 357 MULTIFILTER_MAC
  10. 338 sshd_ecdsakey

Related question: what I can I do to free up NVRAM to keep my device functioning, short of deleting data in custom_clientlist, dhcp_staticlist or deleting ssh keys?

Three items that would be nice to move to JFFS storage and in-RAM access are: custom_clientlist, dhcp_staticlist, and dhcp_hostnames because being able to edit these in a text editor would be handy, in addition to freeing up that NVRAM storage.

It just seems like NVRAM in this unit is inadequate unless one doesn't really try to manage the devices on their network.

Is a change like possible, and what are the ramifications (no pun intended) of a change like this if it were to be made?

Thank you for your time
 

faria

Senior Member
Is it possible to move custom_clientlist and dhcp_hostnames from NVRAM to jffs in a future enhancement to AsusWrt-Merlin?? I just upgraded my RT-AC68P to AsusWrt-Merlin 384.17 and I'm now getting the following message in the UI:

"Your router is running low on free NVRAM, which might affect its stability.
Review long parameter lists (like DHCP reservations), or consider doing a factory default reset and reconfiguring."

I'm not sure what has increased in the NVRAM usage with this upgrade, perhaps it was somewhat coincidental, but I haven't made any explicit configuration changes lately (my config is pretty old)

My top 10 items in NVRAM taking space are (bytes followed by item):
  1. 1400 custom_clientlist
  2. 1089 sshd_hostkey
  3. 991 sshd_authkeys
  4. 822 dhcp_staticlist
  5. 810 nc_setting_conf
  6. 628 sshd_dsskey
  7. 539 client_info_tmp
  8. 527 rc_support
  9. 357 MULTIFILTER_MAC
  10. 338 sshd_ecdsakey

Related question: what I can I do to free up NVRAM to keep my device functioning, short of deleting data in custom_clientlist, dhcp_staticlist or deleting ssh keys?

Three items that would be nice to move to JFFS storage and in-RAM access are: custom_clientlist, dhcp_staticlist, and dhcp_hostnames because being able to edit these in a text editor would be handy, in addition to freeing up that NVRAM storage.

It just seems like NVRAM in this unit is inadequate unless one doesn't really try to manage the devices on their network.

Is a change like possible, and what are the ramifications (no pun intended) of a change like this if it were to be made?

Thank you for your time
pretty much all of that is already on jffs in /jffs/nvram/ at least on NG models.
you can move " dhcp_staticlist" to "/jffs/configs/dnsmasq.conf.add" to free some nvram, you can use the Script "dhcpstaticlist.sh" by # Original Author: Xentrk to achieve that.
 
Last edited:

David Cavalli

Regular Contributor
I was just about to type the dnsmasq.conf.add to pay back those who helped me with the exact same solution. Almost had the exact same post. Making this post to add the only other piece of information to add to the puzzle. I too had a very old configuration that suddenly had the "!" warning about low NVRAM. As an FYI, from what I was told, it's not that the new firmware suddenly used more NVRAM, but that the "!" warning threshhold was always there, but that message had only recently been activated in the last version or two fo firmware. The dnsmasq file changed everything for me and my router is streamlined and running great. :D
 

SomeWhereOverTheRainBow

Very Senior Member
I was just about to type the dnsmasq.conf.add to pay back those who helped me with the exact same solution. Almost had the exact same post. Making this post to add the only other piece of information to add to the puzzle. I too had a very old configuration that suddenly had the "!" warning about low NVRAM. As an FYI, from what I was told, it's not that the new firmware suddenly used more NVRAM, but that the "!" warning threshhold was always there, but that message had only recently been activated in the last version or two fo firmware. The dnsmasq file changed everything for me and my router is streamlined and running great. :D
yea every since I setup over a 100 static ips, I have moved all mine to dnsmasq.conf.add and haven't looked back.
 

James Olsen

New Around Here
Thank you, everyone for the great replies. I've been trying to educate myself on configuring dnsmasq manually through dnsmasq.conf.add and I had a few more questions I hope you will be willing to provide some guidance on.

For replicating static IP assignments and custom DHCP names (to make them human friendly and distinguishable from other devices of the same make/model on the network), are you only utilizing the "dhcp-host=xxx,yyy,zzz" directive? Or do you have other things in your dnsmasq.conf.add that are required to make it work with this new file? If I use dnsmasq.conf.add, do I leave to change anything in the UI configuration regarding the DHCP server (turn anything on and off) in order to use dnsmasq.conf.add? I'm hoping the dnsmasq.conf.add is supplemental to the DHCP configuration in the UI (such as IP pool range, default lease time, etc) and not a full replacement for all those configuration values. (I have enabled jffs scripts)

From what I understand from reading the dnsmasq docs, the IP address field is optional (so I can assign just a dhcp name without a static ip), and likewise the name field is optional if I only want to assign a static ip and leave the name as-is. Is this your interpretation as well?
Some (made-up) examples:
# both assign name and static ip
dhcp-host=00:11:22:33:44:55,Scott Phone,192.168.1.26,24h
# just assign name
dhcp-host=00:11:22:33:44:56,TV,24h
# just assign static ip
dhcp-host=00:11:22:33:44:57,192.168.1.27,24h

What lease time are you guys typically defining, or are you omitting that parameter and leaving that whatever the default lease time is?

Thanks again for the great tips. Looking forward to getting all this set up and working!

--James
 

RMerlin

Asuswrt-Merlin dev
I can't move Asus's nvram settings.
 

James Olsen

New Around Here
Thanks again everyone.

I was able to create the dnsmasq.conf.add and everything seems to be working as desired in that regard.
 

David Cavalli

Regular Contributor
From what I understand from reading the dnsmasq docs, the IP address field is optional (so I can assign just a dhcp name without a static ip), and likewise the name field is optional if I only want to assign a static ip and leave the name as-is. Is this your interpretation as well?
Some (made-up) examples:
Here are some specific lines in my config, editing out the exact MAC info:

###----- Kwikset devices (50 series)
dhcp-host=68:47:49:AA:AA:AA,KwiksetHaloFront,192.168.1.51,1440

###----- MyQ devices (50 series)
dhcp-host=64:52:99:AA:AA:AA,MyQGarageMain,192.168.1.53,1440
dhcp-host=64:52:99:AB:AA:AA,MyQGarageExtra,192.168.1.54,1440

###----- Honeywell devices (50 series)
dhcp-host=B8:2C:A0:AA:AA:AA,HoneywellHomeUpstairs,192.168.1.55,1440

###----- Arlo devices (60 series)
dhcp-host=A4:11:62:AA:AA:AA,ArloBaseUnit,,192.168.1.61,1440

###----- Ring devices (70 series)
dhcp-host=A4:D5:78:AA:AA:AA,RingChimeProUpstairs,192.168.1.75,1440
dhcp-host=40:BD:32:AB:AA:AA,RingChimeProDownstairs,192.168.1.76,1440
dhcp-host=3C:E1:A1:AC:AA:AA,RingVideoDoorbellPro,192.168.1.77,1440

Hope that helps. Glad to hear it worked for you too! :D
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top