latenitetech
Regular Contributor
First things first ...
We must be talking past each other on the scripts and the awk commands I'm referring to. The "generated script" in my case is named "nvram-restore-202004271709_RT-AC68U-MIGR.sh" (located in the backup directory of my nsru installation).
I had to insert a screenshot as the paranoid bbs wouldn't let me insert the actual code here.
Notice the 'awk' on lines 35, 39, 45, 49. The ones on all but line 45 have the issue with the escaped single-quote. Removing the backslashes from those 3 awk statements seems to fix the problem.
As for the other concerns of why as I'm doing such a crazy thing as trying to migrate between 2-yr old FW versions. A bit of background, I was crazy busy with work when the migration from 380 to 384 happened, and since my work is critically dependent on a working router environment, I just didn't have the time to risk any downtime if that migration went south. Fast forward several very busy years, I'm now even more concerned about downtime trying to get that old/reliable router upgraded, so I bought another identical model and will use it as my test bed before I commit it to production on the latest FW. Seeing there was a backup tool that purported to do migrations, I thought I'd give it a try. Worst case, I rebuild it from scratch (I have a lot of customizations).
We must be talking past each other on the scripts and the awk commands I'm referring to. The "generated script" in my case is named "nvram-restore-202004271709_RT-AC68U-MIGR.sh" (located in the backup directory of my nsru installation).
I had to insert a screenshot as the paranoid bbs wouldn't let me insert the actual code here.
Notice the 'awk' on lines 35, 39, 45, 49. The ones on all but line 45 have the issue with the escaped single-quote. Removing the backslashes from those 3 awk statements seems to fix the problem.
As for the other concerns of why as I'm doing such a crazy thing as trying to migrate between 2-yr old FW versions. A bit of background, I was crazy busy with work when the migration from 380 to 384 happened, and since my work is critically dependent on a working router environment, I just didn't have the time to risk any downtime if that migration went south. Fast forward several very busy years, I'm now even more concerned about downtime trying to get that old/reliable router upgraded, so I bought another identical model and will use it as my test bed before I commit it to production on the latest FW. Seeing there was a backup tool that purported to do migrations, I thought I'd give it a try. Worst case, I rebuild it from scratch (I have a lot of customizations).
Last edited: