The independent technical support site for all things networking!

Archive for the ‘Announcements’ Category

RouterTech Firmware 2.92

January 10th, 2010 by Kieran in Announcements

With over 25 new features and bug fixes, the RouterTech team is proud to announce the release of version 2.92 of it’s firmware. Details of all changes and fixes are shown in the list below.

1. New shell script: (wireless firmwares only) – restarts the wireless access point.

2. Busybox “sync” has been replaced with a stand-alone sync utility (wireless firmwares only).

3. Fixed a display issue with the printenv command (problem with printing newlines).

4. Fixed a display issue for pppoe on the Status menu.

5. Following a poll on the forum, the bwbasic interpreter has been removed.

6. Following a poll and other discussions on the forum, the default DSP driver for the standard firmwares has been set to dsp75.

7. New feature: udpxy added to the wireless firmwares. The program allows you to relay multicast UDP traffic to a client’s TCP (HTTP) connection (unicast). This allows you to use IP TV (UDP multicast) services via wifi. Example: “udpxy -m br1 -p 88 -S”
where: m – interface (LAN group) where the IP-TV bridge connection added.
-p – the port to listen on… here, it is port 88
-S – enable the bandwidth statistics. The status page is available at (router ip and 88 port from the -p 88 option). Also the -B option can be used to setup udpxy’s cache size, e.g: “udpxy -m br1 -p 88 -B 1024K -S”
After this you can use the IP-TV as unicast by ethernet and wi-fi, for example if the udp multicast url is udp://@ – you can access it as

8. The darkstat feature has been removed from the firmwares for routers with 2mb flash.

9. The rt_commands.html file has been removed from the binary firmwares.

10. Busybox has been upgraded to v1.15.3.

11. New shell script: – to start the firmware’s http server, optionally specifying the http server’s port (the default port is 80). This script runs during the boot-up process to start the http server for the web configuration.

12. New environment variable: http_port – to specify a port for the http server. If this is set to “none”, then the http server will not be started during the bootup process – this can save significant memory on low memory routers – but you will not be able to open the web configuration with this setting. If you thereafter wish to configure the router from its web interface in such a case, you will need to run from the command line, either with no parameters, or with the desired port number.

13. Slight change to the syntax of to: –threshold=<number> (note the “=” sign).

14. The dnsproxy server has been upgraded from dproxy-nexgen to dnsmasq v2.51 (still masquerading as “dproxy”) for its up-to-date caching dns proxy functions only (NOT lan dhcp). The code has been patched, to reduce size by disabling unused options and functions, to ignore command line parameters, and to do all configuration by configuration file. Additional conf files can be added to /tmp/dns.d/. dnsmasq supports many options and enables additional functions such as auto selection of the fastest responding dns server from all configured, and domain blocking – exploited by the extra_dns and adblock functions below.

15. New shell scripts: and – to assist in blocking popup adverts by means of “dns poisoning”. It is basically obsolete if you can use Firefox and adblock plus – but otherwise (e.g., if using IE) it is very useful. Advantages (a) it only needs to be implemented once – on the router – and all clients would benefit from the ad blocking, etc (b) it works with all browsers such such as IE which don’t have adblock (c) some of the hosts in the hosts block lists do some of what tinyproxy could have achieved, re: parental control. For this purpose, downloads and converts one of a number of common internet resources (“small”, “medium”, “large”, or “xlarge”) of ad servers to be blocked. The largest of these uses a lot of cpu cycles on the router (about 20%) – but since the router’s cpu is largely idle most of the time, this is not a major issue. The smallest consumes only about 5% cpu cycles. Run with no parameters to see the syntax. is a shell to, allowing it to download more than one of the internet lists at once (e.g., “ exit small large”). Note that, for routers with low memory (i.e., 8mb RAM), you should never use “large” or “xlarge”. In fact, “small” might be the only one that such routers will be able to cope with. If you try to download more lists than your free memory can cope with, your router WILL crash!
NOTE: you MUST always run “ exit” to remove the adblock features from memory, before any attempt to upgrade the firmware.

16. New environment variable: adblock – use this to schedule to run when a WAN connection is made. The values should be the parameters that you wish to pass to (e.g., setenv adblock “exit medium xlarge”). On routers with 8mb RAM, you should only supply “small” – do NOT try to use the medium/large/xlarge lists on such routers.

17. New utility: pixelserv – a tiny webserver that serves up a single pixel to any request. It can be used in conjunction with the adblock features.

18. New shell script: uptime – parses and displays the system uptime information.

