Hubbry Logo
OpenWrtOpenWrtMain
Open search
OpenWrt
Community hub
OpenWrt
logo
7 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
OpenWrt
OpenWrt
OpenWrt
View on Wikipedia
from Wikipedia

OpenWrt
OpenWrt 18.06.1 login screen
DeveloperOpenWrt Project
OS familyLinux (Unix-like)
Working stateCurrent
Source modelOpen source
Initial releaseJanuary 2004; 21 years ago (2004-01)
Latest release24.10.4[1] Edit this on Wikidata / 21 October 2025; 6 days ago (21 October 2025)
Latest preview24.10.0-rc7[2] / 29 January 2025; 8 months ago (2025-01-29)
Repository
Available inEnglish, Chinese, Polish, Portuguese, Punjabi, Spanish, Welsh + 25 partially translated languages[3]
Update methodopkg (up to 24.10 release) apk (snapshot builds)
Package managerAlpine Package Manager (APK) opkg (up to 24.10 release)
Supported platforms50 different platforms using the following Instruction sets: ARC, ARM, m68k, MIPS, PowerPC, SPARC, SuperH, x86, x86-64[4]
Kernel typeMonolithic (Linux)
UserlandBusyBox
Default
user interface		CLI, WebUIs (LuCI)
LicenseFree software (GPL and other licenses)
Official websiteopenwrt.org

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.

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

[edit]

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]


Releases

[edit]
Version (Code name)[13][14] General availability Kernel Latest minor version Latest release date Projected EoL[15] libc Notes
"Stable Release" 2004-01 ? — uClibc Based on Linksys GPL sources for WRT54G and a buildroot from the uClibc project
0.9 (White Russian)[16][17] 2007-02-05 2.4.30 — NVRAM-based, nas, wl. Supported platform: brcm-2.4.
7.06 (Kamikaze)[18] 2007-06-02 2.6.19 7.09[19][20] 2007-09-30 Does not appear Using opkg. Supported platforms: atheros-2.6, au1000-2.6, brcm-2.4, brcm47xx-2.6, ixp4xx-2.6, imagicbox-2.6, rb532-2.6 and x86-2.6.
8.09 (Kamikaze)[21] 2009-02-19 2.6.26 8.09.2[22][23] 2010-01-10 Does not appear New platform: ar71xx.
10.03 (Backfire)[24] 2010-04-07 2.6.32 10.03.1[25] 2011-12-21 Does not appear Supported platforms: adm5120_mips, adm5120_mipsel, ar7, ar71xx, atheros, au1000, avr32, brcm-2.4, brcm47xx, brcm63xx, cobalt, ep80579, ifxmips, ixp4xx, kirkwood, octeon, orion, ppc40x, ppc44x, rb532, rdc, x86 and xburst.
12.09 (Attitude Adjustment)[26] 2013-04-25 3.3 — CoDel (network scheduler) backported from Linux 3.5 to 3.3. New platforms: ramips, bcm2708 (Raspberry Pi) and others.
14.07 (Barrier Breaker)[27] 2014-10-02 3.10 — New platforms: i.MX23, i.MX6.[28]
15.05 (Chaos Calmer)[29] 2015-09-11 3.18 15.05.1[30] 2016-03-16 2016, March nftables (available since Linux kernel 3.12); New platforms: TBA if any
17.01 (Reboot (OpenWrt/LEDE))[31] 2017-02-22 4.4 17.01.7 2019-06-20 2018, September musl[32] 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]
18.06[35] 2018-07-31 4.9 / 4.14 18.06.9 2020-12-09 2020, December
19.07[36] 2020-01-06 4.14 19.07.10 2022-04-20 2022, April WPA3 support.[37] Flow offloading (beta).[38]
21.02[39] 2021-09-04 5.4 21.02.7 2023-05-01 2023, May WPA3, TLS and HTTPS support included by default, initial DSA support, LXC and ujail support [40]
22.03[41] 2022-09-06 5.10 22.03.7 2024-07-25 2024, July 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]
23.05[43] 2023-10-13 5.15 23.05.6 2025-08-20 2025, July New devices added, ipq40xx target converted to DSA, default cryptographic library switched to mbedtls, core components updated.[44]
24.10[45] 2025-02-06 6.6 24.10.4 2025-10-22 2026, February New devices added, ipq806x target converted to DSA, improved support for WiFi6 (802.11ax) and initial support for WiFi7 (802.11be), core components updated.[46]
Legend:   Latest version   Previous version, security maintenance   End of Life versions

LEDE

[edit]
This section is about the wireless network router operating system. For other uses, see Lede (disambiguation).
LEDE
Login banner
DeveloperLEDE Project
OS familyUnix-like
Working stateMerged with OpenWrt
Source modelOpen source
Initial releaseMay 2016; 9 years ago (2016-05)
Repository
Available in26 languages[47]
Update methodopkg
Package manageropkg
Supported platforms23 platforms using the following Instruction sets: AVR32, ARM, CRIS, m68k, MIPS, PowerPC, SPARC, SuperH, Ubicom32, x86, x86-64[48]
Kernel typeMonolithic (Linux)
UserlandBusyBox, GNU
Default
user interface		CLI, WebUIs
LicenseFree software (GPL and other licenses)
Official websitelede-project.org

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

Version[13] Release date Kernel Notes
17.01.0 2017-02-22 4.4.50 first stable release[58]
17.01.1 2017-04-19 4.4.61 bug fixes and enhancements[59]
17.01.2 2017-06-12 4.4.71 security fixes[60]
17.01.3 2017-10-03 4.4.89 security fixes[61]
17.01.4 2017-10-18 4.4.92 security fixes (KRACK, as far as addressable by server side fixes)[62]
17.01.5 2018-07-18 4.4.140 security fixes [63]
17.01.6 2018-09-03 4.4.153 security fixes [64]

