So actually, the error you pointed out with the < field separator occurred when I clicked on the DHCP Server tab. The Learn More link is this:This may be interesting.....the '<' is a field separator for the staticlist.....but it didn't say where????? What does the Learn More link say?
@RMerlin - FYI
Only other thing I can think of to capture is the jffs permissions...
ll /jffs | grep nvram
ll /jffs/nvram
After that...starting over sounds like a good idea.
Also, should I start over differently than usual to ensure this gets wiped out? I was just going to Restore Factory Defaults in the Administration tab.Only other thing I can think of to capture is the jffs permissions...
ll /jffs | grep nvram
ll /jffs/nvram
After that...starting over sounds like a good idea.
In addition to doing the restore factory defaults, I might do a Reformat JFFS at next boot after the reseet completes. I did a quick look at the code, and didn't immediately see where it reset the nvram directoryAlso, should I start over differently than usual to ensure this gets wiped out? I was just going to Restore Factory Defaults in the Administration tab.
Nothing that I know of, but I haven't kept track of all the changes in this area.Would going to Merlin change anything in this scenario (I know your fork won't work b/c of newer code base)?
Reformat JFFS at next boot: is that in Merlin only? If I stay on ASUS stock, how is that accomplished?In addition to doing the restore factory defaults, I might do a Reformat JFFS at next boot after the reseet completes. I did a quick look at the code, and didn't immediately see where it reset the nvram directory
Nothing that I know of, but I haven't kept track of all the changes in this area.
Oh...I didn't think that was Merlin unique.....Reformat JFFS at next boot: is that in Merlin only? If I stay on ASUS stock, how is that accomplished?
admin@RT-AC86U:/tmp/home/root# nvram get jffs2_formatOh...I didn't think that was Merlin unique.....
check to see if the following returns a value
nvram get jffs2_format
Thanks for all of your help. I've performed a factory reset (along with a firmware update that released today for Asus stock). I did another factory reset after the firmware update completed just to be sure. I've entired a manual assignment and rebooted. So far, so good. I went back and looked at the jffs permissions and they were the same as before. I also watched the browser console and saw the same errors as were discussed previously. I'll post if something changes. Thanks again everyone.Then I guess it's just a factory reset....good luck!
Thanks for the taking the time to go back and double check those items. At least we now know they were not playing a role (although the mystery remains).I went back and looked at the jffs permissions and they were the same as before. I also watched the browser console and saw the same errors as were discussed previously.
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!