User NVRAM Save/Restore Utility

LATEST RELEASE: Release 24a

12-February-2017
nvram-save-r24a.zip
Download [url]http://bit.ly/1SDz2Hb[/url]
===============================

Version 24a 12-February-2017

This is an INI file only update (hence just the suffix change to 24a)
INI file Changes

sync with 380.65 Merlin and V23 LTS fork

add support for Merlin firmware update

add support for new ipv6 options

add support for OpenVPN 2.4

add support for DNSCrypt (LTS fork)

add support MU-MIMO options

add support for Bluetooth compatibility

add support for Facebook WIFI (ASUS OEM only)

misc updates to wan and wifi variables

Full Changelog history is available in the download directory

Some quick usage notes:

Although new options/suggested improvements have been added to give greater

control during execution, the default operation of the utility has not been changed. If
you have used the utility in the past, you can continue to use it just like before.

A help command has been added to the utility, nvram-save.sh -h

Code:

NVRAM User Save/Restore Utility

nvram-save.sh Version 24
Options: -h this help msg
-v Print version/perform consistency check
-b Backup mode - save for restore to same router (default)
-m Migration mode - transfer settings to another router
-i inifile Specify custom nvram variable ini file
-clk Include clkfreq/overclock setting (Backup mode only)
-nojffs Skip backup of jffs storage
 -nouser Skip execution of user exit script

When running the utility or using the print version option, nvram-save.sh, nvram-
restore.sh, jffs-restore.sh, nvram-merlin.ini and nvram-excp-merlin.sh are consistency
checked to make sure they are all the same version. A WARNING message will be
printed on a version mismatch, but execution will continue if actually running to
generate the restore script.

You can now specify a custom nvram variable 'ini' file to use to generate the restore
script. A sample ini,
nvram-sample.ini, is included which is a stripped down version of the full ini
containing only basic entries that people
have mentioned in various threads.

The generated restore scripts now take a single option, '-clean'

This option will prevent the restore of unnecessary variables (variables removed,
options no longer present if backleveling firmware) by only restoring those user
variables which are initialized by a reset to factory defaults. The terminal window will
list those variables which were not restored when you execute the restore. Restoring
all the variables should not cause any problems except for wasted NVRAM space.

nvram-restore.sh and jffs-restore.sh will now prompt you to load the last saved
backups and to run a 'clean' restore if run without any input parameters
NOTE: You can still run the individual nvram-restore-yyyymmddhhmm-macid.sh
scripts to perform a restore as in previous releases. (The full timestamp including
hhmm was added in Release 24)

The backup files may now be placed in a 'backup' subdirectory. Just 'mkdir
/mnt/ASUS/backup' and the files will be placed there instead of in the main working
directory.

The default state is NOT to save clkfreq overclocking values (safest when moving to a
new code level). If you wish to
include this setting, specify the -clk option on the nvram-save.sh command.

The nvram-merlin.ini files contains a section at the end for custom User Adds. You
may edit this section to add any NVRAM variables you may have created for use in
scripts, or to temporarily add any variables which may be missing.

The nvram-save utility also creates two text files during execution that can be viewed
or archived.

o nvram-all-yyyymmddhhmm-macid.txt (all nvram variables, including system

variables not normally changed by the user)

o nvram-usr-yyyymmddhhmm-macid.txt (the nvram variables actually saved by

the utility in their save categories)

As a reminder, the restore process will make the following changes if moving from a
376 or earlier code to 378 or later Merlin releases
 o Exception process will attempt to create the proper format for the MAC Filter
lists depending on the firmware level. If a problem occurs, run the included
clear-maclist.sh script to reset the filters.

o If jffs is not active, it will be set to be activated and formatted, jffs scripting
will be disabled

o If jffs is active, jffs scripting will also be activated

o If you are using a VPN server, the settings will be migrated to the new nvram
variable

o Adjust the QOS type to maintain the traditional QOS settings if moving from a
Non-Adaptive QOS firmware to one supporting Adaptive QOS.

The utility is still valid for ASUS OEM as well as Merlin releases, although it will not
attempt to fix changes in the use of nvram variables between releases (just too many
ASUS levels with various release numbers to track).

-----------------------------------------------------------------
SHA256 hash:

Code:
b2e370f5a5f81b0ec2053c6ea97b867b29fd18e73800a85b4cca1109197c4a43
*nvram-save-r24.zip

Thanks again to everyone for their feedback and suggestions. Enjoy!