Features

[edit]

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

[edit]

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

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

OpenWrt Buildroot provides the following features:[70][72]

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

Hardware compatibility

[edit]

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

Adoption

[edit]

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

Derivative projects

[edit]
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.[78] 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.[79]
  • 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[80]
  • LibreMesh – Framework for creating OpenWrt-based firmwares for wireless mesh nodes. GitHub Project
  • 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.[81]
  • 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[82][83]
  • 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.[84]
  • 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.[85]

See also

[edit]

References

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

OpenWrt

View on Grokipedia
from Grokipedia
OpenWrt is a free and open-source Linux distribution targeted at embedded devices, particularly wireless routers and access points, that provides a fully writable filesystem with no read-only components and a package management system for extensive customization and extensibility beyond the limitations of proprietary vendor firmware. Developed as a highly modular GNU/Linux operating system, OpenWrt allows users to install and manage thousands of software packages, including support for advanced networking features such as IEEE 802.11s wireless mesh networking and IEEE 802.11r fast BSS transition (fast roaming) for seamless client roaming in wireless deployments, security tools, and IoT applications, all built on a recent Linux kernel without unnecessary bloat. Its design emphasizes stability, performance, and community-driven development, with over 3,000 standardized packages available for devices ranging from consumer routers to enterprise hardware. The project originated in 2004 from the open-source firmware community around the WRT54G router, sparked by the enforcement of the GNU General Public License (GPL) on its embedded code, leading to the initial "White Russian" releases that kickstarted the movement for customizable router software. In 2016, a group of developers forked the project to form LEDE (Linux Embedded Development Environment) to address governance and release process concerns, but the two initiatives remerged in January 2018 under the unified OpenWrt name to consolidate efforts and resources. Governed as a fiscally sponsored project of the since September 10, 2020, OpenWrt operates with transparent decision-making through public mailing lists, forums, and IRC channels, relying on a global volunteer community of developers and users for contributions to code, documentation, and hardware support. The project maintains regular stable releases, with the latest version, OpenWrt 24.10.4, issued on October 22, 2025, ensuring compatibility with a broad table of supported hardware encompassing hundreds of router models. A notable milestone is the launch of the OpenWrt One router on November 29, 2024, the first device designed specifically for the firmware by the in collaboration with , featuring , modular internals for repairability, and a price of US$89 to promote software freedom and user control in .

History

Origins and early development

OpenWrt originated in January 2004 as an open-source initiative sparked by 's release of GPL-licensed for the of its popular WRT54G . This disclosure, compelled in part by GPL enforcement efforts, enabled developers outside to dissect and modify the , replacing components with fully open alternatives to achieve enhanced customization and control over router functionality. The project emerged from a of tinkerers and coders motivated by the desire to unlock the full potential of embedded networking hardware, transforming static router into a dynamic, user-extensible platform. The foundational objectives centered on developing a lightweight, embeddable tailored for routers and similar devices, prioritizing , efficiency, and strict adherence to open-source principles. Early efforts focused on creating a minimal yet robust system using the GPL sources combined with a derived from the project, which facilitated the re-implementation of closed-source elements through freely available tools. This approach ensured the remained compact for resource-constrained embedded environments while allowing seamless integration of additional features. The inaugural public release in delivered a stripped-down paired with for essential utilities and basic networking tools, establishing a solid base for routing and wireless operations on the WRT54G. Community engagement surged rapidly via online forums and collaborative contributions, accelerating innovation; by early , new developers had joined, leading to the publication of experimental builds based on a customized buildroot2 system after initial closed development phases. Key early contributors included Felix Fietkau, whose work on core systems and integration proved instrumental, alongside the founding team drawn from the broader developer ecosystem responding to the GPL availability. Between 2004 and 2006, OpenWrt broadened its compatibility to encompass additional Broadcom-based devices, extending beyond the original WRT54G to support a wider array of routers sharing similar chipsets like the BCM47xx series. This period also saw the introduction of the first image builder—initially known as the image generator—a pre-configured tool that simplified the creation of tailored images without requiring full recompilation from source, thereby democratizing custom builds for users and developers. These advancements laid the groundwork for OpenWrt's growth, evolving briefly into more structured release cycles with the debut of the branch in late 2006.

Major releases and version history

