Kalpana Kalpana (Editor)

OpenWrt

Updated on
Edit
Like
Comment
Share on FacebookTweet on TwitterShare on LinkedInShare on Reddit
Developer
  
OpenWrt Project

OS family
  
Unix-like

Source model
  
Open source

Written in
  
Lua

Working state
  
Current

Initial release
  
January 2004 (2004-01)

OpenWrt

OpenWrt is an embedded operating system based on Linux, primarily used on embedded devices to route network traffic. The main components are Linux, util-linux, uClibc or musl, and BusyBox. All components have been optimized for size, to be small enough for fitting into the limited storage and memory available in home routers.

Contents

OpenWrt is configured using a command-line interface (ash shell), or a web interface (LuCI). There are about 3500 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), and laptops. It is also possible to run OpenWrt on personal computers, which are most commonly based on the x86 architecture.

History

The project came into being because Linksys built the firmware for their WRT54G series of wireless routers from publicly available code licensed under the GPL. Under the terms of that license, Linksys was required to make the source code of its modified version available under the same license, which in turn enabled independent developers to create additional derivative versions. Support was originally limited to the WRT54G series, but has since been expanded to include many other chipsets, manufacturers and device types, including Plug Computers and Openmoko mobile phones.

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. Some features formerly required proprietary software. Before the introduction of OpenWrt 8.09, using Linux 2.6.25 and the b43 kernel module, WLAN for many Broadcom-based routers was only available through the proprietary wl.o module that was also provided for Linux 2.4.x only.

The code names of OpenWrt branches are named after alcoholic beverages, usually including their recipes in the MOTD as well, cf. White Russian, Kamikaze, Backfire, Attitude Adjustment, Barrier Breaker.

Hardware incompatibilities

With the Attitude Adjustment (12.09) release of OpenWrt, all hardware devices with 16 MB or less RAM are no longer supported as they can run out of memory easily. Older Backfire (10.03) is recommended instead for bcm47xx devices, as issues for those devices came from dropping support for the legacy Broadcom target brcm-2.4.

Features

OpenWrt follows the bazaar-philosophy and is known for an abundance of options. Features include:

  • A writable root file system, enabling users to add, remove or modify any file. This is accomplished by using overlayfs to overlay a read-only compressed SquashFS file system with a writable JFFS2 file system in a copy-on-write fashion. JFFS2 supports flash wear leveling.
  • The package manager opkg, similar to dpkg, enables users to install and remove software. The package repository contains about 3500 packages. This contrasts with Linux-based firmwares based on read-only file systems without the possibility to modify the installed software without rebuilding and flashing a complete firmware image.
  • A set of scripts called UCI (unified configuration interface) intended to unify and simplify the configuration of the entire system
  • 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.
  • Exhaustive possibilities to configure network-related features, like:
  • IPv4 support.
  • IPv6 native stack:
  • Prefix Handling,
  • Native IPv6 configuration (SLAAC, stateless DHCPv6, stateful DHCPv6, DHCPv6-PD),
  • IPv6 transitioning technologies (6rd, 6to4, 6in4, ds-lite, lw4o6, map-e),
  • Downstream IPv6 configuration (Router Advertisement, DHCPv6 (stateless and stateful) and DHCPv6-PD).
  • Routing through iproute2, Quagga, BIRD, Babel etc.
  • Mesh networking through B.A.T.M.A.N., OLSR and IEEE 802.11s-capabilities of the WNIC drivers
  • 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.
  • Stateful firewall, NAT and port forwarding through netfilter; additionally PeerGuardian is available
  • Dynamically-configured port forwarding protocols UPnP and NAT-PMP through upnpd, etc.
  • Port knocking via knockd and knock
  • TR-069 (CWMP) client
  • IPS via Snort (software)
  • 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. 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, etc.)
  • Extensible realtime network monitoring and statistics through e.g. RRDtool, Collectd, Nagios, Munin lite, Zabbix, etc.
  • Domain Name System (DNS) and DHCP through Dnsmasq, MaraDNS, etc.
  • Dynamic DNS services to maintain a fixed domain name with an ISP that does not provide a static IP address
  • Wireless distribution system (WDS) including WPA-PSK, WPA2-PSK, WPA-PSK/WPA2-PSK Mixed-Mode encryption modes
  • OpenWrt supports any hardware that has Linux support; devices that can be connected (e.g. over USB) to an embedded device include
  • Printers
  • Mobile broadband modems
  • Webcams
  • Sound cards
  • Notable software packages to use the hardware support are:
  • File sharing via SAMBA, (Windows-compatible), NFS and FTP, 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
  • An extensive Ajax-enabled web interface, thanks to the LuCI project
  • Regular bug fixes and updates, even for devices no longer supported by their manufacturers

    • Web interface

    Before release 8.09, OpenWrt had a minimal web interface. In OpenWrt releases 8.09 and newer, a more capable web interface is included. This interface is based on LuCI, an MVC framework written in the Lua programming language.

    The X-Wrt project provides an alternative web interface, named webif² in the package repositories, for the current and previous versions of OpenWrt.

    The Gargoyle Router Management Utility is a web interface for OpenWrt with a strong emphasis on usability. It was originally available as a set of packages for OpenWrt. As the author of Gargoyle started to make modifications to the base system layout of OpenWrt, the package system was dropped and only complete firmware images are now available for download. Gargoyle makes extensive use of JavaScript to offload as much work as possible to the client computer, and is focused on ease of use, striving to reach a level comparable to the appliance feeling of commercial router firmware.

    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.

    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.

    OpenWrt Buildroot provides the following features:

  • 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.

    Hardware compatibility

    OpenWrt runs many different routers, and includes a table of compatible hardware on its website. In its buyer's guide, it recommends Qualcomm Atheros chips over Broadcom chips.

    Adoption

    OpenWrt, especially its Buildroot build system, has been adopted many times:

  • Freifunk and other mesh network communities
  • Bufferbloat.net (Cerowrt)
  • IETF IPv6 integration projects HIPnet and HomeNet are OpenWrt-based

    • Derivatives

  • LEDE is founded as a spin-off of the OpenWrt project and shares many of the same goals.
  • CeroWrt – with a purpose to complement the debloat-testing kernel tree and provide a platform for real-world testing of bufferbloat fixes
  • Coova chilli – OpenWrt-based with focus on wireless hotspots, a fork of chillifire with focus on wireless hotspot management
  • Gargoyle – a web interface for OpenWrt with a strong emphasis on usability that later forked into a separate distribution
  • 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
  • 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.
  • 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.
  • The Turris Omnia router runs on an OpenWrt derivative
  • Diverse grassroots projects for wireless community networks, including Freifunk, Libre-Mesh and qMp
  • libreCMC – OpenWrt-based distribution without non-free software or binary blobs, endorsed by the Free Software Foundation

    • References

    OpenWrt Wikipedia
    (Text) CC BY-SA