The current stable version Barrier Breaker 14.07 was released on October 2nd, 2014. It is based on
r42625. See http://wiki.openwrt.org/doc/barrier.breaker
- Images download
The 12.09 "Attitude Adjustment" version has been released on 25 April 2013 -
it marks the previous stable version of OpenWrt. It is based on
- Images (Downloads)
The general method for picking the right image is visiting the Table of Hardware, then matching the "Platform & Frequency" of your device with the image you're downloading. Sometimes, the "Status" column will have additional information for your device, such as building its image or device-specific installation instructions.
If there isn't a pre-built image for your device, follow the Building OpenWrt instructions to build a custom image.
Any bugs in the firmware should be reported via the ticket system. Before reporting a new bug please first search for similar bugs.
The development branch (trunk), code named Chaos Calmer, contains bleeding edge source code for OpenWrt.
|The development branch can contain experimental code that is under active development and should not be used for production environments. Bleeding edge OpenWrt supports additional hardware; however, it's considered unstable, and sometimes won't compile.|
Bleeding edge can be built from sources:
Alternatively, pre-built snapshots are available. The so-called buildbots are automated machines that run build scripts around the clock to keep recent snapshots available for install.
|Prebuilt trunk images do not come with any web interface or GUI. You will need to be comfortable using a command line and remote shell to install one yourself: LuCI Essentials|
The bots build for most specific build targets (i.e. devices). For more information about the automated build process, see the buildbot page http://buildbot.openwrt.org:8010/. The builds are available in the snapshot directory of the OpenWrt download page:
While the build process is automated and is mostly functioning, it's highly advisable that you check the dates on the files before downloading them to prevent installing an outdated version.
If opkg is complaining that the packages list is too old, it is possible that the last few buildbot runs have failed for your platform and the packages are already a few days old.
Buildbot also reports which packages fail to build, so that developers get feedback on possible errors. So when wondering why a package is not currently available in trunk, you could also check the "broken packages" list for your platform. http://buildbot.openwrt.org:8010/broken_packages/
E.g. for ar71xx: http://buildbot.openwrt.org:8010/broken_packages/ar71xx/
Some forum members provide custom OpenWrt Images. Visit OpenWrt Community Releases for more.
Please visit the version history page for an overview of previous releases.
Please see the notes and explanations here: file naming
about/latest.txt · Last modified: 2014/10/02 23:14 by hnyman