Thank you for the links, that was the context I was missing (and why it didn't come up in my search). I thought it was being suggested that a factory reset was needed if you were changing your SSID!
Sorry I meant him as @breathless, not you...I have no issues. And again Merlin has said nothing about a factory reset being needed. And certainly changing SSID's is NO valid reason to factory reset that's simply false.
Noooooo!Thank you for the link, that was the context I was missing. I thought it was being suggested that a factory reset was needed if you were changing your SSID!
Good for you, if you encountered no issue or have forgot/reconnected on client first (basically same/similar effect).I'm using the same SSIDs at home for many years through few system upgrades and in few locations. My business places also have the same SSIDs because I'm moving equipment from site to site often. I'm always using a new (never before used) power outlet though.
No ideas here, plain necessity; and as I said sometimes. You were lucky, that's all!If you come to my home or business with ideas to reset my equipment or change the SSIDs I'll show you the door right away.
Have been doing this for 25+ years
I have encountered it and solved it with this, RMerlin noticed it too, many others did also; soooo...Means little.
One of my first jobs, the eternally great Mr Ezell told me
"Practice does not make perfect. Perfect practise makes perfect."
No ideas here
You haven't read what I said carefully, my recommendation was to forget the Network on the Client (or new SSID if multiple clients have issues), and only at the end reset.Reboot, reset and/or reconfigure comes exactly from no ideas what is happening. Please, don't join that team. In very rare cases I needed to re-connect a client. It's a client issue and you don't need to do anything with the AP to fix it. I only recommend reset, reconfigure, use defaults and don't touch when the user has no enough knowledge to troubleshoot. Don't offer it as universal solution to every problem. It's often a waste of time solution.
I see, there's however no such option on the client side. Besides that there seems to be no way to transfer VPN config/settings, not just certificates.
It is not enough to just copy the "/jffs/openvpn" folder.
mkdir -m 755 -p /jffs/scripts
curl -kLSs --retry 3 --retry-delay 5 --retry-connrefused pastebin.com/raw/eUEtWtEc | tr -d '\r' > /jffs/scripts/SaveRestoreNVRAMvars.sh
chmod 755 /jffs/scripts/*.sh
./SaveRestoreNVRAMvars.sh
./SaveRestoreNVRAMvars.sh -menu
I am archiving this. Thanks for being around. This will definitely help me at some point!At the beginning of 2021, I wrote a small shell script for a relative of mine so he could more easily & quickly back up & restore a specific subset of NVRAM variables related to his OpenVPN Server configuration (separately from his backing up the contents of the "/jffs/openvpn" folder). This was done at a time when he was having some issues with the router & needed to reset to factory defaults frequently while troubleshooting the problem.
Later on, I made more changes to add NVRAM variables for his OpenVPN client configurations. Eventually, I rewrote the script to be able to back up & restore any subset of NVRAM vars using an input file that lists the specific NVRAM variable key names targeted for backup. I recently updated the script to add a user-friendly menu (based on the code I wrote for YazDHCP).
If you're interested in trying this script, you can download it from PasteBin (www.pastebin.com)
Here are the instructions:
1) Open an SSH terminal window & type the following commands:
NOTE: You can choose to save the script file in any other location that you prefer.Bash:mkdir -m 755 -p /jffs/scripts curl -kLSs --retry 3 --retry-delay 5 --retry-connrefused pastebin.com/raw/eUEtWtEc | tr -d '\r' > /jffs/scripts/SaveRestoreNVRAMvars.sh chmod 755 /jffs/scripts/*.sh
2) To run the shell script and get some brief help messages, simply go to the directory where it was saved and type:
Bash:./SaveRestoreNVRAMvars.sh
3) I recommend running the script first in "Menu Mode" to set your preferences for the backup directory & input file path.
Bash:./SaveRestoreNVRAMvars.sh -menu
4) Attached is an example of the required input file (NVRAM_VarList_SAMPLE.txt)
The input file must be saved in the same directory where the shell script is located.
Rename the file to "NVRAM_VarList.txt" & modify it as necessary for your own purposes.
HTH
I'll have a look at it, thank you!At the beginning of 2021, I wrote a small shell script for a relative of mine so he could more easily & quickly back up & restore a specific subset of NVRAM variables related to his OpenVPN Server configuration (separately from his backing up the contents of the "/jffs/openvpn" folder). This was done at a time when he was having some issues with the router & needed to reset to factory defaults frequently while troubleshooting the problem.
Later on, I made more changes to add NVRAM variables for his OpenVPN client configurations. Eventually, I rewrote the script to be able to back up & restore any subset of NVRAM vars using an input file that lists the specific NVRAM variable key names targeted for backup. I recently updated the script to add a user-friendly menu (based on the code I wrote for YazDHCP).
If you're interested in trying this script, you can download it from PasteBin (www.pastebin.com)
Here are the instructions:
1) Open an SSH terminal window & type the following commands:
NOTE: You can choose to save the script file in any other location that you prefer.Bash:mkdir -m 755 -p /jffs/scripts curl -kLSs --retry 3 --retry-delay 5 --retry-connrefused pastebin.com/raw/eUEtWtEc | tr -d '\r' > /jffs/scripts/SaveRestoreNVRAMvars.sh chmod 755 /jffs/scripts/*.sh
2) To run the shell script and get some brief help messages, simply go to the directory where it was saved and type:
Bash:./SaveRestoreNVRAMvars.sh
3) I recommend running the script first in "Menu Mode" to set your preferences for the backup directory & input file path.
Bash:./SaveRestoreNVRAMvars.sh -menu
4) Attached is an example of the required input file (NVRAM_VarList_SAMPLE.txt)
The input file must be saved in the same directory where the shell script is located.
Rename the file to "NVRAM_VarList.txt" & modify it as necessary for your own purposes.
HTH
what is the output, when you typeI'll have a look at it, thank you!
Getting this error:
kees@GT-AX6000:/jffs/scripts# ./SaveRestoreNVRAMvars.sh -menu
**ERROR**: Backup directory [/opt/var/NVRAM_VarsBackup] NOT FOUND.
ls -la /opt/var
into the SSH command-line?Is that all the output you're getting?I'll have a look at it, thank you!
Getting this error:
kees@GT-AX6000:/jffs/scripts# ./SaveRestoreNVRAMvars.sh -menu
**ERROR**: Backup directory [/opt/var/NVRAM_VarsBackup] NOT FOUND.
ASUSWRT-Merlin GT-AX6000 3004.388.4_0 Mon Aug 21 19:34:19 UTC 2023what is the output, when you typels -la /opt/var
into the SSH command-line?
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!