OpenWrt's version history began with early experimental builds in 2004, evolving into stable releases characterized by cocktail-themed codenames until 2016, after which numerical year-month (YY.MM) versioning was adopted for major stable branches. The project transitioned from Subversion to Git for version control in 2010, facilitating more efficient collaborative development during the Backfire era. Initial releases like White Russian (version 0.9, released January 2007) were based on Linux kernel 2.4.30 and focused on basic firmware customization for devices such as the Linksys WRT54G, using a uClibc-based buildroot without a formal package manager. This was followed by the Kamikaze series (versions 7.06 to 8.09.2, released June 2007 to January 2010), which introduced the opkg package manager in 2007 for lightweight software installation and upgraded to Linux kernel 2.6.x (e.g., 2.6.21.5 in 7.09), enabling better support for diverse hardware platforms while maintaining a compact footprint. Subsequent milestone releases built on these foundations with incremental improvements in stability and features. (10.03 to 10.03.1, April 2010 to December 2011) adopted 2.6.32, a version, and enhanced wireless driver support via mac80211, including ath9k and b43 modules, alongside refinements to the build system for easier customization. (12.09, April 2013) introduced the Unified Configuration Interface (UCI) for streamlined network and system configuration, running on 3.3.x, which improved modularity for advanced routing setups. Barrier Breaker (14.07, October 2014) focused on overall stability enhancements and updated to 3.10, while Chaos Calmer (15.05 to 15.05.1, September 2015 to March 2016) marked the shift to YY.MM numbering, upgraded to 3.18 for better USB and storage handling, and added improved support, establishing a pattern of annual major releases with ongoing snapshot builds for testing. The LEDE fork from 2016 to 2018 briefly disrupted the timeline but was reintegrated, leading to continued numerical versioning. Post-reintegration releases emphasized security and hardware compatibility: 18.06 (July 2018 to December 2020) used Linux kernel 4.9/4.14 with end-of-support in December 2020; 19.07 (January 2020 to April 2022) on kernel 4.14 with stability improvements and hardware compatibility enhancements; 21.02 (September 2021 to May 2023) transitioned to kernel 5.4 for enhanced performance; 22.03 (September 2022 to April 2024) on kernel 5.10; and 23.05 (October 2023 to August 2025, now end-of-life) based on Linux kernel 5.15, introduced enhanced Wi-Fi 6 support via updated hostapd and cfg80211 components, along with security hardening, and reached end-of-support in August 2025 after six service releases. As of November 2025, the current series is 24.10 (initial stable release February 2025, incorporating over 5,400 commits from the prior branch), utilizing 6.6 for improved efficiency and new device support, with service releases up to v24.10.4 on October 22, 2025, addressing kernel updates to 6.6.110 and fixes. OpenWrt maintains a release cadence of roughly annual major versions, supplemented by daily snapshot builds, and a support policy of 2-3 years per branch, including backported patches to ensure longevity for embedded deployments.
SeriesInitial ReleaseKernel VersionKey HighlightsSupport End
White Russian (0.9)January 20072.4.30Basic buildroot foundationUnsupported
Kamikaze (7.06–8.09.2)June 20072.6.xopkg introductionUnsupported
Backfire (10.03)April 20102.6.32mac80211 wireless, Git migrationUnsupported
Attitude Adjustment (12.09)April 20133.3.xUCI configurationUnsupported
Barrier Breaker (14.07)October 20143.10Stability enhancements, procd initUnsupported
Chaos Calmer (15.05)September 20153.18YY.MM numbering, IPv6/USB improvementsUnsupported
18.06July 20184.9/4.14Post-merger stability, improved IPv6December 2020
19.07January 20204.14Hardware compatibility, ath79 supportApril 2022
21.02September 20215.4Transition to kernel 5.x, DSA networkingMay 2023
22.03September 20225.10Enhanced device support, security updatesApril 2024
23.05October 20235.15Wi-Fi 6 enhancementsEnd of Life (August 2025)
24.10February 20256.65,400+ commits, TLS 1.3Ongoing

LEDE fork and project reintegration

In 2016, dissatisfaction within the OpenWrt community grew over issues including a declining number of active core developers, lack of processes for new contributors, unreliable , insufficient transparency in , inadequate automated testing, and delays in stable releases. These concerns, compounded by internal disagreements and single points of failure in , prompted a group of prominent developers—including Jo-Philipp Wich, John Crispin, Daniel Golle, Felix Fietkau, Hauke Mehrtens, Matthias Schiffer, and Steven Barth—to announce the LEDE (Linux Embedded Development Environment) project on May 3, 2016, as a spin-off aimed at rebooting the community's collaborative efforts. The fork effectively saw nearly all active OpenWrt core developers migrate to LEDE, halting significant progress on the original project and shifting over 100 commits worth of development activity to the new initiative within weeks. LEDE differentiated itself by emphasizing automated testing frameworks, a more modular and simplified build system with enhancements to the Image Builder for easier customization, transparent public communication channels, project-wide voting for decisions, a single class of committers with a liberal merge policy, and a focus on regular, predictable release cycles to improve stability and . This approach enabled LEDE to deliver its first stable release, version 17.01 "Reboot," in February 2017—based on the earlier OpenWrt 15.05 codebase but incorporating thousands of updates over nine months, including 4.4.50, updated packages like 2.76 and 1.0.2k, enhanced security features such as SHA256 source validation, and support for new hardware targets like ipq806x and layerscape. In contrast to OpenWrt's stalled development, LEDE's faster pace addressed long-standing release delays, with infrastructure managed by multiple operators to ensure redundancy. Reunification efforts began in late 2016 through discussions between the projects, culminating in a formal proposal in May 2017 that outlined merging under the OpenWrt name while adopting LEDE's codebase, governance model, and infrastructure. The LEDE community voted in favor of the proposal by early June 2017, with unanimous support for the remerge and OpenWrt branding among participants. The process involved integrating OpenWrt patches into LEDE (provided they met quality standards), migrating resources like the repository to git.openwrt.org (with mirroring), transferring domains to Software in the for legal oversight, and phasing out separate forums and mailing lists over several months. The merger was formally announced on January 3, 2018, marking the unification of both projects under OpenWrt and establishing LEDE's rules—such as small, frequent releases and emphasis on maintenance—as the foundation for future development. Post-remerge outcomes included improved project health through decentralized management and automated processes, extended support for the LEDE 17.01 series (with service releases continuing into 2019 for security fixes), and the archival of pre-15.05 OpenWrt releases while limiting updates to 15.05. This reintegration, facilitated by a collaborative summit in 2017, resolved the schism and fostered greater community participation, with the unified repository reflecting contributions from both sides.

Technical features

Core architecture and components

