Posted: Tue Apr 07, 2020 17:19 Post subject: [Solved] Using "Admin > Backup" and pitfalls
MODS: This may not be Atheros specific, please let me know or move it to the appropriate place
Is it possible to make a complete backup of the config of R7800 and get it on another R7800? Will this catch all settings including startup scripts and such?
I've got one flashed with DD-WRT r42819 and another still stock from the factory. When I'm done setting up the first one, I'd like to mirror it's config to the second one, make a few tweaks manually (like IP address) then place them both in their final locations.
What's the best way to do this? I can see two general approaches:
1) Flash the 2nd one with .img for to get DD-WRT running first, then backup config from 1st and restore it on the 2nd. Will this get everrthing? I care most about VAPs, VLANs, and Bridge configs.
2) [i]Not sure this is possible[/], Kind of like imaging a hard drive with dd: Take a complete image of the 1st one, somehow flashing it on to 2nd one. Upgrading to DD-WRT and getting the settings all at once.
Last edited by krby on Tue Apr 07, 2020 18:12; edited 2 times in total
Ok, so recommended procedure is to:
1) Take backup on R7800-1 running r42819
2) Use img file for r42819 to do initial flash of R7800-2 from Netgear stock to DD-WRT
3) Restore backup from step 1 onto R7800-2
4) Reboot R7800-2, check settings, adjust the few things that I want to be different
Or...should I be using a different img file for the initial flash of R7800-2 and doing a .bin upgrade to r42819?
Last edited by krby on Tue Apr 07, 2020 18:13; edited 1 time in total
The backup file contains your scripts and all. It also contains *some* mac addresses that were probably originally derived from the router's native config. (For wifi 2.4 & 5 GHz and switch/LAN/WAN).
The question would be does restore from the 1st router's backup override the 2nd router's native mac addresses? I see that some GUI pages (e.g. Setup->Networking) seem to treat MACs as variables. It might be a good idea to capture the 2nd router's MAC addresses from a default config before restoring the new config over it, just in case. I assume you want both routers active where other equipment could see both at the same time, so you don't want them using the same MACs. _________________ dd-wrt on TP-Link Archer A7 v5
Joined: 21 Jan 2017 Posts: 1779 Location: Illinois Moderator
Posted: Wed Apr 08, 2020 12:47 Post subject:
My email to BS and his reply:
I saw the nvram editor tool and see that when you make a backup the mac addresses are saved. Given that, if someone has two identical routers, same build, and they save the nvram backup and load it onto the second router to save time on config, will that brick/spawn gremlins, or is that ok and the router will still load it's hard baked key details like MAC addresses?
depending on the router model variables which may brick devices will be ignored. this includes also mac addresses. so its all backed up, but not all will be restored
see the big filterlist here in this sourcecode https://svn.dd-wrt.com/browser/src/router/nvram/backup.c and the function "nvram_critical_internal"
I assume this is not advisable, but wanted to check.
you can do that without any issue. its just not advices to backup and restore between different device models. since they may have different interface names (eth0 vs vlan1 etc.)
and wan port assignments. so the resulting network configuration might be bad. but if the interface usage is identical you can also use the same backup on different models
you can do that without any issue...so the resulting network configuration might be bad. but if the interface usage is identical you can also use the same backup on different models
I interpret that to mean across the exact same model and revision on the same build of dd-wrt, restoring a config should not brick, but it might lead to an invalid network config out of the box depending what the exact router restores from the backup (MACs etc).
So, I'll take the advice of noting down MACs for the various interfaces, then restoring, and updating those if I need to.