QUOTE(FameWolf @ Jul 29 2016, 04:43 AM)
FYI the .trx file is stored in a subdir from the dir that has the start.sh script. startshdir/trx_archive/creationdatetime
I have found out it's dangerous to just use the .trx.
"The firmware file must be divided into several parts before flashing. It is dangerous to do it yourself."
If no one can confirm it's safe to share the settings between the mi and the mi-3 (backup and restore) I suppose I'll have to do them manually.
The following script (ran from the router) will create a file that contains the full config for the router in text file format with nvram set commands that can be edited so it is suitable to flash to a new router. The normal binary backup is very dangerous because it will try to assign hardware addresses and other things so you'd want to delete anything except the section you wanted such as the ip ranges, static ip addresses etc....
#!/bin/bash
nvram showall > nvram_settings.txt
rm nvram_settings.tmp
cat nvram_settings.txt | while read i;
do
o=${i%}
echo "nvram set " ${o} >> nvram_settings.tmp
done
sort nvram_settings.tmp > my_settings.txt
FrameWolf,I have found out it's dangerous to just use the .trx.
"The firmware file must be divided into several parts before flashing. It is dangerous to do it yourself."
If no one can confirm it's safe to share the settings between the mi and the mi-3 (backup and restore) I suppose I'll have to do them manually.
The following script (ran from the router) will create a file that contains the full config for the router in text file format with nvram set commands that can be edited so it is suitable to flash to a new router. The normal binary backup is very dangerous because it will try to assign hardware addresses and other things so you'd want to delete anything except the section you wanted such as the ip ranges, static ip addresses etc....
#!/bin/bash
nvram showall > nvram_settings.txt
rm nvram_settings.tmp
cat nvram_settings.txt | while read i;
do
o=${i%}
echo "nvram set " ${o} >> nvram_settings.tmp
done
sort nvram_settings.tmp > my_settings.txt
By any chance you have the old developer firmware?
It seems that the newer developer firmware is no longer SSH accessible
Aug 3 2016, 01:41 AM

Quote
0.0353sec
0.79
7 queries
GZIP Disabled