OpenWrt serves as an embedded Linux distribution characterized by a minimal root filesystem that incorporates to deliver compact implementations of essential utilities, enabling efficient operation on resource-constrained hardware. The system is built around the , with the 24.10 stable release utilizing version 6.6, which is optimized for embedded devices through targeted configurations and modules. This base structure ensures a lightweight foundation, typically occupying just a few megabytes, while supporting extensibility without compromising core stability. Central to OpenWrt's architecture are several key components that facilitate configuration and management. The LuCI web interface provides a user-friendly graphical frontend for system administration, allowing modifications via a browser-based dashboard. Complementing this is the Unified Configuration Interface (UCI), a centralized utility that standardizes settings management across diverse applications by storing configurations in plain-text files under /etc/config/, accessible through command-line tools, Lua bindings, or C libraries. For process supervision and initialization, OpenWrt employs procd, a lightweight daemon written in C that handles init scripts, hotplug events, and service restarts via the ubus inter-process communication system, replacing older mechanisms like hotplug2. Modularity is a core principle of OpenWrt's design, achieved through a layered filesystem approach. The immutable base resides in a read-only image mounted at /rom, which compresses the core system for efficient storage on . Writable changes are managed via , which unions a persistent /overlay partition—typically formatted as on NOR flash or on NAND—with the read-only layer, allowing users to modify files and install software without altering the original image. Additionally, support for initramfs enables temporary, RAM-based boots for recovery or testing scenarios, loading a minimal environment directly into memory. The architecture is tailored for devices with limited resources, targeting systems with 8 to 128 MB of RAM and 4 to 32 MB of flash storage, where modern builds warn against using below 8 MB flash or 64 MB RAM due to constraints on package installations. Administration emphasizes command-line tools via ash shell (from ) and the LuCI web interface, eschewing resource-intensive graphical desktops to prioritize efficiency and security on embedded platforms. Over time, OpenWrt has evolved its standard library implementation, transitioning from to libc starting with the Chaos Calmer (15.05) release in 2015 to enhance compliance, reduce size, and improve security without increasing footprint. This shift, now standard in releases like 24.10 with 1.2.5, better supports modern software while maintaining compatibility with embedded constraints.

Package management and extensibility

OpenWrt employs as its lightweight , a of the earlier ipkg system originally developed for embedded devices like the NSLU2's Optware. handles the installation, removal, and management of software packages in the .ipk format, allowing users to extend the base firmware without rebuilding the entire image. This system overlays packages onto the read-only base filesystem using a writable overlay, such as or , to conserve limited flash storage while enabling persistent changes. The primary repositories for opkg are hosted on downloads.openwrt.org, offering over 9,000 packages as of 2025 across various architectures in the latest release. These include branches for releases, snapshot feeds for the development trunk with cutting-edge updates, and third-party feeds for specialized content such as drivers. Package indexes are configured via files like /etc/opkg/distfeeds.conf, and security is enhanced by signature verification using the usign tool with ed25519 keys, a feature integrated since the Chaos Calmer 15.05 release in 2015. Installation and management occur primarily through command-line operations. Users first run opkg update to refresh the package lists from repositories, followed by opkg install <package> to download and install software along with its dependencies, or opkg remove <package> to uninstall it. Opkg automatically resolves dependencies, ensuring required libraries and components are pulled in, though users can override with flags like --force-depends if needed. For pre-configured setups, the Image Builder tool integrates opkg by allowing users to generate images with selected packages baked in, avoiding runtime installation on resource-constrained devices. This extensibility enables diverse customizations, such as adding VPN support via or clients, setting up media sharing with or MiniDLNA servers, or deploying monitoring with tools like Collectd, all resolved through opkg's dependency handling. OpenWrt supports multiple plugins for internet behavior monitoring, including traffic statistics, app/website filtering, time controls, access logs, and app identification, which can be installed via opkg or third-party feeds with varying compatibility by version and hardware. Common options include OpenAppFilter (OAF) for DPI-based app filtering and auditing of over 100 applications; FROS for app filtering of over 400 applications, audit reports with visualized records, and time controls for parental management; luci-app-accesscontrol for MAC-based time restrictions; Squid + Sarg for HTTP/HTTPS access logs and reports; ntopng for traffic monitoring and analysis; luci-app-statistics for flow charts; and firewall rules combined with dnsmasq for domain logging. The overlay mechanism ensures efficient storage by writing changes only to the upper layer, minimizing footprint on flash-limited hardware. Despite its flexibility, opkg has constraints tied to embedded environments. Package sizes are limited by available flash storage, often capping installations on devices with 8 MiB or less, potentially requiring extroot configurations for . Additionally, the base system lacks automatic updates, necessitating manual opkg upgrade commands or full sysupgrades, as mass updates can risk instability or soft-bricking if not handled carefully.

Networking and security functionalities

