Felix Fietkau
137921ab08
The links of an AP MLD share one interface name. Each asked for the object of that name, the first link got it, and the others failed. The object, its subscribers, and the state a subscriber set through it belonged to that one link: - the object went away with that link, although other links remained, and a subscriber took the removal for the end of the AP MLD and of every station on it; - notify_response, the BSS Transition Management Query answer flag and the bans applied to that link only, while each link read its own; - bss_mgmt_enable and the rrm_nr methods changed the capabilities and the neighbor report database of that link only. Keep one object per AP MLD, from its first link to its last. A method runs on a link that is there: the AP MLD's first link once its setup has added it to the object, or, once the last link has left the AP MLD and before its BSS frees the object, a link the object still counts. A link is counted once. Notifications of every link go through it. notify_response, the BTM query answer and the bans are the AP MLD's, and every link reads them. bss_mgmt_enable, the implicit neighbor report enable of the rrm_nr methods and rrm_nr_set apply to every link, and a link that joins later takes the flags and the neighbor list set before. The methods that name a station act on the link that holds it: get_clients lists the stations of every link, a non-AP MLD once with the station of its association link, and rrm_beacon_req, rrm_lm_req and update_airtime find the station on any link, as del_client and bss_transition_request already did. They answered for the first link only, and after that link left the AP MLD, for another one. 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