Felix Fietkau
e0e11b78f7
On an EHT BSS or an AP MLD with sae, psk3, sae-mixed or psk3-mixed, the RSNE Override 2 element carries SAE-EXT-KEY and GCMP-256 (CCMP without phy support). An explicit sae_ext_key 1 and gcmp256 1 also put both items into the RSNE, and the element stayed as a duplicate. A configuration that asks for an RSNE with AKM 24 and GCMP-256 and an RSNXE only sets sae_ext_key 1 and gcmp256 1. The Beacon then had an RSNO2E and an RSNXOE in addition. A duplicate RSNO2E adds nothing. A client sees both items in the RSNE, and the RSNE meets WPA3 Specification v3.5 2.5 items 4 and 5. Build the element only when the RSNE lacks its AKM or its pairwise cipher. Without an RSNO2E, hostapd writes no RSNXOE either (wpa_auth_gen_wpa_ie()). The default keeps the element as before, with the client fixes of commitsfc652db52aand5e067465ff, and so does a BSS with one of the two options. One exception: without phy support for GCMP-256, the element carries SAE-EXT-KEY and CCMP, which an RSNE with sae_ext_key 1 already offers, so that BSS sends no element. 0 still keeps an item out of both elements. sae-compat keeps its own elements. On an AP MLD, the decision covers all links (ap.uc mld_rsno2()): WPA3 Specification v3.5 14.2 requires an identical RSNE Override 2 element on all links of an AP MLD that uses RSN overriding. The element goes only where the RSNE of every link offers both items. A psk2 or psk-mixed AP MLD has PSK in the RSNE of its 2.4 and 5 GHz links, so all its links keep the element, also the 6 GHz link, whose RSNE has SAE. An AP MLD of sae whose RSNE has both items on every link uses no RSN overriding. IEEE 802.11be-2024 12.6.2 then requires the same RSNE on every link except the AKM list and MFPR, and one common AKM. The links share SAE and SAE-EXT-KEY, also on a 6 GHz link. 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