Reminder to self: [WayBack] Tomato by shibby – upgrade procedure and cfg backup | LinksysInfo.org:
I keep a text file with the changes I’ve made after a fresh install and I keep the file updated as I make changes.
Re-configuring the router after that takes a bit of time, but it is not that bad. Toastman’s method (here) noted above as well as the methods described here and here can also be used, but I haven’t tried them.
which references:
- [WayBack] Using QOS – Tutorial and discussion | Page 3 | LinksysInfo.org
You need to save a file somewhere on or off the router, with the following command from the command line.nvram export –set >config.txt
This outputs the complete setup in useable text form, each line beginning with “nvram set”. This means it’s ready to input to the router without having to add the “nvram set” to every line. You could do this by ssh or telnet.
NOTE – you can only restore the whole config file to the original router. To configure a different router you need to cherry pick the important lines (see below)
e.g.
nvram set clkfreq=480,240,120
nvram set wl0_country=AU
nvram set wan_domain=freewifi
nvram commit - [WayBack] Tomato RAF Releases | Page 18 | LinksysInfo.org
save off the results of nvram export –quote, ie:
Code:
nvram export –quote > nvram_clean
after erasing, then subsequent changes are easy to find later with:
Code:
nvram export –quote | grep -Fvf nvram_clean
While not quite as readable or cut and paste friedly as –set, –quote is script friendly with the advantage that all entries are always a single line. - [WayBack] I’ve created a command-line NVRAM cfg file parser | LinksysInfo.org
Decodes Tomato cfg files into JSON so they can be changed and compared against other backups. Encodes JSON-formatted Tomato cfg key/value pairs into the Tomato cfg format.
–jeroen