OpenWrt's networking core is built around a that provides comprehensive control and protection. Starting with version 22.03, the firewall backend shifted from (used in firewall3) to via firewall4, enabling more efficient rule processing and native support for modern netfilter features like connection tracking and NAT. This system uses zone-based policies to define flows between interfaces, such as allowing LAN-to-WAN forwarding while rejecting unsolicited inbound WAN by default, thereby securing the router against external threats. For VLAN-based WiFi isolation, such as for guest or IoT networks, users can create separate firewall zones for these interfaces, enable forwarding from these zones to the WAN only, and prohibit forwarding to the main LAN zone; optionally, plugins like banIP for dynamic IP banning or AdGuard for ad-blocking and DNS-based filtering can be installed to impose additional restrictions. VLAN support adheres to and 802.1ad standards, allowing users to configure virtual LANs on switch-equipped devices for without additional hardware. Quality of Service (QoS) is implemented using the control (tc) subsystem, with the integrated Smart Queue Management (SQM) tool applying algorithms like or fq_codel to prioritize and mitigate , ensuring low latency for real-time applications even on congested links. Dynamic routing protocols are handled by the BIRD daemon, supporting BGP, OSPF, and RIP for advanced route propagation in complex topologies. OpenWrt supports internet behavior monitoring through various plugins that enable traffic statistics, app/website filtering, time controls, access logs, and app identification, enhancing traffic management and security. Common options include OpenAppFilter (OAF) for deep packet inspection (DPI)-based app filtering and auditing of over 100 applications; FROS for app filtering covering more than 400 applications, audit reports with visualized records, and time controls, particularly for parental management; luci-app-accesscontrol for MAC-based time restrictions; Squid combined with Sarg for HTTP/HTTPS access logs and reports; ntopng for comprehensive traffic monitoring and analysis; luci-app-statistics for flow chart visualizations; and firewall rules integrated with dnsmasq for domain logging. These plugins are installed via the opkg package manager or third-party feeds, with compatibility varying by OpenWrt version and hardware. Additionally, OpenWrt natively enables IPv4/IPv6 dual-stack operation, including client and server modes for and address assignment, facilitating seamless transition to environments. Wireless functionalities in OpenWrt emphasize flexibility and performance for router deployments. The hostapd daemon manages access point configurations, supporting WPA2/WPA3 encryption, multiple SSIDs, and client isolation to enhance privacy. For mesh networking, the batman-adv kernel module enables layer-2 routing over Wi-Fi links, allowing seamless extension of networks across multiple nodes with features like VLAN bridging for isolated client groups. Additionally, OpenWrt supports the IEEE 802.11s standard for wireless mesh networking, which provides standardized mesh backhaul between nodes using Wi-Fi protocols and works reliably in recent versions with compatible hardware and drivers. For seamless client roaming across access points sharing the same SSID, OpenWrt implements IEEE 802.11r Fast BSS Transition (also known as Fast Transition), which reduces authentication time during handovers. These two standards are distinct from each other and from batman-adv but can be effectively combined, with 802.11s handling mesh backhaul infrastructure and 802.11r enabling fast client mobility in the same deployment; official documentation and community configurations from 2024-2025 confirm reliable operation in current OpenWrt releases. Recent OpenWrt releases, leveraging Linux kernel 5.15 and later, provide support for Wi-Fi 6 (802.11ax) and preliminary Wi-Fi 7 (802.11be) through drivers such as ath10k/ath11k for Atheros/Qualcomm chipsets and mt76/mediatek for MediaTek hardware, delivering improved throughput, MU-MIMO, and OFDMA for dense environments. Security is a foundational aspect of OpenWrt, with built-in tools promoting hardening from installation. The Dropbear SSH server offers lightweight, secure remote access, configurable for public-key authentication and restricted to LAN interfaces to prevent WAN exposure. The uhttpd web server powers the LuCI interface with HTTPS support via Let's Encrypt integration or self-signed certificates, and can be tunneled over SSH for added protection against interception. To counter brute-force attacks, fail2ban can be installed and configured to scan logs from Dropbear and uhttpd, dynamically banning offending IPs through firewall rules. The opkg package manager facilitates automatic security updates, with the project maintaining a vulnerability disclosure process that tracks CVEs—such as those affecting kernel components or packages—dating back to 2010, ensuring timely patches via advisories and repository feeds. For advanced secure tunneling, WireGuard has been the preferred VPN protocol since OpenWrt 21.02, offering high-speed, kernel-level encryption with minimal configuration overhead compared to legacy options like OpenVPN. Unique to OpenWrt's design is its hotplug , powered by procd, which dynamically detects and configures network interfaces in response to hardware changes, such as plugging in a USB Ethernet adapter or , without manual intervention. To enforce secure initial setup, OpenWrt installations ship with no default , prompting users to set one via the firstboot process or LuCI interface, thereby avoiding common vulnerabilities from factory credentials. While core networking and tools are pre-installed, further customization—such as additional VPN clients or intrusion detection—is achievable through the opkg package .

Development

Governance and community structure

Following the reintegration of the LEDE fork in January 2018, OpenWrt operates under a model derived from the LEDE project's rules, where decisions are made by simple majority vote among committers, with an emphasis on broad consensus achieved through public discussions on mailing lists and IRC channels. The project distinguishes between committers, who have repository access and voting rights, and non-committers, fostering an open process that balances input from developers and power users. The community structure revolves around key hubs, including the official forum at forum.openwrt.org for user support and discussions, the repository at github.com/openwrt/openwrt for issue tracking and code contributions, and periodic in-person developer meetings such as the annual OpenWrt Summit. These gatherings, like the 2025 event in Sundhausen, , facilitate collaboration on project priorities and technical advancements. OpenWrt maintains a centered on Rule 11: "Be nice to each other," established in 2016, which promotes respectful interactions and prohibits to ensure an inclusive environment for all participants. Funding supports the volunteer-driven project through donations managed by the , its fiscal sponsor since September 2020 as a 501(c)(3) non-profit organization, alongside sponsorships from hardware vendors such as , which collaborates on device testing and development like the OpenWrt One router. Maintainer responsibilities are divided among target-specific maintainers who oversee hardware ports and architectures, release managers who coordinate version updates and stability, and a broader base of active contributors exceeding 1,000 individuals who handle package maintenance, testing, and documentation as of 2025.

Build system and contribution processes

