You most likely don`t need five OpenVPN clients, so I would suggest clearing all the vpn_client5_* settings completely (unset them).
That's a very good point, in particular for lower-powered routers such as the RT-AC68U.
Given your above suggestion, I went ahead and modified my script to include 3 of the OpenVPN clients for possible removal. When the script is run without arguments, it will also list all 3 sets of NVRAM variables that are found on the router *without* making any changes.
If you decide to remove one or more of the OpenVPN clients, type the following command as before:
Bash:
./CleanupNVRAMvars.sh -unset
The script will prompt you for confirmation before completely removing (i.e. nvram
unset *) each set of OpenVPN client NVRAM vars. To avoid, or at least minimize, accidental confirmations the only accepted character that confirms removal is the upper-case letter
Y. This way, you need a 2-key combination to really go ahead with the removal steps.
I've just run the modified script on an RT-AC68U router and found that one set of OpenVPN Client settings consists of
33 NVRAM variables and was taking
774 bytes of storage (this was for a never configured/used client). That's
165 NVRAM variables for a total of
3,870 bytes when you add up all
5 OpenVPN clients.
After talking with my relative (who owns the RT-AC68U router) and discussing the pros & cons, it was decided to remove only 3 of the OpenVPN clients. The router has now gained
2,336 bytes. That's fairly significant for a router that was already starving for NVRAM space.
I've already updated my previous post
#30 with the newly-modified version of the script in case anyone is interested or wants to try it out.
My 2 cents.