RouterTech AR7WRD/AR7RD Firmware v2.0
Author: RouterTech Development Team (thechief, biro)
Version: v2.0 (20060904)
Category: Third-party (3rd-party) Router Firmwares
This firmware supports the following routers and their clones provided by different companies and MAY support others too - check the docs or ask us in the forums: SART2/SWAMR/SWART2/GWART2/Solwise/ADDON/Roper FLYNET/ASUS AAM6020VI-T4
This firmware has been built for the family of routers based on the TI AR7WRD and AR7RD platforms (specifics shown in the compatibility section of this release and in the documentation provided with the firmware). Reading the documentation below, and that included with this firmware is essential to ensure successful flashing. Support for this firmware can only be obtained in the firmware forum of this site. Bug reports should be filed in the same forum, with a prefix to the the thread title of [BUG]. This will allow the development team to read, discuss and fix the bug before updating the firmware and closing the thread.
While we provide full support for our firmwares and will help out with issues or problems in any way we can we will not be held liable in any way in the unlikely event of damage occuring to your router. You are advised to read all documentation including that related to recovery of routers after a failed flash to ensure the highest chance of a successful upgrade and the smallest chance of problems.
Which version for me?
To determine which version of firmware you need then you need to find out if you use the adam2 bootloader or psp. You don't need to know what these mean, simply follow the instructions below.
Note: with respect to some routers (e.g., the ADDON GWAR3000) the manufacturers alternate between the psp boot loader and the Adam2 boot loader. So it is absolutely essential that everybody (regardless of the router that they have) verifies their routers' bootloaders before trying anything.
In order to ascertain the bootloader that your router is using, you should telnet ot ssh to the router, and run the command:
If the "bootloaderVersion" is 1.2.x, AND the "PROMPT" contains something like "psbl" then your router is using the PSP bootloader, and you should use the firmware with "pspboot" in the filename.
Code: Select all
By the same token, if your "bootloaderVersion" is something like "0.22.x", AND the "PROMPT" contains something like "Adam2", then your router is using the Adam2 bootloader, and you should use the firmware with "adam2" in the filename.
A few more words on versions...
It has come to our attention that due to incorrect labelling on some Safecom routers people without wireless are attempting to load the routertech firmware for wireless routers and encountering problems. This is not a fault with the firmware just that the labelling on the router is incorrect.
Please then note that the SWART2-54125 / GWART2-54125 are the WIRELESS versions and the SART2-4115 / GART2-4115 DON'T have wireless but may be wrongly labelled (By SC ) as SWART2-54125 / GWART2-54125. Note the extra W. Please check to see if your router actually has wireless before believing that you need the routertech firmware for wireless routers.
We have had many questions about version names from ebuyer. It is therefore worth mentioning that the G****** are the Ebuyer GURU branded versions of the S****** from Safecom.
BEFORE you try upgrading to this firmware, you are advised to take the following precautions:
1. Run the "cat /proc/ticfg/env" command (as above) to check that the environment variable called "IPA" is set to 192.168.1.1 - and, if not, then set it to 192.168.1.1 (or to whatever you use normally). This is how to do it (from the router's shell command line):
Code: Select all
echo IPA 192.168.1.1 > /proc/ticfg/env
2. Get and install a copy of the PCTool (not to make any changes but just connect) to the router with it, so that you can get a 'feel' for the timing etc. You will need the PCTool to recover the router if the firmware upgrade process goes wrong, and "bricks" your router.
You can get the PCTool here: viewtopic.php?t=335
If something goes wrong...
Sometimes upgrades can go wrong and your router becomes a "brick". If this occurs you will need to attempt a rescue. See the details here: viewtopic.php?t=242
The tag-lines on the firmwares are not definitive with respect to the routers they can be used on by any means. To be sure check your router make, check the docs in each firmware package, check to see whether your router has a psp or Adam2 bootloader, check that the "ProductID" is either "AR7RD" or "AR7WRD" (when you run the command "cat /proc/ticfg/env" as above), and, if in any doubt ask in our forums BEFORE you try anything - we are here to help!
version 2.0 (20060904) (4th September 2006) - changes (compared with v1.0 firmware)
- * Spanking new RouterTech web interface (courtesy of Neo)
* The "System" menu is now easily accessible from the top menu bar
* More detailed information on the startup page
* A functional SNTP (under the "Advanced" menu)
* DNS configuration (under the "Setup" menu) - this allows you to specify your ISP's DNS servers manually
* IPAccount (enabled under the "Advanced" menu, and observable under the "Status" menu)
* System Diagnostics (under the "Tools" menu)
* Optimise RAM (under the "Tools" menu - experimental)
* Run Command (under the "Tools" menu)
* Better organisation of the information on the "Modem Status" page
* The ability for the router to monitor (at specified hourly intervals) whether the external (WAN) connection is active, and to reboot itself it it has lost its sync upon a check being made (experimental).
* Better support for P2P software
* Improved firmware support for preventing full NAT tables
- * Quick configuration
* nbtscan (only removed from the AR7RD firmware)
* ez-ipupdate (only removed from the AR7RD firmware)
* The SFT server is no longer enabled by default - but it can be executed by anyone who wants to run it manually.
- * No USB suppport for the 4-port versions
* SNMP will probably still kill the router, requiring a reboot (it eats memory, until the router runs of out RAM and crashes). The new IPAccount feature provides some of the information that would normally be sought by using SNMP
* UPnP will also probably do the same as SNMP
The links to our firmware require you to be registered and logged into the site to see and use them. This is to make sure we can provide you with support easily if you need it. When logged in they appear below this post
As usual for the budding developers amongst you the sourcecode from which all our firmwares released here has been compiled is made available under the GPL. Files are on lara. Grab your copy here