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 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 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.
- 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 are continuing with the 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 - if you have wireless and the Adam2 bootloader then you would download "Standard Wireless (Adam2 bootloader)".
- Busybox has been upgraded to v1.x. This has led to some space savings, while increasing the number of busybox applets quite dramatically, because we have been able to remove some standalone programs (see below).
It also means that nearly the same command set is supported across all platforms (i.e., 2mb flash and 4mb flash).
- msmtp has been removed in favour of busybox sendmail.
- Standalone stty and sync have been removed in favour of the busybox equivalents.
- Experimental darkstat binary (see http://dmr.ath.cx/net/darkstat/). It has to be run after a WAN connection is established. Included is a shell script (onconnectWAN) that can be used to schedule it to run on each bootup (by setting "darkstat_enable" to "yes" in the environment).
* try: darkstat -i ppp0
* or: setenv darkstat_enable yes
In order to see the output of darkstat, point your brower to http://192.168.1.1:667.
- "arp" problems have been fixed.
- Replaced the standalone arp with busybox arp.
- Fixed DSP 7.3A driver for standard firmware, and dsp73B replaces dsp6B for Annex B. ROHS firmware upgraded to dsp72.
- 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
- The bwbasic BASIC interpreter has replaced tcl (wireless routers only) .
- 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
- "Led" command added - to manipulate the router's lights. Run "Led" without parameters to see the syntax.
- Updated miniupnpd.
- "Assign ISP DNS" added to wireless ROHS firmware.
- A whole load of new busybox applets have been added.
- Small bug in tinyproxy fixed.
- Dropbear has been upgraded to v0.51.
- 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.
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.
As usual sourcecode, released under the GPL, is made available on Lara for budding developers.