RouterTech Firmware v2.91.1 [NOW OBSOLETE]
Version: v2.91.1 (20090922)
Author: RouterTech Development Team (thechief)
Other contributor(s): mstombs
Testers: Various RT staff & forum members
Polls: Participate in the POLLS for Firmware v2.92!
A list of compatible routers is available in our knowledge base. Please check this before even contemplating an upgrade and remember you should always ask in our forum if unsure. Also see the section below on backing up and compatibility.
Disclaimer & Warning
1. Flashing custom firmwares onto a router is not for novices, as the process may well "brick" the router.
2. You must not flash this firmware onto your router unless you are very familiar with the PC-Tool (or similar) and are competent in using it to un-brick a router.
3. Please take this warning very seriously. If you are not adept at recovering bricked routers, and if you are not familiar with the PC-Tool, then do not install this firmware!
4. Do not even consider installing this firmware without first reading all the documentation supplied with the firmware. If you fail to observe this, then you are entirely on your own.
5. Do not even consider installing this firmware without first running the Router Upgrade Checker (RUC) and following whatever counsel it gives. If you fail to observe this, then you are entirely on your own.
6. Do not even consider installing this firmware unless you have first backed up your router's bootloader environment (i.e., /proc/ticfg/env) to your hard disk. If you fail to observe this, then you are entirely on your own.
Backing up & Compatibility
For ease we recommend you run the Router Upgrade Checker - this will backup your environment, LED config, current config, default config, generate a recovery script for the bootloader environment, and tell you if your router is suitable for this firmware.
Before upgrading you must backup your router config as detailed above and reset to factory defaults.
Please remember to run the Router Upgrade Check BEFORE you upgrade!
If you choose to upgrade via the router's web interface, then you MUST observe the following
- First reset the router to factory defaults before trying to install this firmware.
- When upgrading via the web interface, (particularly for the 1350A wireless firmware) you must wait for at least 7 minutes for the new firmware to establish itself. Do not do anything to the router for at least 7 minutes from the moment the upgrade process starts, and do not interrupt the upgrade process.
- Once your router has been upgraded and be seen to be working you must reset to factory defaults again
The Router Upgrade Checker as described in the backup and compatibility section above can backup your LED config - if you use the Router Upgrade Checker then you can double-check the output by looking in the check*.txt file for data after the "/etc /led.conf" line.
Comprehensive Documentation and Frequently Asked Questions (FAQs)
While full documentation is included with every release of our firmware we have also made it available as a separate download below so you can take time to read it before even needing to download a firmware. The router upgrade and firmware FAQs are also hosted online HERE. We recommend you do this as it will give you a chance to properly familiarise yourself with the process and get every angle covered etc.
PC-Tool and repairing / unbricking
Please see this forum topic
Assuming your router is compatible, you just need to download the release that matches your router - if you have wireless and the Adam2 bootloader then you would download "Standard Wireless (Adam2 bootloader)".
1. Bug fix for ddns in the standard firmwares (the 1350A wireless firmwares were not affected).
2. New utility added: mjproxy - a very small proxy for SIP. It has an algorithm that computes the MD5 to allow the user to be authenticated and logged on with the SIP registrar of a VOIP service.
3. New shell script: auto_defragenv.sh - defragments the environment after the fragmentation level has passed a specified threshold (default 30 for Adam2, and 50 for PSPboot). This can be changed by supplying "--threshold <number>" at the command line, or by setting the new environment variable "DEFRAG_THRESHOLD" to the desired number (where "number" stands for a positive whole number). The number should not normally be less than 20 nor exceed 40 (Adam2) or 60 (PSPboot). Note that no check is done as to whether the number is sensible. The defaults are sensible, and should normally left well alone. The command line parameters take precedence over any value in "DEFRAG_THRESHOLD".
4. New environment variable: DEFRAG_THRESHOLD - to specify a different maximum fragmentation threshold for the auto_defragenv.sh script.
5. Updated version of darkstat (latest from the git repository)
6. Busybox upgraded to v1.14.4.
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 (in this forum) if you need it. When logged in they appear below this post.
Now also available to download via the forum when logged in
BE SURE TO READ ALL THE DOCUMENTATION IN THE FIRMWARE DOWNLOADS BEFORE TRYING ANYTHING WITH THIS FIRMWARE. Otherwise, YOU ARE ON YOUR OWN.