OpenWrt (from open wireless router) is an open-source project for embedded operating systems based on Linux, primarily used on embedded devices to route network traffic. The main components are Linux, util-linux, musl,[5] and BusyBox. All components have been optimized to be small enough to fit into the limited storage and memory available in home routers.
The OpenWrt project was started in 2004 after Linksys had built the firmware for their WRT54G series of wireless routers with code licensed under the GNU General Public License.[6] Under the terms of that license, Linksys was required to make the source code of its modified version available under the same license,[7][8] which enabled independent developers to create derivative versions. Support was originally limited to the WRT54G series, but has since been expanded to include many other routers and devices from many different manufacturers.
Using this code as a base and later as a reference, developers created a Linux distribution that offers many features not previously found in consumer-level routers. Early on some features required proprietary software. For example, prior to OpenWrt 8.09 (based on Linux 2.6.25 and the b43 kernel module) WLAN for many Broadcom-based routers could only be had via the proprietary wl.o module (and which required Linux 2.4.x).
OpenWrt releases were historically named after cocktails, such as White Russian, Kamikaze, Backfire, Attitude Adjustment, Barrier Breaker and Chaos Calmer, and their recipes were included in the message of the day (motd) displayed after logging in using the command-line interface.
In May 2016, OpenWrt was forked by a group of core OpenWrt contributors due to disagreements on internal process.[9] The fork was dubbed Linux Embedded Development Environment (LEDE). The schism was reconciled a year later.[10] Following the remerger, announced in January 2018,[11] the OpenWrt branding is preserved, with many of the LEDE processes and rules used. The LEDE project name was used for v17.01, with development versions of 18.01 branded OpenWrt, dropping the original cocktail based naming scheme.[12]
There were only release notes for "OpenWrt/LEDE 17.01.7 - Seventh Service Release - June 2019" with a code revision "rTODO-2252731af4".[33] The official announcement of "OpenWrt/LEDE v17.01.7 service release" was never made in the OpenWrt Forum due to GPG signing certs issues.[34]
Firewall4 based on nftables, many new devices added, more targets converted to DSA, dark mode in LuCI, year 2038 problem handled, core components updated.[42]
The Linux Embedded Development Environment (LEDE) project was a fork of the OpenWrt project and shared many of the same goals.[47][48][49][50][51] It was created in May 2016 by a group of core OpenWrt contributors due to disagreements on OpenWrt internal processes.[48] The schism was nominally reconciled a year later in May 2017 pending approval of the LEDE developers.[52] The remerger preserves the OpenWrt branding, but uses many of the LEDE processes and rules. The remerge proposal vote was passed by LEDE developers in June 2017,[53] and formally announced in January 2018.[54] The merging process was completed before the OpenWrt 18.06 release.[55]
OpenWrt features a writeable root file system, enabling users to modify any file and easily install additional software. This is in contrast with other firmware based on read-only file systems which don't allow modifying installed software without rebuilding and flashing a complete firmware image. This is accomplished by overlaying a read-only compressed SquashFS file system with a writeable JFFS2 file system using overlayfs.[63][64] Additional software can be installed with the opkg package manager and the package repository contains approximately 8000 packages (by 2022).
LuCI
OpenWrt can be configured through either a command-line interface or a web interface called LuCI. OpenWrt provides set of scripts called UCI (unified configuration interface) to unify and simplify configuration through the command-line interface.[65] Additional web interfaces, such as Gargoyle, are also available.
OpenWrt provides regular bug fixes and security updates even for devices that are no longer supported by their manufacturers.
Extensible configuration of the entire hardware drivers, e.g. built-in network switches and their VLAN-capabilities, WNICs, DSL modems, FX, available hardware buttons, etc.
OpenWrt's development environment and build system, known together as OpenWrt Buildroot, are based on a heavily modified Buildroot system. OpenWrt Buildroot is a set of Makefiles and patches that automates the process of building a complete Linux-based OpenWrt system for an embedded device, by building and using an appropriate cross-compilationtoolchain.[68][69]
Embedded devices usually use a different processor than the one found in host computers used for building their OpenWrt system images, requiring a cross-compilation toolchain. Such a compilation toolchain runs on a host system but generates code for a targeted embedded device and its processor's instruction set architecture (ISA). For example, if a host system uses x86 and a target system uses MIPS32, the regular compilation toolchain of the host runs on x86 and generates code for x86 architecture, while the cross-compilation toolchain runs on x86 and generates code for the MIPS32 architecture. OpenWrt Buildroot automates this whole process to work on the instruction set architectures of most embedded devices and host systems.[68][70]
OpenWrt Buildroot provides the following features:[68][70]
Makes it easy to port software across architectures
Uses kconfig (Linux kernel menuconfig) for the configuration of all options
Provides an integrated cross-compiler toolchain (gcc, ld, uClibc etc.)
Handles standard OpenWrt image build workflow: downloading, patching, configuration, compilation and packaging
Provides a number of common fixes for known badly behaving packages
Besides building system images, OpenWrt development environment also provides a mechanism for simplified cross-platform building of OpenWrt software packages. Source code for each software package is required to provide a Makefile-like set of building instructions, and an optional set of patches for bug fixes or footprint optimizations.[71]
Hardware compatibility
OpenWrt runs many different routers and includes a table of compatible hardware on its website.[72] In its buyer's guide,[73] it notes that users recommend devices equipped with wireless chips from either Qualcomm's Atheros, Ralink (now MediaTek) or any vendor with open source drivers and specifications. It specifically avoids Broadcom chipsets as the feature set is very limited due to having no open drivers. OpenWrt also recommends choosing a device with a minimum of 16 MB of flash and 128 MB of RAM, preferably higher amounts.[74]
Adoption
OpenWrt, especially its Buildroot build system, has been adopted as the structure for other efforts. For example
AltiWi "one-time-fee-only" replacement for Cloudtrax.
CeroWrt – (2011—2014) project to resolve bufferbloat in home networking, support IPv6, integrate DNSSEC, for wired and wireless, to complement the debloat-testing kernel tree and provide a platform for real-world testing of bufferbloat fixes.[76] The CeroWRT project is completely by 2014, when the finalized fixes were merged into OpenWRT. The "Bufferbloat project" behind CeroWRT went on to research new methods such as CAKE.[77]
Coova chilli – OpenWrt-based with focus on wireless hotspots, a fork of chillifire with focus on wireless hotspot management
Flukso – Wireless sensor nodes using an Atheros AR2317 chipset running a patched OpenWrt OS for communication. Sources and hardware schematics available on GitHub.
Fon – OpenWrt-based wireless routers acting as hotspots. Sources and toolchain available on fonosfera.org
Gargoyle – a web interface for OpenWrt with a strong emphasis on usability that later forked into a separate distribution
Gluon – Framework for building OpenWrt-based firmwares fitted for mesh network deployment: GitHub Project
JUCIWRT – a modern distribution using the JUCI webgui that later became an OpenWrt feed instead. The source code for JUCI is available at mkschreder/juci and is still usable by installing openwrt feed found at mkschreder/juci-openwrt-feed
PacketProtector – OpenWrt-based security distribution that includes IDS, IPS, VPN, and web antivirus capabilities. Packages included Snort, Snort-inline, FreeRADIUS, OpenVPN, DansGuardian and ClamAV. These tools were accessible via the old web GUI management interface of OpenWrt, called X-Wrt or webif^2. Project ended on June 7, 2012.[79]
Qualcomm's QCA Software Development Kit (QSDK) which is being used as a development basis by many OEMs is an OpenWrt derivative
RutOS – an operating system for all Teltonika routers, based on OpenWrt. Source code found at GPL - Teltonika Networks Wiki.
SmoothWAN – aggregation of multiple Internet connections and network conditioning using Speedify, Engarde and tinyfecvpn.
Turris Omnia and Turris MOX routers run on an OpenWrt derivative
Ubiquiti's wireless router firmwares are based on OpenWrt
FreeWRT was a Linux distribution that was used in embedded systems such as WLAN devices from Linksys and Asus. Not related to a project (with same name) based on Sveasoft firmware.[citation needed]
Friendly Electronics manufactures the NanoPi series of SoC devices and makes available an OpenWRT derivative OS called FriendlyWRT.[82]
Ansuel's Technicolor Custom GUI a modified management web interface developed on the basis of the official Technicolor for Homeware firmware, which runs a fork of OpenWrt, unlocking Technicolor Modem/Routers.[83]
^"Welcome to the OpenWrt Project (OpenWrt Project)". OpenWrt. January 2018. Retrieved February 16, 2018. As of January 2018, the current Stable OpenWrt release [17.01.4] was built from the LEDE 17.01 source code, and branded with the LEDE project name. Development versions of OpenWrt are currently branded with the OpenWrt name, and have a version number of 18.01 "
