Try it again from a different PC/browser.
post the output ofThanks for your help so far. After I run the nvram set and commit, it appears that those 4 entries are still set in the dhcp_staticlist parameter.
I obfuscated portion of MAC, but here:post the output of
nvram show | grep staticlist
And those are the 4 entries you say you can't delete? Try this sequence....I obfuscated portion of MAC, but here:
dhcp_staticlist=<C4:54:44:5C:XX:XX>192.168.2.163<00:90:A9:B9:XX:XX>192.168.2.183<10:1F:74:FE:XX:XX>192.168.2.200<B8:27:EB:0C:XX:XX>192.168.2.201
size: 54347 bytes (76725 left)
And those are the 4 entries you say you can't delete? Try this sequence....
close the gui and ssh to router
nvram unset dhcp_staticlist
nvram commit
nvram show | grep staticlist (should be empty response)
service reboot
after the router reboots (give it a few minutes), ssh to router
nvram show | grep staticlist
should show 'dhcp_staticlist='
open the router gui and try to enter a new static entry, hit apply
back in ssh session
nvram show | grep staticlist
should show the new entry....if the old entries are back, you must have a browser extension that is autofilling the form behind the scenes.
Wow....that's really strange. I'm starting to suspect you may have a hardware problem writing to nvram. I've never seen 'unset' not work before.
Let's try and create/delete a new variable....
nvram set test_nvram="xxxxxxxxxxxxxxx"
nvram commit
nvram show | grep test_nvram
nvram unset test_nvram
nvram show | grep test_nvram
@giant25
Last try....let's try and rewrite staticlist with a value from the command line
nvram set dhcp_staticlist="<FF:FF:FF:FF:FF:FF>192.168.2.200"
nvram commit
nvram show | grep staticlist
nvram unset dhcp_staticlist
nvram show | grep staticlist
That cleared it:Code:rm /jffs/nvram/dhcp_staticlist
So now what? Should I try to make assignments in the GUI and see if they survive a reboot? I really appreciate both of you guys. I've run Merlin and John's fork on a few RT-n66u's over the years. Maybe it's time for my 86u to get off stock as well....That cleared it:
admin@RT-AC86U:/tmp/home/root# rm /jffs/nvram/dhcp_staticlist
admin@RT-AC86U:/tmp/home/root# nvram show | grep staticlist
size: 54202 bytes (76870 left)
admin@RT-AC86U:/tmp/home/root#
Yes, try that.So now what? Should I try to make assignments in the GUI and see if they survive a reboot?
So the nvram command doesn't operate on variables that have been moved to jffs?Code:rm /jffs/nvram/dhcp_staticlist
So the nvram command doesn't operate on variables that have been moved to jffs?
Anyone have an 86u that can test this??? Seems weird if I'm the only one....It should, at least it used to do so in the past... <shrug>.
Nvram is all closed-source now, so Asus will have to sort this out on their own.
Pinging @arthurlien .
One last thing to check if you would....turn on the browser console (F12), then add an assignment and hit apply. Are there any errors posted in the console?btw, I just tried to add an assignment via GUI and then reboot. No dice, table was empty.
One last thing to check if you would....turn on the browser console (F12), then add an assignment and hit apply. Are there any errors posted in the console?
Thread starter | Title | Forum | Replies | Date |
---|---|---|---|---|
D | Manually Assigned IP Address Not Respected for Repeater | ASUSWRT - Official | 2 | |
L | Security update support list for the US market | ASUSWRT - Official | 6 |
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!