Modifying The DD-WRT GUI
Joinsubscribers and get a daily digest of news, geek trivia, and our feature articles. Assuming you are familiar with those topics, keep reading. Keep in mind that this guide is a little more technical, and beginners should be careful when modding their router. The firmware modification kit enables one to make modifications to the firmware without compiling it from source. Making changes this way, with the aid of the provided scripts, becomes a simple matter of downloading, replacing and deleting some files. In addition, this method has the added advantage of relieving you from the JFFS dependency for packages installation, which for routers with only 4MB of flash is a real problem. Picture by publicenergy. Once you have followed this procedure it should be relevantly simple to adapt it for other packages installations. Warning : Tread lightly… keep in mind that incorrect usage of the modification kit, can leave you with a router that needs de-brick-ing as in turn it into a useless brick. The firmware modification kit has some dependencies for it to compile and work. The first thing to consider is which version you want to use? In order to make it easier to keep track of what version we are using, rename the downloaded file to represent its version number:. In order to be able to change files within the firmware we need to extract its content into a temporary directory. The syntax of this command is:. Note: The first time you run this command, it builds the mod-kit tools on your system. Now that the firmware is extracted we can install the packages to it. In general, the procedure is to download the package and its dependencies in the form of an ipk file from the openWRT repository. Once downloaded install them into the extracted firmware using the provided script. Knockd is a daemon that listens to communication events at the link layer for sequences then acts on them. Using this technique you could trigger the server to perform any sort of operation you need of it remotely across the internet without exposing your home network. We promised you back then that we will show how to configure this for DD-WRT and we will now deliver. This is mainly useful if your going to create scripts on the router that you would like to receive feedback on their operation via email. Gmailyou have to install the openSSL pakage as well. Configurations There is a limitation with the SSMTP package, that it is not possible to invoke it with an alternate configuration file. Because the firmware is read-only when its on the router, that means that out of the box we can only hardcode the configuration into the firmware.
These docs may no longer be accurate. Description II. Why is this useful? Where to get the kit IV. Requirements V. Compatibility VI. Acknowledgements and more IX. Links X. Revision history. Description This kit gives the user the ability to make changes to a firmware image without recompiling the firmware sources. It works by extracting the firmware into its component parts, then extracting the file system image assuming its in one the supported formats. The user can then make modifications to the extracted file system, and rebuild the firmware image. Although this kit completely automates the process, it is also useful for those who need a handy collection of utilities to manipulate firmware images. The following utilities are included in this kit, along with scripts to automate their use:. This kit doesn't just collect existing tools, it also offers new ones and modifications to existing ones. Custom code currently is:. Currently TRX and uImage headers are supported. This tool wasn't officially made available until squashfs 3. A list of some of the many reasons this might be desired are:. The best way to download and use this kit is to check out the sources from the repository. The automated scripts all automatically build the executables, and the sources. It is easy as downloading something and using it that way. Also, if you are unable to use a simple SVN checkout, then it is likely that this kit is a danger to you because it is for advanced users. All of the many OpenWrt packages should work with OpenWrt images and many other firmware images. I've worked to make sure the requirements are low enough for anyone to use this kit. However, to reduce distribution costs and better represent the multi-platform capabilities of this kit, the binary tools in the kit do automatically build themselves the first time you run one of the scripts. The few requirements are all basic items that everyone has easy access to:. The kit is probably not far from compatibility, but easier to just install a linux VM. Any TRX style firmware image format should that uses squashfs-lzma as a root file system work fine. Firmwares that use regular zlib squashfs or unsupported file systems will work if the steps that extract the file system and rebuild the file system are tweaked. Instructions I've scripts that simply and abstract the firmware modification process. Basically, it's a one-step process to extract the firmware, and a one-step process to rebuild the firmware. There are also scripts to install or remove individual packages or entire directories of packages. You must run this tool from inside the directory it exists in. This is where the intermediate files and the extracted file system will be stored.