LEDE

OpenWrt

OpenWrt

Embedded Linux distribution

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,[4] and BusyBox. All components have been optimized to be small enough to fit into the limited storage and memory available in home routers.

Quick Facts Developer, OS family ...

OpenWrt is configured using a command-line interface (ash shell) or a web interface (LuCI). There are about 8000 optional software packages available for installation via the opkg package management system.

OpenWrt can run on various types of devices, including CPE routers, residential gateways, smartphones, pocket computers (e.g., Ben NanoNote). It is also possible to run OpenWrt on personal computers and laptops.

History

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]

Releases

More information Version (Code name), General availability ...

LEDE

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

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

More information Version, Release Date ...

Features

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.[62][63] 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.[64] 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:

Development

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.[67][68]

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.[67][69]

OpenWrt Buildroot provides the following features:[67][69]

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

Hardware compatibility

OpenWrt runs many different routers and includes a table of compatible hardware on its website.[71] In its buyer's guide,[72] 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.[73]

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.
  • 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[74]

Derivative projects

See also: List of router firmware projects
  • AREDN The Amateur Radio Emergency Data Network uses a firmware based on OpenWrt: GitHub Project
  • 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.[75] 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.[76]
  • 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
  • libreCMC – OpenWrt-based distribution which excludes non-free software or binary blobs, endorsed by the Free Software Foundation[77]
  • Linino – OpenWrt-based distribution for the MIPS-based Arduino Yùn: GitHub Project
  • Midge Linux – an OpenWrt-based distribution for devices based on Infineon Technologies ADM-5120 SoCs, such as Edimax BR-6104K and BR-6104KP.
  • OpenMPTCProuter – aggregation of multiple Internet connections using Multipath TCP
  • OpenSAN – iSCSI target Storage Area Network realization.
  • 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.[78]
  • 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
  • Diverse grassroots projects for wireless community networks, including Freifunk, Libre-Mesh and qMp
  • Some TP-Link, Xiaomi, ZyXEL and D-Link router firmwares are derived from OpenWrt[79][80]
  • 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.[81]
  • 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.[82]

See also

