I recently came across Toastman's post on saving a router's configuration from a CLI terminal. I would ideally like to use this to create a script containing all of the user-generated settings, with the goal of being able to swap hardware around with ease. Browsing through the list of NVRAM variables though, several issues present themselves. Settings related to clockspeed, interrupts, etc. should obviously not be included in case the new hardware isn't identical. Additionally, it occurs to me that one GUI entry may assign multiple values, not just the one with the same name. Toastman included a short list of variable groups that might be desirable to duplicate, but this is did not cover the many unique applications that each build now has - many of which have NVRAM variables even though they are disabled. I hypothesise that the best way to get only the needed variables (without plugging them into a spreadsheet and manually googling the unknown ones, which I have already started doing) would be a procedure like this: Flash intended Tomato build Reset NVRAM Export variables, giving a default baseline for the hardware in question Manually apply desired settings and reboot Export variables a second time Use a diff program to select changed lines and trim out everything else. Will this give me the results I'm looking for? Additionally, if I want to go deeper and catalogue what each control (or group of controls) in a setting page alters so that I can easily mix and match, how can I use the remote logging to capture the NVRAM changes?