What is OpenWrt?

OpenWrt is described as a Linux distribution for embedded devices.

Instead of trying to create a single, static firmware, OpenWrt provides a fully writable filesystem with package management. This frees you from the application selection and configuration provided by the vendor and allows you to customize the device through the use of packages to suit any application. For developer, OpenWrt is the framework to build an application without having to build a complete firmware around it; for users this means the ability for full customization, to use the device in ways never envisioned.

> Supported Devices


OpenWrt LEDE merge

The OpenWrt and the LEDE project are happily announcing the unification
of both projects under the OpenWrt name.

After long and sometimes slowly moving discussions about the specifics
of the re-merge, with multiple similar proposals but little subsequent
action, we're happy to announce that both projects are about to execute
the final steps of the merger.

The new, unified OpenWrt project will be governed under the rules
established by the LEDE project, which can be found at
https://lede-project.org/rules . Active members of both the former LEDE
and OpenWrt projects will continue working on the unified OpenWrt.

LEDE's spinoff and subsequent re-merge into OpenWrt will not alter the
overall technical direction taken by the unified project. We will
continue to work on improving stability and release maintenance while
aiming for frequent minor releases to address critical bugs and security
issues like we did with LEDE 17.01 and its four point releases until now.

Old pre-15.05 OpenWrt CC releases will not be supported by the merged
project anymore, leaving these releases without any future security or
bug fixes. The OpenWrt CC 15.05 release series will receive a limited
amount of security and bug fixes, but is not yet fully integrated in our
release automation, so binary releases are lacking behind for now.

The LEDE 17.01 release will continue to get full security and bug fix
support for both source code and binary releases.
We are planning a new major release under the new name in the next few

The merged project will use the code base of the former LEDE project.
OpenWrt specific patches not present in the LEDE repository but meeting
LEDEs code quality requirements got integrated into the new tree. The
source code is hosted at
https://git.openwrt.org/?p=openwrt/open … ;a=summary with a
continuously synchronized Github mirror hosted at
https://github.com/openwrt/openwrt . We accept patches sent to our
mailing list via openwrt at lists.infradead.org (is still being setup) or
Github pull requests to https://github.com/openwrt/openwrt .

Yet open pull requests to both the old OpenWrt and LEDE repositories
will be closed after a 30 day grace period. We encourage people to open
new pull requests at the new repository or re-send still unmerged patches.

