In
order to see the output of
darkstat, point your brower to http://192.168.1.1:667 (or click
on "Darkstat"
in the "Status" menu in the router's WEB interface).
For wireless routers, because the (closed source) wireless AP driver is
incompatible with some tcpdump packets, packets (out interface) will
get dropped, and so the stats for that interface will show zero bytes
transferred. This problem does not exist with non-wireless firmwares.
Unfortunately, since we do not have the sources for the wireless AP
driver, we cannot fix the problem with wireless routers.
5. "arp" problems have
been fixed.
6. Replaced the
standalone arp with busybox arp.
7. Fixed DSP 7.3A
driver
for standard firmware, and dsp73B replaces dsp6B for Annex B. 1350A firmware upgraded to
dsp72.
8. Added code to
identify the flash chip manufacturer. The flash chip information is
written to /proc/flashinfo
*
It can
be read by: "cat /proc/flashinfo"
*
It is also displayed in the system diagnostics
9. The bwbasic BASIC
interpreter has replaced tcl (wireless routers only)
.
10. The led.conf file can now
be loaded from a minix partition if a full path name is supplied - and
as long as the minix partition is mounted via an "RT_init_x" command
*
e.g., setenv led_conf
/nvram/led_blahblah.conf
11. "Led"
command added - to manipulate the router's lights. Run "Led" without
parameters to see the syntax.
12. Updated miniupnpd.
13. "Assign ISP DNS" added
to wireless 1350A firmware.
14. A whole load of new busybox applets have been added.
15. Small bug in tinyproxy fixed.
16. Dropbear has been upgraded to v0.51.
17. Default ip-up
script added, for commands that will be executed when WAN connection is
established. This calls crond and darkstat if they are enabled. You can
add more commands to be executed by adding to /var/tmp/ppp_ip-up,
or /var/tmp/onconnectWAN.
version 2.5 (20080331)
(31 March 2008) - changes (compared with v2.3 and v2.4)
- Consolidates the
v2.3 and v2.4 branches
- Problem with saving DDNS settings (in the 1350A 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:password@myftp.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.
- Tcl interpreter removed
- 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 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 SAR605EW
router).
- "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 RouterTech
Development Team, 31 March 2008
- Support for the
TNETW1350A wireless chipset. This
requires a separate firmware image (with "1350A" in its name)
The RouterTech
Development Team, 19 October 2007
New
features applicable only to wireless routers, or non-wireless routers
with 4mb flash and 16mb RAM (e.g., ADSL2MUE)
1. Add support for TCPMSS
in kernel and add iptables command, to overcome MTU issues with some
websites. Unfortunately this eats some RAM, and so it has not been
added to RAM-challenged routers (i.e., those with only 8mb RAM).
2. New scripts:
* makemtd.sh
- create a new mtd partition automatically
* deletemtd.sh
- delete the mtd5 partition and restore the mtd partition
table to the values before the new mtd partition was created
3. Tcl interpreter added. You can either run it interactively
(by running "tcl")
or you can use it as the command shell for scripts
- e.g.,
#!/usr/bin/tcl
puts
"Hello World"
4. More friendly text editor - "easyedit" (renamed "edit" in the
firmware) added
5. scp
support added (this involved upgrading to bug-fixed versions of
uClibc's ftruncate64.c and truncate64.c). You can now use WinSCP or any other
scp client to upload/download files to/from the router
6. cifs
support added. This allows you to mount shared network drives on your
router. There is a ready-made mountpoint "/cifs" that can be
used for mounting
Syntax:
mount
-t cifs /<anything> <mountpoint> -o
user=MyWindowsLoginName,pass=MyWindowsPassword,unc=//<server_ipaddress>/<share_name>
Example:
mount
-t cifs /blah /cifs -o
user=freddy,pass=ddyfre,unc=//192.168.1.3/scratch_drive
This will give you read/write access (at
"/cifs/") to
the shared directory: "192.168.1.3/scratch_drive"
WARNING: You
MUST unmount any shared drive before any attempt to upgrade a firmware,
and before turning off your router.
7. Minix
(read/write)
filesystem support added. This allows you to
create read/write Minix partitions on the router.
There is a ready-made mountpoint "/nvram" that can be
used for mounting.
The steps to using the minix filesystem
support are:
A. create
a new mtd partition - in multiples of 1024 (e.g., "makemtd.sh mtd5 131072")
B. reboot
the router
C.
convert it to minix (e.g., "mkfs.minix
/dev/mtdblock/5")
D. mount
it (e.g., "mount -t
minix /dev/mtdblock/5 /nvram")
After this, you can write/read from/to "/nvram"
E. If you
want this to be mounted
automatically during bootup, use the "RT_cmd_x" functionality
e.g. setenv RT_cmd_2 "mount -t minix
/dev/mtdblock/5 /nvram"
F. The
system will look for "/nvram/startup.sh"
upon boot up, and will execute it if it is found
G. Always
unmount the partition
before rebooting, turning off the router, or flashing a new firmware
(e.g., "umount /dev/nvram") otherwise you WILL
lose data.
DIRE WARNINGS:
1. This feature works okay in our tests
- but your mileage may vary. Do NOT use
this feature unless you are very familiar with unbricking bricked
routers.
2. You MUST
unmount any minix partition before rebooting or
turning off the router, and before any attempt to upgrade a firmware,
otherwise the upgrade will NOT
happen!!!!!
8. New commands for minix filesystem support:
mkfs.minix -
create a new minix filesystem
fsck.minix -
check a minix filesystem
The RouterTech
Development Team, 5 June 2007
- Removed stray
'`' character on "home" page :-)
- Interactions with the bootloader environment for
Adam2-based routers now operate directly on the Adam2
environment "file" (/proc/sys/dev/adam2/environment)
instead of /proc/ticfg/env
- Works around problems with reading MAC addresses by saving
them directly into files in /var/tmp/ and then reading those. This
makes the issue of disappearing /proc/ticfg/env files less of a problem
for Adam2-based routers
- User
supplied DNS now works (you have to disable "Use Peer DNS"
on the ISP connection page)
- Default date/time is set on boot-up to the date/time that
the firmware was built
- Fixed bug whereby the wrong WEP key is displayed on the
"home" page
- Some memory optimisations should make everything work
smoother
- New NAT
optimisations should result in better P2P performance
- New commands introduced: "getenv" and "setenv" - there
is no longer any need to manipulate the bootloader environment files
directly: use these commands instead (see
rt_commands.html)
- New scripts: "routertech_start_inits.sh" and
"routertech_misc_inits.sh", which are called during init (they should NOT be called
directly)
- Wireless Production 1 has been added to the "wireless"
section
- New support for routers with ATMEL flash chips
(e.g., some DLink G604T/G624T)
- Facility to choose between dsp versions (for wireless
routers only (by setting the appropriate value for a new bootloader
environment variable, "dsp_ver"))
- e.g., running: setenv
dsp_ver dsp5A && /sbin/reboot would select
DSP v5, AnnexA. Choices are between dsp5A, dsp62A,
dsp71A,
and dsp6B
(i.e., dsp v6, AnnexB - note
that the AnnexB selection is untested). Note also that all
these are case-sensitive. The default is dsp62A.
- Facility to choose between atm driver versions (by setting
the appropriate value for a new bootloader environment variable, "atm_ver") - e.g.,
running: setenv
atm_ver dsp5A && /sbin/reboot would select
the "tiatm.o" driver, version 5. Choices are between dsp5A
and dsp62A.
Note also that all
these are case-sensitive. The default is dsp62A.
- Facility to choose between different versions of the LED
configuration file. - e.g., running: setenv
led_conf led.sar600 && /sbin/reboot would
select the LED file for the Solwse/Axtech 600E* series. Choices are
between led.g604t,
led.generic,
led.sar600,
and led.adsl2mue. The
default is led.generic.
- New command: "wakelan"
- to wake up PCs on a LAN
- Enhancement to the "Run Command" function - you can now
click on a "Command List" link to obtain help about the RouterTech
commands (see rt_commands.html)
- New scripts: "cron_disable.sh"
(to disable cron) and "cron_enable.sh"
(to re-enable cron). You should only run cron_disable.sh if
you won't ever need to setup "cron" jobs. This should free up some
memory, to be used for other things. Note however that there
are many
things that
depend on "cron" (e.g., chksync), so you should not disable cron unless
you are really sure that you want to lose all that functionality.
- New command: "tinyproxy"
- web proxy and URL filter (the URLs to be blocked must be put
in /var/tmp/tinyproxy.filter,
before starting tinyproxy)
- Update the code base in line with the latest Acorp patches.
The RouterTech
Development Team, 27 February 2007
- Bug in the
checksync feature fixed
- Functional DDNS (with no-ip support)
- A new msmtp client added (to send emails from the router)
- USB support added (not available via the web interface).
This can
be disabled by adding "usb_enable no" to the environment (i.e., run
this command once, from a telnet/ssh command prompt echo "usb_enable no" >
/proc/ticfg/env)
- Auto execution of shell scripts at bootup added. This
requires
entries in the environment (/proc/ticfg/env). If there is any entry in
/proc/ticfg/env that points to a shell script (i.e., ending with the
extension ".sh") that shell script will be executed everytime the
router boots up. There is a default "autoexec.sh" provided,
which
just runs any commands passed to it
- Several new commands added. See the
rt_commands.txt
file for
details. Some of them can be used for the auto execution feature - The
old (now obsolete) no-ip feature has been removed. It
is now part of the DDNS functionality
Known issues
The non-wireless versions (with only 8mb RAM) can sometimes struggle in
low memory situations and produce a sluggish web interface.
In
such cases, memory can be freed up by disabling unneeded features.
Prime candidates are upnp, snmp, and IP Accounting, and by running the
memory optiomiser periodically (e.g., via a "cron" job). The crontab file is "/var/spool/cron/crontabs/root".
A sample can be found here.
Running the memory optimiser periodically is easy to do now - see the
AUTOEXEC example for memchk.sh in rt_commands.html.
The RouterTech
Development Team, 29 October 2006
- Spanking new
RouterTech web interface :-)
- The "System" menu is now easily accessible from the top
menu bar
- More detailed information on the startup page
- Date/time stamps in the system log
- A functional
SNTP (under the "Advanced" menu) - this allows your router
to synchronise its date/time from public NTP servers - NOTE
that the router will detect a huge time difference when the date/time
is corrected, and will log you out from the web interface if you are
logged in - you will need to log in again
- 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) - this
allows you to see who is using all your bandwidth!
- System
Diagnostics (under the "Tools" menu) - this
gives you very detailed information about what is going on
inside your router
- Optimise RAM
(under the "Tools" menu) - this attempts to recover RAM lost due to
memory fragmentation and leakage
- Run Command
(under the
"Tools" menu) - this allows you to run from the web configuration
interface almost any command that you can run from the login shell. Use this feature with EXTREME
CAUTION. You could easily trash your router with it. YOU HAVE BEEN WARNED!
- 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.
This feature is experimental and is only for those who know what they
are doing. The feature is enabled by making an entry for "checksync.sh"
in "/proc/ticfg/env". Note that if you mess up that file, your router
may well become a brick, and you will need to try and recover it. For
those who are brave enough, entering the following command (only once)
from the command prompt in a telnet or ssh session, and then rebooting
the router,will do the job: echo "checksync.sh 6"
> /proc/ticfg/env (this
means "do the
sync checks every 6 hours" - you can specify any number
between 1 and 24 - and if you want to turn it off, specify 0)
- Quick configuration
- rdate
- ud
- 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 [Note:
fixed in v2.1]
- 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 [Note:
fixed in v2.5]
The RouterTech
Development Team, 4 September 2006
- Removed the user
"isp" and password "isp" from the
default config.xml.
The presence
of these settings in the default config.xml was a serious security risk,
in that it meant that anyone with access to your PC can login to the
router as "isp, isp" and the begin to wreak havoc with your settings!
- Various
changes made to the default /etc/init.d/rcS
(e.g., the use of a prime
number for /proc/sys/net/ipv4/netfilter/ip_conntrack_max
- this results
in better performance)
- Default
settings provided for several UK ISPs
- Some buggy code was fixed
- Several new
features:
- Extra
features enabled in Busybox applets
- Fixed the "manager_get_defaults - !node"
bug
- Several extra
commands (some of which have been referred to above). If
you are not
familiar with Linux/Unix, then you are probably not interested in what
follows.
These
are the extra commands, and their locations:
/bin/
- chgrp
- chmod
- chown
- df
- egrep
- grep
- hostname
- kill
- mkdir
- more
- mount
- netstat
- pidof
- rmdir
- sed
- touch
- true
- uname
/usr/bin/
- basename
- clear
- cmp
- dirname
- du
- expr
- find
- free
- head
- id
- killall
- telnet
- test
- tftp
- traceroute
- which
- xargs
/usr/local/bin/
- bunzip2
- bzcat
- cfgconv
(converts from binary config to xml and vice versa)
- cpio
- crond
- crontab
- ftp
- ftpget
- ftpput
- gunzip
- gzip
- klogd
(kernel log daemon
- allows you to log kernel messages)
- logger
(allows you to write a message to the system log)
- logread
(allows you to read system and kernel logs when directed to the
circular buffer, rather than to a file)
- rdate
(retrieves date and time from ntp time servers)
- nbtscan
- ez-ipupdate
- sft
(small ftp server,
running on port 5556 - if you have the sft client, you can upload files
from your PC to the router using the same port)
- syslogd
(syslog daemon
- allows you to have customised system logs)
- top
(displays currently running processes and important information about
them)
- ud
(uptime daemon
- reports on system uptime)
- uncompress
- unzip
- zcat
The RouterTech Development Team, 6 May 2006