The OpenWrt build system is based on Buildroot, which automates the compilation of a cross-compilation toolchain, kernel, and root filesystem for embedded devices. It relies on a set of Makefiles to define build rules, dependencies, and targets, enabling the generation of firmware images tailored to specific hardware. Patches are managed using Quilt, a tool integrated into the system for applying, refreshing, and organizing modifications to upstream sources during the build process. This setup supports cross-compilation across multiple target architectures, such as MIPS, ARM, and x86, by producing a complete toolchain including compilers like GCC, binutils, and libraries such as musl libc on the host system. Developers contribute to OpenWrt primarily through its repositories hosted on mirrors, where changes are submitted as pull requests (PRs) after forking the relevant repository. The involves creating a dedicated branch for each set of changes, writing commit messages in imperative form with a Signed-off-by line per contribution standards, and ensuring patches are tested locally before submission. is conducted by maintainers, who verify formatting, functionality, and adherence to guidelines using tools like the checkpatch.pl script; approved PRs are merged via staging trees into the primary repository at git.openwrt.org. and () processes utilize Actions to automate testing and builds on pull requests, a practice adopted across OpenWrt repositories to catch issues early. Several tools facilitate development without requiring a full source build. The Image Builder provides a pre-compiled environment for end-users and developers to customize images by adding packages, modifying configurations, or generating sysupgrade-compatible files, bypassing the need for complete recompilation. The (SDK) allows isolated compilation of individual packages against a pre-built , streamlining package development and testing. The feeds system enables integration of external package repositories by defining them in the feeds.conf file and updating via scripts, allowing modular extension of the core build with community or third-party contributions. Quality assurance in OpenWrt emphasizes automated builds and selective testing. Nightly snapshots are generated daily from the latest source code, providing experimental firmware with associated build logs and failure reports available for debugging build issues across targets. Some packages leverage autotools for configuration and include unit tests during compilation to validate functionality, though core system components rely more on integration testing via the build process. Security fixes from upstream projects are actively monitored and backported to stable release branches, ensuring long-term support for verified releases while snapshots receive the latest changes. To lower , OpenWrt maintains extensive documentation on its , covering build setup, package creation, and patching workflows to guide new contributors. While formal mentorship programs have been explored through initiatives like in related projects, the community encourages participation via forums and IRC for direct support.

Hardware support

Compatible device categories

OpenWrt primarily supports consumer-grade routers, access points, and embedded single-board computers, enabling users to customize for advanced functionality. These categories encompass a wide range of devices from mainstream vendors, with compatibility determined by factors such as processor , storage capacity, and presence. Wireless routers form the largest supported category, including popular models like the WRT series (e.g., WRT54G) and Archer series (e.g., Archer C7), which are favored for their robust community support and ease of flashing. Wireless access points, such as those from and Engenius, provide focused coverage without full routing capabilities, often integrated into larger networks. Embedded single-board computers, like the models with custom OpenWrt builds, extend support to non-traditional for applications in IoT and custom gateways. Installation on compatible devices typically involves web-based firmware upgrades through the original equipment manufacturer (OEM) interface, which allows direct flashing of OpenWrt images without specialized tools. For recovery or initial setup on Broadcom-based chips, TFTP () methods are common, requiring a network connection and specific button combinations to enter mode. Advanced users may employ serial console access via a USB-to-TTL cable for or debricking, particularly on devices with locked . These processes carry risks, including permanent bricking if power is interrupted or incorrect images are applied, and often necessitate compatibility with tools like U-Boot or CFE (Common Firmware Environment). The official Table of Hardware (ToH) database on the OpenWrt website lists approximately 2,000 supported models as of 2025, providing detailed installation guides, recovery button sequences, and warnings about potential risks like reduced usable flash . Vendor support varies, with official OpenWrt images available for brands such as (e.g., R series), (e.g., RT-AC series), and , while community-maintained ports cover older or niche hardware from manufacturers like and Buffalo. All compatible devices must meet minimum hardware prerequisites of 8 MB flash storage and 64 MB RAM, though 16 MB flash and 128 MB RAM are recommended for full feature support and updates in recent . Bootloader compatibility is essential, as OpenWrt relies on unmodified or unlockable boot environments like U-Boot for reliable installation.
CategoryExamplesKey Considerations
Wireless RoutersLinksys WRT54G, TP-Link Archer C7High community support; web/TFTP install
Wireless Access PointsUbiquiti UniFi AP, Engenius EAPFocused on ; serial recovery common
Embedded SBCs (custom build)Versatile for IoT; requires manual configuration

Target architectures and platforms

OpenWrt primarily supports MIPS architectures, which remain the most common for consumer routers due to their prevalence in embedded ; these include both big-endian and little-endian variants such as mips_24kc and mipsel_74kc. architectures have become dominant since around 2015, encompassing Cortex-A and Cortex-M series processors across 32-bit and 64-bit implementations like arm_cortex-a9_neon and aarch64_cortex-a53, enabling support for a wide range of modern system-on-chips (SoCs). OpenWrt 24.10 also introduced support for LoongArch architectures via the loongarch64 target. x86 and x86_64 architectures are targeted for mini-PCs, virtual machines, and servers, leveraging more powerful / hardware for advanced routing applications. support emerged in OpenWrt 24.10, including platforms like Allwinner D1 and StarFive JH71x0, marking an expansion into open instruction set architectures. Key SoC platforms include Atheros with the ath79 target for chips, offering robust open-source integration for MIPS-based devices. platforms, such as ramips for MT7620/MT7621 and mt76 for newer chipsets, dominate budget routers and access points. Qualcomm Atheros QCA series are covered under targets like ipq40xx and ipq806x, supporting high-performance SoCs in enterprise-grade equipment. support is limited, particularly for components, due to reliance on proprietary drivers that complicate full open-source compatibility. Porting OpenWrt to new platforms involves developing kernel modules tailored to specific SoCs, often integrating vendor-provided trees such as the SDK for IPQ series initialization and hardware abstraction. Ongoing efforts include upstreaming drivers for emerging Wi-Fi 7 chips like MT792x via the mt76 subsystem, enhancing support for 802.11be standards in recent kernels. Challenges in porting include the need for closed-source binary blobs for certain interfaces, such as BCM43xx series, which hinder complete open-source operation and require hybrid driver approaches. Power management for battery-powered or low-energy devices, particularly on platforms, demands custom kernel configurations to balance performance and efficiency without vendor documentation. OpenWrt 24.10 provides stable support for over 39 targets across these architectures, with snapshot builds extending experimental coverage to platforms like RK35xx for ARMv8-based single-board computers.

