Felix Fietkau
5fe8fade02
A subscriber that reports the BSS colours of a radio needs three fields: the BSS Color subfield and the Partial BSS Color subfield that the radio transmits, and the colours of the OBSSs that the AP identified itself or learnt from the BSS Color Collision reports of its stations. get_status named the colour, as -1 while BSS Color is disabled, and neither of the others. hostapd kept its colours in use per BSS, and each collision event replaced them. It also added the colour of a BSS Color In Use report, which names a colour a station uses with a peer (IEEE Std 802.11-2024 11.21.2.8), not an OBSS colour. 174-ap-keep-the-obss-colors-of-a-radio keeps two sets per radio: - the OBSS colours, which the kernel's collision events and the BSS Color Collision reports of stations add to. A colour leaves the set 60 s after an event named it, or 130 s after a report did (the longest dot11BSSColorCollisionSTAPeriod, 120 s, plus a 10 s margin), and the ageing pauses while BSS Color is disabled; - the colours of BSS Color In Use reports, held per station until a report of colour 0 or until the station leaves. A colour change picks a colour outside both sets. get_status now adds, beside bss_color, at the top level and in each entry of the links of an AP MLD: - he_bss_color: the BSS Color subfield of the HE Operation element. It keeps the colour while BSS Color is disabled (IEEE Std 802.11-2024 26.11.4); bss_color keeps -1 then; - bss_color_partial: he_bss_color_partial of the radio; - bss_colors_in_use: the OBSS colours of the radio, 1 to 63. The colours of BSS Color In Use reports are not among them. On mt76 the kernel's collision events name the colliding colour only: mt7996 does not detect collisions itself, and mac80211 (ieee80211_rx_check_bss_color_collision()) reports an OBSS whose colour equals the BSS's own. Other OBSS colours reach the set only through the BSS Color Collision reports of stations. The colours are a list rather than the 64-bit bitmap, because a blobmsg int64 with bit 63 set reads as a negative number in ucode and JSON. 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