The procedure using tnftp above works with the OEM MTD set using separate images, but takes much more work IMHO. And I am not sure a webgui upgrade of RT firmware is possible if MTD4 is not changed to span the FS and kernel. The tutorial I wrote up last march was done because RRT
does not do well when trying to flash these routers with separate images.
I have verified my single image process using RRT many times now with GT701wg. The MTDs for the 4 port GT704wg are a bit different and must be set per the RT docs for the the RT firmware being flashed. Search for my posts & tutorial to get the details.
Basically... After using RUC to backup the environment and config (mtd3), I setup the PC IP with RRT, boot into the bootloader upon power-up, set the MTDs with RRT, then flash single image with RRT then wait 5 MINUTES !. Reboot router, reset PC IP and login to 192.168.1.1. The config file s/be reset to defaults upon boot. After basic configuration I can also setup a BIG minix partition (in spite of warnings) using
then reboot, wait 5 minutes for mtd5 to get formatted, reboot again and the env is set to automount /nvram on mtd5. Script city now !
As for Openwrt, the flashing procedure (and MTDs) are much different (use ftp to set MTD5 and flash per openwrt website).
Do not load openwrt unless you NEED a wireless client (without wep, wpa or wds). And it will not be bridged either, it will act like a wireless router in reverse but the wireless MAC may become generic. And kamikaze will fill up the flash with inactive files so beware. And much traffic on the airwaves (ie; ch 6) will cause the openwrt acx driver to hang ! Routertech rules Actiontec for DSL and AP needs.
Use telnet for getenv & setenv, use fixenv to defrag after changes to the env. Here is an example of jewels in my environment:
mtd5 0x90350000,0x903f0000
RT_init_nvram mount -t minix /dev/mtdblock/5 /nvram/
led_conf led.gt704wg
cron_enable 1
RT_cmd_1 write_crontab.sh '47' '8' '*' '*' '*' '/sbin/reboot'
netshaper_enable 1
RT_cmd_2 netshaper -d 192.168.1.255/24 50000
RT_cmd_3 netshaper -s 192.168.1.255/24 50000
utelnetd_timeout 7200
Note that the reboot function must be setup using
Code: Select all
cronjob-env.sh '/sbin/reboot' '22' '2' '*' '*' '*' 'RT_cmd_1'
from the command line. Do not use setenv to enter that due to the quotes.
I found a common cause of bricking due to trying to set MTDs manually with FTP QUOTE or telnet or ssh. If you use the backspace key when typing the commands, the BS code gets into the env and even PCtool and CICLamab tools can make the env worse. CICLamab may truncate the env.
SO new revelation - do not use ftp or telnet to change the mtds. Use the RRT Router Repair tool only. And use care when using setenv. Using unsetenv will not remove the trashed entries in the env. Blank lines in the env are evidence of corrupt entries. Blame adam2 bootloader for all of this.
Peer separation, IP accounting and Netshaper are what makes RouterTech firmware standout
!