Adoption and impact

Widespread usage and applications

OpenWrt enjoys significant consumer adoption for enhancing home routers with advanced customization options beyond stock limitations. Users frequently install packages like , Adblock-Fast, Home, and Adblock-Lean to enable network-wide ad-blocking, which effectively reduces advertisements, conserves bandwidth, and mitigates tracking across all connected devices. Similarly, are a common application, utilizing firewall configurations to block specific web pages, enforce time-based access restrictions, and limit connectivity via filtering, making it accessible for family network management. These features are achieved through straightforward upgrades on supported hardware, contributing to its popularity among home users seeking greater control and privacy. Advantages of OpenWrt for local network management include its free and open-source nature, high customizability, full support for VLANs and multiple SSIDs, and compatibility with various hardware. Disadvantages may include the need for initial firmware flashing, which is guided but required, and a steeper learning curve compared to graphical systems like Omada, although the LuCI web interface is intuitive for many users. In enterprise and ISP environments, OpenWrt supports deployments in specialized networking scenarios, including mesh networks and VoIP gateways. Research demonstrates its effectiveness in low-cost mesh architectures that integrate Voice over Internet Protocol (VoIP) for reliable communication in resource-constrained settings, such as campus or rural deployments. Its extensible design also facilitates implementations, allowing dynamic traffic optimization across multiple connections. Partnerships with vendors like Gl.iNet further promote professional adoption by offering pre-flashed OpenWrt routers optimized for , IoT gateways, and secure remote management, with models like the GL-MT3000 providing dual-band and multi-gigabit Ethernet support. Prior to the launch of its Amplifi product line, leveraged OpenWrt-based firmware in devices like the AirOS series for enterprise-grade solutions. OpenWrt's versatility extends to educational and hobbyist applications, particularly in IoT and smart home projects. It integrates seamlessly with platforms like to automate and control connected appliances, enabling users to build custom smart home ecosystems on embedded hardware. In academic settings, it serves as a tool in university networking courses and labs, where its open-source nature supports hands-on experiments in protocol configuration, , and custom firmware development. Hobbyists often repurpose OpenWrt-enabled devices for innovative uses, such as systems in or , capitalizing on its lightweight base and package ecosystem. The platform's market impact is evident in its role displacing proprietary stock firmware among networking enthusiasts, who value its superior customization and security over vendor defaults. The global OpenWrt Wi-Fi router market, encompassing compatible hardware and firmware solutions, was valued at $1.2 billion in 2024 and is projected to reach $4.7 billion by 2033, driven by demand for open-source alternatives in customizable networking. This growth is amplified in emerging markets through support for affordable, high-performance hardware like budget MIPS-based routers with at least 16 MB flash and 128 MB RAM, enabling widespread access to advanced features without high costs. As of 2025, over 230 companies worldwide, including Amazon and , incorporate OpenWrt in their operations or products, underscoring its enterprise reach. The OpenWrt forum reflects this active user base with more than 59,000 topics across categories like installation, hardware, and development discussions. A notable recent development enhancing adoption is the OpenWrt One router, launched on November 29, 2024, in collaboration with and the , which features and modular design to promote accessible, repairable hardware running OpenWrt.

Derivative projects and forks

DD-WRT is a prominent alternative to OpenWrt, emphasizing ease-of-use through an enhanced (GUI) and broad hardware compatibility for routers and embedded systems. Originally developed as an independent since 2005, it prioritizes user-friendly features like simplified configuration menus and advanced options while maintaining Linux-based extensibility. Tomato, particularly its active continuation as FreshTomato, serves as a lightweight alternative optimized for Broadcom-based routers, incorporating performance tweaks such as advanced QoS, bandwidth monitoring, and efficient to enhance throughput on compatible hardware. It streamlines the interface for reduced overhead, making it suitable for users seeking minimalistic yet powerful networking solutions. Gargoyle extends OpenWrt with a focus on user-friendly (QoS) management, providing intuitive tools for setting bandwidth quotas, throttles, and visual monitoring to equitably distribute network resources. Based directly on OpenWrt releases like version 22.03, it adds custom web interfaces for QoS configuration without altering the underlying kernel or package system. Among forks emphasizing software freedom, LibreCMC stands out as a fully free /Linux distribution for embedded devices, adhering strictly to the Free Software Foundation's guidelines by excluding non-free components. Derived from OpenWrt, it targets minimal-resource hardware like routers, ensuring all included software meets 's free software definition for greater user control and ethical compliance. Vendor-specific variants like AsusWRT-Merlin enhance proprietary Asus router firmware with OpenWrt-inspired improvements, such as better stability, additional scripting support, and minor feature additions, while retaining the base AsusWrt codebase. This approach allows users to leverage OpenWrt-like extensibility on hardware without fully replacing the manufacturer's software. Collaborative projects include OpenWISP, an open-source network management system designed for ISPs, which integrates OpenWrt devices for automated configuration, monitoring, RADIUS authentication, and firmware upgrades across large-scale deployments. Similarly, Turris OS, developed by CZ.NIC, is a secure OpenWrt-based operating system for routers, featuring automatic lifetime updates, dynamic firewall rules, and tools like reForis for web-based management to bolster network security. These projects often share foundational elements with OpenWrt, such as the , while diverging to address niche requirements like enhanced GUIs or freedom-focused builds. Contributions occasionally flow back to the main project, exemplified by the Smart Queue Management (SQM) system originating from the CeroWrt , which was integrated into OpenWrt to mitigate through advanced . As of 2025, the OpenWrt ecosystem remains vibrant, with numerous major derivatives fostering cross-pollination through platforms like , where shared code and best practices continue to evolve the broader community of router projects.