The remerged OpenWrt project is legally represented by the Software in
the Public Interest (SPI) - an US 501(c)(3) non-profit organization.
(see https://www.spi-inc.org/projects/openwrt/ ) The SPI is managing our
OpenWrt trademark, handling our donations and helping us with legal

The original OpenWrt codebase has been archived for future reference and
is hosted at https://github.com/openwrt/archive .

The bug tracker is available at https://bugs.openwrt.org with previously
reported LEDE project issues migrated to it.

Old pre-15.05 OpenWrt CC releases, which are not supported any more, can
be found at http://archive.openwrt.org .

Infrastructure currently available under the lede-project.org domain
will be moved to corresponding openwrt.org subdomains and redirects will
be put in place where appropriate.

The old OpenWrt buildbot infrastructure will be shut down and its
compute resources integrated with the existing LEDE infrastructure in
order to maintain build coverage of current and future releases.

The merger of the OpenWrt and LEDE forums and wikis is not yet fully
decided, so all portals will continue to be available under their
respective domains until a definite consensus is reached.

OpenWrt project


OpenWrt Summit 2016

To help encourage the growth and strength of OpenWrt, LEDE and the broader ecosystem, the OpenWrt Summit Committee is organizing the second OpenWrt Summit. Co-located with ELCE and OpenIoT in Berlin, Germany on October 13, the OpenWrt Summit is the only annual event focusing exclusively on OpenWrt. Free for all to attend, OpenWrt Summit does not require an ELCE/OpenIoT ticket.

Anyone interested in OpenWrt, LEDE or other related projects is invited and welcome.

As a community centered conference, we invite users, developers, employees of companies who use OpenWrt and anyone interested in OpenWrt or LEDE to submit a speaking/session proposal for the OpenWrt Summit.

Suggested topics include:

* Introductory topics (What is OpenWrt/LEDE? How to build? How to install? How to build packages?)
* Hardware (Adding support for hardware you created or bought, contributing back to the core)
* OpenWrt/LEDE derivatives (Best practices, staying close to core)
* Unique and complex usage scenarios
* Security (Containers, jails, etc)
* Culture (Encouraging new contributors, documentation, advocacy)
* Internet of Things/Internet of Everything
* Future of OpenWrt, LEDE and related projects

We also welcome any other session topic related to OpenWrt and LEDE. Again, we encourage everyone interested to submit a session proposal for the OpenWrt Summit. Proposals should be submitted by August 19. Financial assistance will be available for speakers who require it.

To learn more and to submit your proposal, please visit: http://openwrtsummit.org . Also, if you're interested in learning more about the conference, including lodging information, please visit this URL as well.


Chaos Calmer 15.05.1

The OpenWrt developers are proud to announce the minor fix release of OpenWrt Chaos Calmer.

   _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 CHAOS CALMER (15.05.1)
  * 1 1/2 oz Gin            Shake with a glassful
  * 1/4 oz Triple Sec       of broken ice and pour
  * 3/4 oz Lime Juice       unstrained into a goblet.
  * 1 1/2 oz Orange Juice
  * 1 tsp. Grenadine Syrup


** Highlights since Chaos Calmer 15.05 **

* Linux kernel updated to version 3.18.23
* Security fixes:
    - kernel: fix keyring reference leak (CVE-2016-0728)
    - openssl updated to 1.0.2f
    - hostapd security fixes
    - samba36 (CVE patches from 2015-12-16)
* Update of netifd, procd, uci, rpcd, ubox & uhttpd
* Driver updates
    - ledtrig-netdev: fix possible deadlock
    - bcm47xxpart: fix bcm53xx booting on NAND with badblocks
    - brcmfmac: fix getting/setting TX power, add stations dumping and support beamforming
    - 8139c: backport v4.3 fixes
    - backport spi layer fixes from v4.2+
    - solos-pci: increase headroom on RX
    - xrx200-net: fix port mirroring issues
    - update mac80211 (adding mt76)
* Support for new devices:
    - Linksys WRT1900ACS (mvebu)
    - D-LINK DIR-615 rev. Ix (ar71xx)
    - LinkIt Smart7688 (ramips)
    - Gainstrong MiniBox v1.0 (ar71xx)
    - ZBT WG2626 (ramips)
    - TP-LINK TL-WR841N/ND v10 (ar71xx)
    - TL-WR741ND v5 (ar71xx)
    - WR740N v5.0 (ar71xx)
    - TP-LINK TL-WR941ND v6 international version (ar71xx)
* Improved support for existing devices:
    - Netgear R8000: USB power and CPU speed
    - RapsberryPi: Add sysupgrade support
* Kernel fixes
    - ramoverlay
    - multicast-to-unicast
    - ip6_fragment related skb_leak
* Package fixes
    - igmpproxy: spurious restart issues

Have fun!
    The OpenWrt developer team


Wireless Battle of the Mesh v9

OpenWrt.org endorses the Battle of the Mesh v9


The "Wireless Battle of the Mesh" is an event that aims to bring together people from across the globe to test the performance of different routing protocols for ad-hoc networks, like Babel, B.A.T.M.A.N, BMX, OLSR, and 802.11s.

Many developers and community networkers will join the event to hack, test, discuss, explain and learn.

If you are interested in dynamic routing protocols or wireless community networks you can't miss this event!

The battlemesh is free of charge and open for all, every year we strive to keep participation costs low by negotiating deals for accommodation and food.

This year the event will take place from Sunday 1st to Saturday 7th of May 2016 in Porto, Portugal. The event is locally organized by INESC TEC, Porto, Portugal. INESC TEC stands for Institute for Systems and Computer Engineering, Technology and Science and is a private non-profit research & development institute located on the campus of the Faculty of Engineering of the University of Porto (Portugal).

OpenWrt.org endorses and supports the Battle of the Mesh v9 because of the efforts made by its community to advance the field of wireless mesh networking and foster the development of grass-roots community networks.

Some OpenWrt developers will attend the event and be ready to answer your questions!

If you are interested in coming join the event's Mailing List to stay up to date with the latest news.


Server status

Recently we got some problems with our main hosting server. RAID controller wasn't able to keep up with the load resulting in many services being unavailable quite often. We decided to switch to a new server which unfortunately took about 3 weeks to order & get a proper hardware.

For about a week we have our main services running on the new machine:

  1. Our main site

  2. Forum


  4. SVN

All services are back, buildbot is running again as well.


Chaos Calmer 15.05

The OpenWrt developers are proud to announce the final release of OpenWrt Chaos Calmer.

   _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
  * 1 1/2 oz Gin            Shake with a glassful
  * 1/4 oz Triple Sec       of broken ice and pour
  * 3/4 oz Lime Juice       unstrained into a goblet.
  * 1 1/2 oz Orange Juice
  * 1 tsp. Grenadine Syrup


** Highlights since Barrier Breaker **

* Linux kernel updated to version 3.18
* Improved Security Features
    - Rewritten package signing architecture based on ed25519
    - Added support for jails
    - Added support for hardened builds
* Improved Networking Support
    - Added or improved support for lots of 3G/4G modems (MBIM, QMI, NCM, ...)
    - Added support for 464XLAT (CLAT) [RFC 6877 + RFC 7050]
    - Netfilter performance enhancements (conntrack route cache)
    - Improved support for self-managing networks [draft-ietf-homenet-hncp]
    - Better multi-core support for the network stack
    - Improved support for MAP-E, MAP-T and LW4over6 IPv4 transitioning technologies
        [draft-ietf-softwire-map, -map-t, -map-dhcp, -lw4over6]
    - Improved network auto-setup capable of detecting and bootstrapping IPv4-only,
      6rd, Dual-Stack, IPv6-only, DS-Lite, LW4over6, MAP-E, MAP-T, 464XLAT
      and combinations without explicit configuration [based on RFC 7084]
    - Added support for Smart Queue Management (SQM) QoS, AQM and Traffic Shaping
    - Improved support for DNSSEC
* Platform and Driver Support
    - Added support for feeds of externally maintained targets
    - New mt7621 subtarget for Mediatek 11ac SoC
    - New mt76 mac80211 based wifi driver for MTK 11ac cores.
    - New mwlwifi mac80211 based wifi driver for the Marvell 88W8864
    - New bcm53xx target for Broadcom ARM BCM47xx/53xx devices
    - New mxs target for Freescale i.MX23/28 family and various boards
    - New sunxi target for AllWinner A10/A13/A20 family and various boards
    - brcm2708: support for Raspberry Pi 2
    - brcm63xx: support for BCM6318 and BCM63268 family
    - brcm63xx: improved fallback sprom support with bcma support

** Improvements since RC 3 **
* Updated 3.18 to 3.18.20
* Security update of openssl to 1.0.2d
* Security update of curl
* brcmfmac: many BCM43602 related fixes
* ar71xx: support more devices
* brcm47xx/bcm53xx: support any NVRAM size
* bcm53xx: basic Netgear R7000 support & R8000 image

** Improvements since RC 2 **
* brcmfmac: support for BCM43602
* mt76: updated version with new firmware support, TX & DMA fixes
* Updated 3.18 to 3.18.17
* Fixed image builder generation
* Various security updates (e.g. openssl, curl)
* Minor fixes

** Improvements since RC 1 **
* Fixed broken ImageBuilders for most targets
* Updated 3.18 to 3.18.14
* Fixed broken IPv6 downstream DHCPv6-PD and onlink-route handling
* Images (special format) for Asus brcm47xx and bcm53xx devices
* Improved stability of sysupgrade on brcm47xx and bcm53xx
* Added HTTPS enforcement option to uhttpd
* Fixed umask issue
* Added support for a few new boards

And lots and lots of other advancements...
As always a big thank you goes to all our active package maintainers, testers, supporters and documenters.

Have fun!
    The OpenWrt developer team