19. New shell script: memavail – reports the amount of RAM that is available to be used.

20. New environment variable: extra_dns – to add DNS servers from a selection (“All”, “OpenDNS”, “Google”, “UltraDNS”, “DNSResolvers”, or “BT”) in dnsmasq format. You can set “extra_dns” to any of these, to a combination of them, or to “All”, and you can use either their full names, or the first letter of their names – e.g., setenv extra_dns “O U D B” – will select DNS servers from OpenDNS, UltraDNS, DNSResolvers, and BT; setenv extra_dns “A” or setenv extra_dns “1” will select all of them.

21. New environment variable: extra_resolvers – to add ALL the DNS servers specified above, in resolv.conf format. These servers are prepended to /etc/resolv.conf. In the TWNETW1350A firmware, only the first three will be used.

22. New environment variable: static_dns – this is useful mainly for those with DHCP (as opposed to pppoa/pppoe) connections, who do not have the “Use Peer DNS” button in the firmware’s web interface. Set it to 1 to prevent the dhcp server from overwriting your static DNS entries.

22. The ssh server (dropbear) has been upgraded from v0.51 to v0.52 in line with upstream package source. A default idle timeout of 120s has also been enabled, to prevent disconnected instances of dropbear from hanging around wasting memory and preventing further logins (maximum 2 simultaneous allowed). To avoid the timeout please enable a keepalive of say 30s in your ssh client (supported by putty and winscp, for example). The dropbear code has been patched to accept this null packet keepalive – the default code acts only on data transfer.

23. The upnp daemon has been upgraded to v1.4 20091102 in line with upstream. Additional optional configuration items include the ability to not show the Internet server in Windows “My network places”, by specifying a null presentation_url.

24. New hook to run a user-supplied script (/var/tmp/ when before rebooting or shutting down the router via the reboot or shutdown commands. When either command is executed, it will search for “/var/tmp/”, and, if it is found, it will be executed immediately. After this, the normal house-cleaning on reboot/shutdown will continue.

25. Wide display support enabled for the “ps” command. This is triggered by running “ps -ww”. The downside of this is that “ps aux” will now generate an error. So you can only run “ps” with no parameters (which will behave as it would when you used to run “ps aux”), or run it with “-w” (132 column width) or “-ww” (2048 column width. Users who have written scripts with “ps aux” will need to change their scripts to just call “ps” (busybox ignored the “aux” anyway). The command “ps -ww” will display everything (up to a width of 2048 characters). It would however need to be used with great discretion, because all the username and password, etc., passed to pppd will be displayed in its full glory (i.e., you don’t really want to post the output of “ps ww” on the forum!).

26. Text files with the mtd calculations for each firmware image now added to each firmware release. Each firmware image has a corresponding “_mtd.txt” file, which shows the correct mtd partition settings for that firmware image. The text files are in unix format (for very good reasons), and so to view them under Windows, you will require a text editor that understands unix line endings.

Thanks to all who worked hard on making this release possible

RouterTech Firmware v2.91

September 14th, 2009 by Kieran in Announcements

RouterTech Firmware v2.91 has been released. While only a minor version number increase since our last release, we’ve included over 20 different changes to fix issues and generally make the firmware better.

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: (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: – 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: 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 (other than the 1350A wireless routers) has 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 – – 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 – the “size” parameter should now be in kilobytes (multiples of 64) and not in bytes – e.g. 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 – – 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.

Thanks to all who worked hard developing and testing this release!

New Look Website

August 22nd, 2009 by Kieran in Announcements

Welcome to the new look RouterTech website!

It might take a short while to find your way around the new layout if you are a regular but by and large things are laid out in a similar way. If you are a newcomer we hope the site will in fact be easier to use than the old one; we’ve consolidated a lot of content into specific pages and moved things out from the forum that really should have been on pages.

Regulars will be delighted to note that we have embraced the new version of phpBB and so are now packing a huge punch when it comes to user features – we hope you find them as useful from a user perspective as we do as staff.

Small points about the design will probably be in a state of flux over the next few weeks but generally we don’t intend to mess with things too much so we hope your experience will be a trouble free and positive one.

If you’re reading this you will have found our new blog and we encourage you to subscribe to this as a means of quickly finding out what is going on with our software and also in the world of home routing generally.

Powered by phpBB & WordPress     Hosted by Kieran O'Shea     Site Code © 2005-2011 Kieran O'Shea     All site contents © 2005-2011 RouterTech - All rights reserved     Valid HTML     Valid CSS     Graphics by Neo