References

  1. [1]
    "OpenWrt 23.05.3 - Service Release - 25. March 2024". March 25, 2024.
  2. [2]
    "LuCI Translation Portal on Weblate". January 22, 2021. Retrieved January 22, 2021.
  3. [3]
    "git.openwrt.org Git - openwrt/openwrt.git/blob - target/Config.in". git.openwrt.org. October 24, 2017. Archived from the original on November 4, 2019. Retrieved July 2, 2018.
  4. [4]
    Fietkau, Felix (June 16, 2015). "OpenWrt switches to musl by default". Archived from the original on June 17, 2015. Retrieved June 16, 2015.
  5. [5]
    Miklas, Andrew (June 7, 2003). "Linksys WRT54G and the GPL". Linux kernel mailing list (Mailing list). Retrieved July 5, 2018.
  6. [6]
    Weiss, Aaron (November 8, 2005). "The Open Source WRT54G Story". Wi-Fi Planet. Retrieved July 5, 2018.
  7. [7]
    "Linksys Releases GPLed Code for WRT54G". Slashdot. July 6, 2003. Retrieved July 5, 2018.
  8. [8]
    Willis, Nathan (May 11, 2016). "LEDE and OpenWrt". LWN.net. Retrieved August 31, 2017.
  9. [9]
    Sharwood, Simon (May 10, 2017). "OpenWRT and LEDE agree on Linux-for-routers peace plan". theregister.co.uk. Retrieved August 31, 2017.
  10. [10]
    Wich, Jo-Philipp (January 2, 2018). "Announcing the OpenWrt/LEDE merge". LEDE Project Forum. Retrieved January 10, 2018.
  11. [11]
    "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 "
  12. [12]
    "OpenWrt version history". October 16, 2023.
  13. [13]
    "Release Builds". October 19, 2023.
  14. [14]
    "Security - Support status". December 28, 2015. Retrieved January 9, 2024.
  15. [15]
    "Whiterussian 0.9 / Kamikaze snapshots". February 5, 2007.
  16. [16]
    "WHITE RUSSIAN 0.9". February 5, 2007.
  17. [17]
    "Kamikaze 7.06". June 2, 2007.
  18. [18]
    "Kamikaze 7.07". July 26, 2007.
  19. [19]
    "Kamikaze 7.09". September 30, 2007.
  20. [20]
    "Kamikaze 8.09". February 19, 2009.
  21. [21]
    "Kamikaze 8.09.1". June 3, 2009.
  22. [22]
    "Kamikaze 8.09.2". January 10, 2010.
  23. [23]
    "Backfire 10.03". April 7, 2010.
  24. [24]
    "Backfire 10.03.1". December 21, 2011.
  25. [25]
    "Attitude Adjustment". April 25, 2013.
  26. [26]
    "Barrier Breaker". October 2, 2014.
  27. [27]
    "OpenWrt Project: Freescale i.MX". openwrt.org. July 16, 2013. Retrieved July 16, 2018.
  28. [28]
    "Chaos Calmer". September 11, 2015.
  29. [29]
    "OpenWrt 15.05.1 "Chaos Calmer"". March 16, 2016.
  30. [30]
    "LEDE 17.01 "Reboot"". June 29, 2019.
  31. [31]
    "[OpenWrt-Devel] OpenWrt switches to musl by default". June 16, 2015. Retrieved June 27, 2015.
  32. [32]
    "OpenWrt/LEDE 17.01.7 - Seventh Service Release - June 2019". June 20, 2019.
  33. [33]
    "OpenWrt 17.01.7 - date of release?". July 20, 2019. Retrieved January 11, 2024.
  34. [34]
    "OpenWrt 18.06". July 31, 2018.
  35. [35]
    "OpenWrt 19.07". January 6, 2020.
  36. [36]
    Mehrtens, Hauke (January 6, 2020). "OpenWrt 19.07.0 - First Stable Release - 6 January 2020". OpenWrt Wiki.
  37. [37]
    Man, Low Kah (February 1, 2020). "Speedtest OpenWRT with flow offloading". Leow Kah Man - Tech Blog.
  38. [38]
    "OpenWrt 21.02". September 4, 2021.
  39. [39]
    Mehrtens, Hauke (September 4, 2021). "OpenWrt 21.02.0 - First Stable Release - 4 September 2021". OpenWrt Wiki.
  40. [40]
    "OpenWrt 22.03". September 6, 2022.
  41. [41]
    "OpenWrt 21.03.0 - First Stable Release - 6 September 2022". OpenWrt Wiki. September 15, 2022.
  42. [42]
    "OpenWrt 23.05". October 13, 2023.
  43. [43]
    Mehrtens, Hauke (October 11, 2023). "OpenWrt 23.05.0 - First Stable Release - 13 October 2023". OpenWrt Wiki. Retrieved October 24, 2023.
  44. [44]
    "Lua Configuration Interface: /modules/luci-base/po". May 10, 2017. Archived from the original on September 26, 2017. Retrieved May 14, 2017.
  45. [45]
    "LEDE Source Repository: /target/Config.in". March 30, 2017. Archived from the original on September 26, 2017. Retrieved May 14, 2017.
  46. [46]
    Larabel, Michael (May 14, 2017). "OpenWRT Gets Forked By Some Of Its Own Developers As LEDE Project". Phoronix. Retrieved May 3, 2016.
  47. [47]
    Willis, Nathan (May 11, 2016). "LEDE and OpenWrt". LWN.net. Retrieved May 14, 2017.
  48. [48]
    Chirgwin, Richard (May 5, 2016). "Router hackers reach for the fork: LEDE splits from OpenWRT". The Register. Retrieved May 14, 2017.
  49. [49]
    Grüner, Sebastian (May 5, 2016). "OpenWRT-Kernentwickler starten eigenen Fork". golem.de (in German). Retrieved May 14, 2017.
  50. [50]
    Ahlers, Ernst (May 4, 2016). "Router-Firmware: LEDE als offenere OpenWRT-Alternative" (in German). Heise Online. Retrieved May 14, 2017.
  51. [51]
    Sharwood, Simon (May 10, 2017). "OpenWRT and LEDE agree on Linux-for-routers peace plan". theregister.co.uk. Retrieved August 31, 2017.
  52. [52]
    Mehrtens, Hauke (June 26, 2017). "LEDE call for vote on remerge proposal V3". LEDE-DEV mailing list. Archived from the original on September 1, 2017. Retrieved August 31, 2017.
  53. [53]
    Wich, Jo-Philipp (January 2, 2018). "Announcing the OpenWrt/LEDE merge". LEDE Project Forum. Retrieved January 10, 2018.
  54. [54]
    "OpenWrt Project: OpenWrt 18.06". openwrt.org. May 18, 2018. Retrieved November 2, 2018.
  55. [55]
    "LEDE Project: LEDE 17.01.0 - First Stable Release - February 2017". Lede-project.org. February 22, 2017. Retrieved October 20, 2017.
  56. [56]
    "LEDE Project: LEDE 17.01.1 - First Service Release - April 2017". Lede-project.org. April 19, 2017. Retrieved October 20, 2017.
  57. [57]
    "LEDE Project: LEDE 17.01.2 - Second Service Release - June 2017". Lede-project.org. June 12, 2017. Retrieved October 20, 2017.
  58. [58]
    "LEDE Project: LEDE 17.01.3 - Third Service Release - October 2017". Lede-project.org. October 3, 2017. Retrieved October 20, 2017.
  59. [59]
    "LEDE Project: LEDE 17.01.4 - Fourth Service Release - October 2017". Lede-project.org. October 18, 2017. Retrieved October 20, 2017.
  60. [60]
    "OpenWrt/LEDE 17.01.5 - Fifth Service Release - July 2018". Lede-project.org. July 15, 2018. Retrieved July 20, 2018.
  61. [61]
    "OpenWrt/LEDE 17.01.6 - Sixth Service Release - September 2018". Lede-project.org. September 2, 2018. Retrieved November 2, 2018.
  62. [62]
    "The OpenWrt Flash Layout". OpenWrt Project. January 18, 2010. Retrieved July 7, 2018.
  63. [63]
    Corbet, Jonathan (June 15, 2011). "Debating overlayfs". LWN.net. Retrieved July 7, 2018.
  64. [64]
    "The UCI System". OpenWrt Project. September 16, 2009. Retrieved July 8, 2018.
  65. [65]
    "29C3: ISP's black box". events.ccc.de. January 19, 2013.
  66. [66]
    "kernel: add codel and fq_codel to generic 3.3 patch set". dev.archive.openwrt.org. May 16, 2012. Retrieved July 2, 2018.
  67. [67]
    "OpenWrt Buildroot – About". openwrt.org. Retrieved October 21, 2013.
  68. [68]
    "OpenWrt Buildroot - Usage and documentation". openwrt.org. January 8, 2006. Archived from the original on October 21, 2013. Retrieved October 21, 2013.
  69. [69]
    Tao Jin (February 13, 2012). "OpenWrt Development Guide" (PDF). Wireless Networks Lab, CCIS, NEU. Retrieved October 21, 2013.
  70. [70]
    "Creating packages". openwrt.org. Retrieved October 21, 2013.
  71. [71]
    "OpenWrt Project: Table of Hardware". openwrt.org. January 19, 2016. Retrieved July 2, 2018.
  72. [72]
    "OpenWrt Project: Buyers' Guide". openwrt.org. December 29, 2010. Retrieved July 2, 2018.
  73. [73]
    "4/32 warning". OpenWrt. September 28, 2020.
  74. [74]
    "Simet Box". Retrieved September 14, 2017.
  75. [75]
    "ANNOUNCE: debloat-testing kernel git tree". LWN.net. Retrieved February 13, 2014.
  76. [76]
    "Cerowrt Wiki - Bufferbloat.net". www.bufferbloat.net.
  77. [77]
    "Free Software Foundation adds libreCMC to its list of endorsed distributions". FSF.org. September 4, 2014. Retrieved December 21, 2014.
  78. [78]
    ""closing time" message from author on PacketProtector forum". Archived from the original on April 21, 2013.
  79. [79]
    "GPL Code Center | TP-Link". www.tp-link.com.
  80. [80]
    "GPL Source Code Support; D-Link". tsd.dlink.com.tw.
  81. [81]
    "FriendlyElec Downloads".
  82. [82]
    "Ansuel GUI". Ansuel Github. August 16, 2017. Retrieved April 16, 2022.
Wikimedia Commons has media related to OpenWrt.
Share this article:

This article uses material from the Wikipedia article LEDE, and is written by contributors. Text is available under a CC BY-SA 4.0 International License; additional terms may apply. Images, videos and audio are available under their respective licenses.