RouterTech Firmware v2.91 Release (20090912)

Software and Firmware releases made by our in-house development team. You may not post here, but subscribing to this forum will allow you to be notified of all new releases, and this is recommended. Support for releases will be provided in the Software/Firmware forums.
Locked
User avatar
Kieran
RouterTech Team
RouterTech Team
Posts: 2664
Joined: Fri Jan 20, 2006 11:30 am
Location: London
Contact:

RouterTech Firmware v2.91 Release (20090912)

Post by Kieran » Mon Sep 14, 2009 8:27 pm

NOTE: this firmware has been superseded by a newer version. You can get the latest version HERE

RouterTech Firmware v2.91 [NOW OBSOLETE!]

Version: v2.91 (20090912)
Author: RouterTech Development Team (thechief)
Other contributor(s): mstombs
Testers: Various RT staff & forum members

Compatible Routers
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.

Upgrading
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
  1. First reset the router to factory defaults before trying to install this firmware.
  2. When upgrading via the web interface, (particularly for the ROHS 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.
  3. Once your router has been upgraded and be seen to be working you must reset to factory defaults again
Note: Before installing this firmware, you must, among other things (see the docs in the zip file for those other things) back up a copy of your router's current "/etc /led.conf" file. We only have a few LED configuration files, and the chances are that we do not have one suitable for your own router. If you do not keep a copy of the original contents of that file, then we have no way of knowing how your LEDs should be configured, and the LEDs will always be wrong. This will not affect the router's normal operation - but you the LEDs will not be reporting the correct operations.

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

Files
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)".

Changelog
1. Bug fix: the "Restart Access Point" button in 4-port non-wireless firmwares removed.

2. Busybox upgraded to v1.14.3.

3. Utilities: "insmod" is now a shell to modprobe; use "insmod-bin" for the "real" insmod (this is a result of the busybox upgrade to v1.14.x and higher).

4. Some security improvements.

5. The "RT configurations" feature has been updated to be able to specify Led file and DSP driver. The available ones are shown in brackets. The desired Led or DSP file should be specified as it
appears in the brackets - and their file extensions must NOT be specified.

6. A new shell script: adam2-defragenv.sh (for routers with the Adam2 bootloader only). It will defragment the Adam2 bootloader environment. The script has to be run from a telnet/ssh login session. Normally, you should not run this command directly. Instead, use setenv DEFRAG DEFRAG (see below).

7. New command for defragmenting the environment - setenv DEFRAG DEFRAG (note the capitals!) - must be run from a telnet/ssh login session (never from the web interface).
NOTE: This command must only be used as a last resort. As with any low-level operation that writes to the router's flash chip, things can go badly wrong. The recommended way to defragment the Adam2 bootloader environment is to run "fixenv" from the bootloader command prompt. The recommended way to defragment the PSP bootloader environment is to run "defragenv" from the bootloader command prompt. You will need a serial console to run commands from the bootloader command prompt.

8. A new shell script: bandwidth.sh - allows you to throttle the bandwidths of those who have exceeded a specified transfer bandwidth (default 500mb) to a very very low speed (default 128 bytes-per-sec), and to display current bandwidth usage data. Requires IP Account to be enabled (example: bandwidth.sh 250 1024 reset - will throttle any client that has exceeded 250mb bandwidth to 1024 bytes per second; the "reset" parameter is optional; if used, then it will first reset the IPAccount statistics - this is useful if your router is not rebooted everyday). Run the command with no parameter to see the syntax.

9. New support for wireless Adam2-based routers with just one ethernet port (e.g., the Actiontec GT701WG).

10. pppd upgraded to v2.4.4.

11. New support for siproxd (wireless routers only) (courtesy of Richard Antony Burton).

12. New environment variable ("siproxd_enable" (wireless routers only)). If set to 1, this will trigger automatic execution of siproxd each time the router boots up, using a default configuration file (/etc/siproxd.conf).

13. Enhancements to the "RT Configurations" page in the "Tools" menu. You can now a) enable/disable Siproxd from this page, and b) select/de-select DSP drivers and Led conf files.

14. DSP/tiatim v6.x has been restored to the AnnexA firmwares.

15. The default DSP driver has generally been changed to DSP/tiatm v6.x. This should free up some memory on low memory routers, and should also be less demanding on the hardware. In the firmwares that allowed for changing the DSP/tiatm drivers, the facility to change the drivers still remains.

16. New DDNS support for dnsomatic (courtesy of Richard Antony Burton).

17. New command: wol_forward (courtesy of Richard Antony Burton). This command is to wake a machine on the LAN from outside the network, via settings in the new wol_forward environment variable. Example: setenv wol_forward "ppp0 br0 7".

18. Following a poll on the forum, Tinyproxy has been removed from all our firmwares and is no longer a feature of the RouterTech firmwares.

19. A new shell script - reset-config.sh - resets the configuration to defaults. Use this command only as a last resort - when everything else fails (e.g., when reset from the web interface fails, or when you are unable to access the web interface).

20. New tool - mtd3_app - this is a low level helper program for some firmware scripts. Do NOT attempt to run it manually!

21. Change in the syntax of makemtd.sh - the "size" parameter should now be in kilobytes (multiples of 64) and not in bytes - e.g. makemtd.sh mtd5 192 auto_minix. The valid sizes are: 64; 128; 192; 256; 320; 384; 448; 512; 576; 640; 704; 768; 832; or 896. If an invalid/unsupported size parameter is given, the script will simply print an error message and will stop. Be sure to not try to create a new partition that is bigger than the available flash space, or you will trash your router.

22. A new shell script - linecount.sh - returns the number of lines in a text file (or "-1" on error). Empty lines and comment lines (beginning with a "#") will be ignored. If you want comment lines to be counted as well, then supply the switch: "--with-comments".

23. A new shell script - check_env - this is a rough-and-ready check for bootloader environment fragmentation (Adam2 routers only). It returns 1 if the bootloader appears to be fragmented, and 0 if it does not appear to be fragmented.

Downloading
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.

Sourcecode
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.
You do not have the required permissions to view the files attached to this post.
Kieran
"Indeed!"
Invaluable links: Forum Rules | Networking Guides | FAQ | Site Search | Forum Search <-- Use it or feel my wrath!
No support via PM, please ask your questions in the forum!
Locked