I think I know what the problem is:
when you have a clean router, no configuration, when you run nvram show some items like static_leases , rc_firewall etc will not show.
I believe when you are restoring the configuration, you check it is exists in the nvram show, if not you do not restore, am I correct? _________________ Linksys MX8500
alternating with MX4300
Thanks for diagnosing. You must have saved the backup in migration mode. It's possible to edit the already generated restore script and change line 18:
Code:
op="-clean"
to
Code:
op=$1
and it shouldn't use clean mode (migration mode automatically turns on clean restore).
You could also rerun nvram-save.sh without -m if the original router is still available.
The nvram save/restore scripts were copied/tweaked (mentioned in the OP) for easyddup to create restore points and also save basic settings. I only wrote easyddup and checknewversion, not nvram save/restore.
PS.
I probably should add a big warning if -m is used on nvram-save as it breaks some dd-wrt features when restored as discussed on page 9 of this thread.
Thanks for diagnosing. You must have saved the backup in migration mode. It's possible to edit the already generated restore script and change line 18:
Code:
op="-clean"
to
Code:
op=$1
and it shouldn't use clean mode (migration mode automatically turns on clean restore).
You could also rerun nvram-save.sh without -m if the original router is still available.
The nvram save/restore scripts were copied/tweaked (mentioned in the OP) for easyddup to create restore points and also save basic settings. I only wrote easyddup and checknewversion, not nvram save/restore.
PS.
I probably should add a big warning if -m is used on nvram-save as it breaks some dd-wrt features when restored as discussed on page 9 of this thread.
makes sense, I will try in soon and update.
Also running nvram-restore-latest.sh without any input parameter? _________________ Linksys MX8500
alternating with MX4300
This worked now, although some other parameters didn't transfer like, DDNS and all wifi configurations etc.
When I'll have more time I will dig inside and see what do I need to change in order to customize my setup.
Thanks you for your help. _________________ Linksys MX8500
alternating with MX4300
Glad it's running. It's likely some variables in nvram-dd-wrt.ini.sample need to be added/modified if some settings are not being saved/restored. If we make useful changes I'll include them in the next release. People could save so much time getting their settings back after a reset or with a new router if nvram-dd-wrt.ini files were augmented and shared.
Posted: Mon Sep 15, 2025 16:54 Post subject: Did not work on v3.0-r60137 std (03/08/25)
Hi Just wanted to report back that I tried easyddup and did not see that my settings transferred. Its possible some did but my wifi settings did not and that is really noticeable.
Is this not working for newer builds or is there another reason it wont restore settings? I'd love this to work as manual setup is so painful and obviously web interface restore is problematic.
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 28.5M 100 28.5M 0 0 455k 0 0:01:04 0:01:04 --:--:-- 464k
Downloaded file OK.
WARNING THIS COULD BRICK YOUR ROUTER!!!
File to burn: ./fwcache/03-08-2025-r60137/asus-rt-ac5300/asus_rt-ac5300-firmware.trx
Are you sure? Type YES to burn SAME firmware: YES
Erase nvram y/n ? y
Save & Restore basic settings y/n ? y
Saving basic settings...
Save user settings restore point y/n ? y
Saving user settings restore point...
Burning ./fwcache/03-08-2025-r60137/asus-rt-ac5300/asus_rt-ac5300-firmware.trx
WARNING: DO NOT INTERRUPT...
WAIT FOR BURN TO COMPLETE (at least 5 minutes)
Done burning
Erasing nvram...
Restoring basic settings...
Rebooting...
So I ran this again and that restore never happened. I ended up with just a regular reset of the settings. So I setup the router again and I guess I'm confused about what exactly each part of this script does. I think I got it but if you dont mind clearing up a few things.
1. Does the easyddup.sh just do the update and later you need to do basic setup and restore the settings via ./nvram-restore.sh? Or does running easyddup.sh do it all in 1 go? OR is a reboot needed & then the restore is made?
2. I first tried with the quickstart guide and it does not mention easyddup. However when I ran nvram-save/restore it did not restore anything after saving. So again I must have missed something.
3. There is 1 thing that might be causing my issue but none of the scripts throw an error so Im really not sure. In the quickstart it mentions making the USB named ASUS, I have mine name 32gb and I tried to mount it as such but I just used sda1, which is default and should work anyway. So when I ran the script it does drop the saved settings in the backup directory. However when I go to restore as I said nothing seems to restore. I dont believe not using ASUS on my USB drive name matters, but it might.
4. If I just want to save my settings on current firmware, reset and then simply restore the exact same settings can I use easyddup? Or do I need to use nvram-restore/save?
Comment I kinda wish your script just pulled all the setting from the bin file that DDWRT already uses, & restore that in the alternative manner. Is that possible? I understand the advantages of this script, but that might be simpler.
Other info background. My router the AC5300 has an issue where it looses its 2.4ghz channel and when I do an update that bug will re-appear after usually a week but sometimes a month. There is 1 restore file I have that always brings it back but of course as the versions change its not good to keep using an old restore file, as you know this causes a lot of issues. So I had to restore manually but this bug still appears regardless so I'm looking for a good way to use your app to restore quickly when the bug appears. Ive looked into rebooting the radios but the commands dont restore the radio to its previous state, they are simply ignored if the radio is in crashed state.