References

  1. https://openwrt.org/about
  2. https://openwrt.org/docs/guide-user/network/wifi/mesh/802-11s
  3. https://openwrt.org/docs/guide-user/network/wifi/roaming
  4. https://openwrt.org/
  5. https://sfconservancy.org/news/2024/nov/29/openwrt-one-wireless-router-now-ships-black-friday/
  6. https://openwrt.org/about/history
  7. https://sfconservancy.org/copyleft-compliance/enforcement-strategy.html
  8. https://nixfaq.org/2021/10/openwrt-a-specialized-operating-system-for-routers.html
  9. https://openwrt.org/docs/guide-user/additional-software/imagebuilder
  10. https://forum.archive.openwrt.org/viewtopic.php?id=26942
  11. https://forum.archive.openwrt.org/viewtopic.php?id=18176
  12. https://forum.archive.openwrt.org/viewtopic.php?id=24177
  13. https://forum.archive.openwrt.org/viewtopic.php?id=37864
  14. https://openwrt.org/releases/15.05/notes-15.05
  15. https://openwrt.org/releases/23.05/notes-23.05.0
  16. https://openwrt.org/releases/23.05/notes-23.05.6
  17. https://openwrt.org/releases/24.10/notes-24.10.0
  18. https://openwrt.org/releases/24.10/notes-24.10.4
  19. https://openwrt.org/docs/guide-developer/security#support_status
  20. https://lwn.net/Articles/686767/
  21. https://www.theregister.com/2016/05/05/router_hackers_reach_for_the_fork_lede_splits_from_openwrt/
  22. https://forum.archive.openwrt.org/viewtopic.php?id=71024
  23. https://openwrt.org/releases/17.01/notes-17.01.0
  24. https://www.cnx-software.com/2018/01/04/openwrt-lede-projects-merge-announced/
  25. https://lwn.net/Articles/722135/
  26. https://www.theregister.com/2018/01/08/lede_and_openwrt_merge/
  27. https://lwn.net/Articles/742708/
  28. https://openwrt.org/packages/pkgdata/busybox
  29. https://openwrt.org/docs/guide-user/luci/start
  30. https://openwrt.org/docs/techref/uci
  31. https://openwrt.org/docs/techref/procd
  32. https://openwrt.org/docs/techref/flash.layout
  33. https://openwrt.org/supported_devices/864_warning
  34. https://openwrt.org/releases/15.05/start
  35. https://openwrt.org/docs/guide-user/additional-software/opkg
  36. https://downloads.openwrt.org/
  37. https://repology.org/repository/openwrt_24_10_x86_64
  38. https://openwrt.org/packages/start
  39. https://github.com/66781881/openwrt-OpenAppFilter
  40. https://www.fros.org.cn/
  41. https://openwrt.org/docs/guide-user/services/webserver/squid
  42. https://openwrt.org/docs/guide-user/firewall/firewall_configuration
  43. https://openwrt.org/rules
  44. https://forum.openwrt.org/
  45. https://openwrt.org/meetings/start
  46. https://openwrt.org/meetings/20250429
  47. https://sfconservancy.org/news/2020/sep/10/openwrt-joins/
  48. https://www.techpowerup.com/327250/openwrt-community-and-banana-pi-launch-openwrt-one-wifi-6-router
  49. https://github.com/openwrt/openwrt
  50. https://openwrt.org/docs/guide-developer/toolchain/buildsystem_essentials
  51. https://openwrt.org/submitting-patches
  52. https://openwrt.org/docs/guide-developer/feeds
  53. https://openwrt.org/releases/snapshot
  54. https://downloads.openwrt.org/snapshots/
  55. https://openwrt.org/docs/guide-developer/security
  56. https://openwrt.org/faq/how_can_i_help_or_contribute
  57. https://openwrt.org/toh/start
  58. https://openwrt.org/supported_devices
  59. https://openwrt.org/docs/guide-user/installation/generic.flashing
  60. https://openwrt.org/docs/techref/targets/start
  61. https://openwrt.org/docs/guide-user/installation/openwrt_x86
  62. https://downloads.openwrt.org/releases/24.10.0/targets/ath79/
  63. https://downloads.openwrt.org/releases/24.10.0/targets/ramips/
  64. https://openwrt.org/docs/techref/hardware/soc
  65. https://openwrt.org/docs/guide-developer/add.new.platform
  66. https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=372c2ea65612fc86039f441be16714df249cd063
  67. https://downloads.openwrt.org/releases/24.10.0/targets/
  68. https://git.openwrt.org/?p=openwrt/openwrt.git;a=shortlog;h=36d0690993ba90321fd0c004e5f3c66ac10966ee
  69. https://openwrt.org/docs/guide-user/services/ad-blocking
  70. https://openwrt.org/docs/guide-user/firewall/fw3_configurations/fw3_parent_controls
  71. https://openwrt.org/reasons_to_use_openwrt
  72. https://www.gl-inet.com/
  73. https://community.ui.com/questions/SDK-investigations-AirOS-V-OpenWRT/3da097b4-9a7c-4fce-803b-e29b54f01fcc
  74. https://www.seeedstudio.com/blog/2021/10/13/smart-home-with-home-assistant-on-openwrt/
  75. https://researchintelo.com/report/openwrt-wifi-router-market
  76. https://openwrt.org/toh/recommended_routers
  77. https://data.landbase.com/technology/openwrt/
  78. https://dd-wrt.com/
  79. https://freshtomato.org/
  80. https://www.gargoyle-router.com/
  81. https://librecmc.org/
  82. https://www.asuswrt-merlin.net/
  83. https://openwisp.org/
  84. https://www.turris.com/en/turris-os/
  85. https://www.bufferbloat.net/projects/cerowrt/wiki/
Add your contribution
Related Hubs
User Avatar
No comments yet.