RouterTech Firmware v2.5
Version: v2.5 (20080331)
Author: RouterTech Development Team (thechief, biro)
Other contributor(s): mstombs
Testers: Shotokan101, SyBorg, eMuNiX, mstombs
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
Flashing this firmware onto your router may well "brick" your router quite badly (e.g., it may trash the bootloader environment, which you will then need to restore).
You must not flash this firmware onto your router unless you are very familiar with the PC-Tool and are competent in using it to un-brick a router.
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!
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 - and if your environment gets corrupted, your router (or at least it's wireless functionality) might be irrecoverable.
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, 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.
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. 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
We have created a new file structure for the downloads which should make it much easier to decide which release to download. Assuming your router is compatible you just need to download the release that matches so say if you have wireless and the Adam2 bootloader then you would download "Standard Wireless (Adam2 bootloader)"
- Consolidates the v2.3 and v2.4 branches
- Problem with saving DDNS settings (in the ROHS version) fixed
- New facility for executing commands earlier during bootup - by "RT_init_x" entries in the environment ("x") stands for a number or some other distinguishing letter/number: e.g.,
setenv RT_init_1 "mount -t minix /dev/mtdblock/5 /nvram" (will execute "mount -t minix /dev/mtdblock/5 /nvram" very early in the boot process)
- Transparent operation supported for Tinyproxy (run "tinytrans.sh" rather than just "tinyproxy")
- ftpfs support added to enable the mounting of directories from an ftp server onto the router (wireless routers only). Enable this by running "insmod ftpfs.o" and then using "ftpmount" to mount the ftp server - e.g., ftpmount root:email@example.com/root/export /ftpfs (this mounts the directory "/root/export" on the ftp server "myftp.com", onto the router's "/ftpfs" directory). It is generally a good idea not to supply your password as a parameter, since ftpmount will ask for it.
- IGMP snooping removed from the web interfaces of routers that don't support it
- New scripts added to set up cron jobs more easily (cronjob.sh, cronjob-env.sh). Run the commands to see the syntax.
- UPnP bugs fixed (thanks to mstombs)
- New upnp daemon based on miniupnpd (see upnp.txt)
- Bugs with regard to multiple sntp instances fixed
- New dsp/atm drivers (7.03) added to the wireless firmwares (although not for the TNETW1350A chip)
- Realtek switch supported added to the TNETW1350A ("ROHS") wireless firmware (this allows the firmware to now support routers using the Realtek switch such as the PTI 8505G, and those with the IP175C switch, such as the Solwise/Aztech SAR605EW routers).
- "chksync.sh" replaced with simply "chksync", to reduce confusion
- More led.conf files added
- Fixed "lanbridge3" problem in 4 port routers
- Fixed "lanbridge0" to "lanbridge2" problem in 1 port routers
- Separate firmware images no longer required for Adam2 routers with ATMEL flash (e.g., G604T)
- New (experimental) feature - "netshaper". Like the alternative "rshaper", this allows you to limit the bandwidth by IP addresses/ranges - plus a command to configure it: "netshaper"
e.g., "netshaper -d 192.168.1.6 32768" (will limit the bandwidth of the computer at 192.168.1.6 to 32kbps)
The netshaper module is NOT loaded by default. Run this command to enable it: setenv "netshaper_enable 1" && /sbin/reboot
NOTE that the netshaper facility CANNOT be used in conjunction with rshaper. You have to choose one or the other. Run "netshaper" without any arguments to see the syntax.
- Experimental script to enable "WAN IP local NAT Loopback" (localnat.sh)
Usage: "localnat.sh UP" to setup/refresh; "localnat.sh init" to install and update on each ppp-up event; "localnat.sh exit" de-installs.
- User writable /etc /ppp/ip-up and /etc /ppp/ip-down scripts, currently used by half-bridge, localnat and upnp, but can be added to.
- Experimental support for AnnexB in non-wireless firmwares (look in the "annexb" sub-directory). Please let us know whether this works (or not!).
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.
BE SURE TO READ ALL THE DOCUMENTATION IN THE FIRMWARE DOWNLOADS BEFORE TRYING ANYTHING WITH THIS FIRMWARE. Otherwise, YOU ARE ON YOUR OWN.
If you are a developer and want to get your hands on our sources to do some tinkering then you can access them on the following links:
Standard Firmware Sources
ROHS Firmware Sources