X-Wrt is a set of packages and patches to enhance the end user experience of OpenWrt. It is NOT a fork of OpenWrt. We work in conjunction with the OpenWrt developers to extend OpenWrt.
Our packages currently work with the latest public release of OpenWrt - Kamikaze 7.09. Support of OpenWrt's upcoming Kamikaze firmware is coming soon. We currently have a stable webif for OpenWrt White Russian. Explore this page to learn about our work, or just skip straight to installing X-Wrt and see the fruits of our labor yourself.
X-Wrt was started because there was a need for end user extensions to OpenWrt, such as an enhanced web management console (webif). For a long time now it has been established that OpenWrt is the best firmware in its class. It far exceeds other firmwares in performance, stability, extensibility, robustness, and design. We at X-Wrt decided it was long past time for end users to get access to this superior firmware.
We are a separate project from OpenWrt due to the difference in focus and development ideals. We are considerably more pragmatic than OpenWrt and have the goal of providing solutions today, while OpenWrt has a more idealistic development philosophy and intends to perfect the firmware core, no matter how many rewrites and how much time it takes. This difference in development attitude creates a complimentary atmosphere that benefits everyone.
This is a free, open-source, community-driven project. Our primary project ideals are:
This project is still young, but we are accomplishing things at a rapid pace. All our work is currently in beta, but our code can be used today and is more stable than many firmwares in their 'final' state. You can keep up with the latest developments by checking the xwrt-svncheckins message list that archives commit logs as they happen: https://lists.berlios.de/pipermail/xwrt-svncheckins.
Our latest stable snapshot of webif² is Milestone 3 RC2. The install buttons below will have you install it. If you then use the webif's update feature you will get the latest internal build.
X-Wrt is a set of packages that overlay OpenWrt. There are two primary ways to install and use X-Wrt on your router:
If you do not already have OpenWrt White Russian on your router, download an appropriate OpenWrt White Russian image and flash it (follow instructions in OpenWrt's wiki). We recommend White Russian RC5, RC6, or 0.9. Kamikaze support is a work in progress, but many functions are supported already.WARNING: Do not install webif² on the micro images OpenWrt distributes. They lack the 'ipkg' package, which is currently critical to the proper operation of webif²
echo "src X-Wrt http://download2.berlios.de/pub/xwrt/packages" >> /etc/ipkg.conf
ipkg install http://ftp.berlios.de/pub/xwrt/webif_latest_stable.ipk
If the display of the web pages looks funny, do a hard refresh (hold down SHIFT and click REFRESH) to clear out the old CSS.
Since our new webif is in beta sometimes you can get a build that has problems. The best advice is:
ipkg install http://ftp.berlios.de/pub/xwrt/webif_latest.ipk -force-reinstall
Although all our work is based around our webif² package, we actually have a number of packages to add to OpenWrt. At present they are all for White Russian, but we are moving actively into Kamikaze right now. A list of some of our packages are:
Last Release: Milestone 3 RC2
For every Milestone there are countless updates, so this is far from a comprehensive list of changes and planned changes. However, it does give some idea of what our development plan is.
Of course, this table only shows the release we have planned in the immediate future.
At RC2 Now
We are working actively towards a version of the webif for OpenWrt's long delayed next generation, Kamikaze. The webif is not finished yet you get its status at http://wiki.x-wrt.org/index.php/Kamikaze.
OpenWrt Kamikaze represents a substantial and fundamental change. It is not simply a new version of White Russian, but instead a complete rewrite of the build root and configuration structure. That is why White Russian went stagnant for so long, the developers quit working on it in favor of this more ambitious idealized solution. This new branch of OpenWrt took a long, long time to hash out, but now its almost ready.
The ever-popular NVRAM configuration storage system is no longer utilized in Kamikaze. It has been replaced with configuration files, many stored in the common format known as 'UCI'. This was done because although an emulated NVRAM storage area to keep tuple based configuration data can be easily implemented on any platform, the OpenWrt developers felt it wasn't structured enough for their tastes. So, out the window it went.
To make the webif work with Kamikaze we therefore have to work with this new configuration system. The good news is our webif already supports UCI. Some pages, like the QoS page, use the UCI system entirely.
Yes, you can use X-Wrt in whatever way you like, providing you do not violate the terms of the GPL license agreement. We can even help you to rebrand the webif and tweak it to suit your needs. Email us to inquire about webif related contract work.
We always need developers, testers, documentation writers, translators, and support personnel. Our project is truly OPEN and FREE. Anyone can come join our project.
If you would like to get write access to our repository, just create an account at www.berlios.de and email firstname.lastname@example.org or contact one of our other developers on the irc channel (#x-wrt / freenode). We do not make anyone pass an 'entrance exam', though we do like for people to supply a patch of some sort just to prove that you are serious.
A listing of some of the needs we have are:
There are some things you can help us with if you choose. When a person makes a donation, that donation is cataloged and made available to whichever developer is in the most need of it at the time. We do have a public list of donators (or at least will, whenever we get some donations).
To prevent troubles with where money should go, we don't accept project-wide monetary donations. However, some developers do accept direct donations to them. We suggest you check the Berlios roster of developers of this project and develop to whichever people you choose. Also, if you want to see a particular feature developed, perhaps donating to a developer will encourage him or her to pursue that feature more quickly than he or she would have otherwise done.