OpenWrt

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.[5] Under the terms of that license, Linksys was required to make the source code of its modified version available under the same license,[6][7] 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.[8] The fork was dubbed Linux Embedded Development Environment (LEDE). The schism was reconciled a year later.[9] Following the remerger, announced in January 2018,[10] 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.[11]

LEDE

This section is about the wireless network router operating system. For other uses, see Lede (disambiguation).

LEDE

Login banner
Developer	LEDE Project
OS family	Unix-like
Working state	Merged with OpenWrt
Source model	Open source
Initial release	May 2016 (2016-05)
Repository	git.openwrt.org/openwrt/openwrt.git
Available in	26 languages[51]
Update method	opkg
Package manager	opkg
Platforms	23 platforms using the following Instruction sets: AVR32, ARM, CRIS, m68k, MIPS, PowerPC, SPARC, SuperH, Ubicom32, x86, x86-64[52]
Kernel type	Monolithic (Linux)
Userland	BusyBox, GNU
Default user interface	CLI, WebUIs
License	Free software (GPL and other licenses)
Official website	lede-project.org

The Linux Embedded Development Environment (LEDE) project was a fork of the OpenWrt project and shared many of the same goals.[53][54][55][56][57] It was created in May 2016 by a group of core OpenWrt contributors due to disagreements on OpenWrt internal processes.[54] The schism was nominally reconciled a year later in May 2017 pending approval of the LEDE developers.[58] 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,[59] and formally announced in January 2018.[60] The merging process was completed before the OpenWrt 18.06 release.[61]

Version	Release Date	Revision Number[62]	Notes
17.01.0	22 February 2017	r3205	First stable release[63]
17.01.1	19 April 2017	r3316	Kernel 4.4.61, bug fixes and enhancements[64]
17.01.2	12 June 2017	r3435	Kernel 4.4.71, security fixes[65]
17.01.3	3 October 2017	r3534	Kernel 4.4.89, security fixes[66]
17.01.4	18 October 2017	r3560	Kernel 4.4.92, security fixes (KRACK, as far as addressable by server side fixes)[67]
17.01.5	18 July 2018	r3919	Kernel 4.4.140, security fixes [68]
17.01.6	3 September 2018	r3979	Kernel 4.4.153, security fixes [69]

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.[70][71] 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.[72] 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.

OpenWrt provides exhaustive possibilities to configure common network-related features, like IPv4, IPv6, DNS, DHCP, routing, firewall, NAT, port forwarding and WPA.

Other features include:

• 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.
• Mesh networking through B.A.T.M.A.N., OLSR and IEEE 802.11s-capabilities of the WNIC drivers and other ad hoc mesh routing protocols that have been implemented within Linux.
• Wireless functionality, e.g. make the device act as a wireless repeater, a wireless access point, a wireless bridge, a captive portal, or a combination of these with e.g. ChilliSpot, WiFiDog Captive Portal, etc.
• Wireless security: Packet injection, e.g. Airpwn, lorcon, e.a.
• Dynamically-configured port forwarding protocols PCP, NAT-PMP, and UPnP IGD through MiniUPnPd
• Port knocking
• TR-069 (CWMP) client[73]
• IPS via Snort
• Active queue management (AQM) through the network scheduler of the Linux kernel, with many available queuing disciplines. CoDel has been backported to Kernel 3.3.[74] This encapsulates Traffic shaping to ensure fair distribution of bandwidth among multiple users and quality of service (QoS) for simultaneous use of applications such as VoIP, online gaming, and streaming media without experiencing the negative impacts of link saturation.
• Load balancing for use with multiple ISPs using source-specific routing
• IP tunneling (GRE, OpenVPN, pseudowire, WireGuard, etc.)
• Extensible realtime network monitoring and statistics through e.g. RRDtool, Collectd, Nagios, Munin lite, Zabbix, etc.
• Dynamic DNS services to maintain a fixed domain name with an ISP that does not provide a static IP address
• OpenWrt supports any hardware that has Linux support; devices that can be connected (e.g. over USB) include
  • Printers
  • Mobile broadband modems
  • Webcams
  • Sound cards
• Notable software packages to use the hardware support are
  • File sharing via SAMBA, (Windows-compatible), NFS, FTP, SFTP. Printer sharing over the print server CUPS (spooling) or p910nd (non-spooling)
  • PulseAudio, Music Player Daemon, Audio/Video streaming via DLNA/UPnP AV standards, iTunes (DAAP) server
  • Asterisk (PBX)
  • MQ Telemetry Transport through Mosquitto

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-compilation toolchain.[75][76]

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.[75][77]

OpenWrt Buildroot provides the following features:[75][77]

• 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.)
• Provides an abstraction for autotools (automake, autoconf), CMake and SCons
• 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.[78]

OpenWrt runs many different routers and includes a table of compatible hardware on its website.[79] In its buyer's guide,[80] 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. OpenWrt also recommends choosing a device with a minimum of 8 MB of flash and 64 MB of RAM, preferably higher amounts.[81]

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.
• Bufferbloat.net (Cerowrt)
• Freifunk and other mesh network communities
• IETF IPv6 integration projects HIPnet and HomeNet are OpenWrt-based
• prplOS, carrier-grade framework designed to power ISPs routers and gateways made by Prpl Foundation
• SIMET Box, developed by NIC.br, is OpenWrt-based[82]

• List of router firmware projects
• Prpl Foundation

Wikimedia Commons has media related to OpenWrt.

• OpenWrt Firmware Selector
• OpenWrt Downloads
• OpenWrt on GitHub
• OpenWrt Mailing Lists
• LuCI project
• OpenWrt Summit
• GPL Code Center at Linksys