Felix Fietkau
090afc220f
hostapd, wpa_supplicant and wdev.uc each allocate addresses with the allocator of common.uc, and each sees the addresses of the others only through lists that they pass to each other or through the netdevs that exist at that moment. An address that one of them keeps for an interface without a netdev is free for the others. Add one allocation table to the wireless code of netifd, with four methods on network.wireless: - macaddr_get gives an address to a name of an owner (hostapd, wpa_supplicant or wdev). A name keeps its address while the wiphy, the radio and the generator options stay the same; with any_radio, also when the radio or the options change, as a station MLD needs. A configured (static) address that another name holds is refused. share lets a name use the address of another name of the same owner, as an AP MLD link does with the MLD address. - macaddr_sync sets the names of an owner and group in one call: names that it does not list are released, and an address can move to another name of the group (from), for a renamed or swapped BSS. - macaddr_release releases one name. - macaddr_list shows the table. Addresses are unique per wiphy. Generation skips the addresses of the interfaces in the UCI configuration, and the addresses of netdevs without an entry. The generator is a copy of the one in common.uc, with the per-radio ranges; it reads the wiphy once per request and stops at the first free address. An entry that shares the address of another name holds that address for the shared name only: a request for that name does not count the entry as a holder. Such an entry accounts for no netdev, so the check of the live netdevs still runs. A released entry, and each entry of an owner whose ubus object goes away, stays as a stale entry for the life of netifd, so that the interface or the process that comes back gets its address by name: - A request, or a sync that keeps the name, claims the entry again. - A released entry with a configured address goes instead. The address comes back with the configuration. - A new name gets a stale address only where the range of the request has no other free address. - A stale entry yields to a request that names its address: a configured address, a shared one, or a value of a sync. A request that takes the address removes the stale entries of other names with it. In a sync, the entries of the same owner lose the address; a stale entry of another owner keeps it, and its name finds a holder when it asks again. The table lives in netifd only. A restart of netifd through its init script tears the radios down first, so the new table starts empty. The configured addresses are lower-cased again in update_config(), because hostapd and wpa_supplicant compare them with the addresses that netifd returns. Nothing uses the methods yet. Signed-off-by: Felix Fietkau <nbd@nbd.name>
OpenWrt Project is a Linux operating system targeting embedded devices. Instead of trying to create a single, static firmware, OpenWrt provides a fully writable filesystem with package management. This frees you from the application selection and configuration provided by the vendor and allows you to customize the device through the use of packages to suit any application. For developers, OpenWrt is the framework to build an application without having to build a complete firmware around it; for users this means the ability for full customization, to use the device in ways never envisioned.
Sunshine!
Download
Built firmware images are available for many architectures and come with a package selection to be used as WiFi home router. To quickly find a factory image usable to migrate from a vendor stock firmware to OpenWrt, try the Firmware Selector.
If your device is supported, please follow the Info link to see install instructions or consult the support resources listed below.
An advanced user may require additional or specific package. (Toolchain, SDK, ...) For everything else than simple firmware download, try the wiki download page:
Development
To build your own firmware you need a GNU/Linux, BSD or macOS system (case sensitive filesystem required). Cygwin is unsupported because of the lack of a case sensitive file system.
Requirements
You need the following tools to compile OpenWrt, the package names vary between distributions. A complete list with distribution specific packages is found in the Build System Setup documentation.
binutils bzip2 diff find flex gawk gcc-6+ getopt grep install libc-dev libz-dev
make4.1+ perl python3.8+ rsync subversion unzip which
Quickstart
-
Run
./scripts/feeds update -ato obtain all the latest package definitions defined in feeds.conf / feeds.conf.default -
Run
./scripts/feeds install -ato install symlinks for all obtained packages into package/feeds/ -
Run
make menuconfigto select your preferred configuration for the toolchain, target system & firmware packages. -
Run
maketo build your firmware. This will download all sources, build the cross-compile toolchain and then cross-compile the GNU/Linux kernel & all chosen applications for your target system.
Related Repositories
The main repository uses multiple sub-repositories to manage packages of
different categories. All packages are installed via the OpenWrt package
manager called opkg. If you're looking to develop the web interface or port
packages to OpenWrt, please find the fitting repository below.
-
LuCI Web Interface: Modern and modular interface to control the device via a web browser.
-
OpenWrt Packages: Community repository of ported packages.
-
OpenWrt Routing: Packages specifically focused on (mesh) routing.
-
OpenWrt Video: Packages specifically focused on display servers and clients (Xorg and Wayland).
Support Information
For a list of supported devices see the OpenWrt Hardware Database
Documentation
Support Community
- Forum: For usage, projects, discussions and hardware advise.
- Support Chat: Channel
#openwrton oftc.net.
Developer Community
- Bug Reports: Report bugs in OpenWrt
- Dev Mailing List: Send patches
- Dev Chat: Channel
#openwrt-develon oftc.net.
License
OpenWrt is licensed under GPL-2.0