Hauke Mehrtens
fc652db52a
Commita12cec9ea3("wifi-scripts: ucode: advertise SAE-EXT-KEY AKM alongside SAE") advertised the SAE-EXT-KEY AKM (00-0F-AC:24, SAE using a group-dependent hash, aka SAE-GDH) by default on every sae, sae-mixed and sae-compat BSS. WPA3 Specification v3.5 only makes this AKM mandatory when the BSS enables EHT or MLO (section 2.5, item 4); for HE and below it is merely recommended (sections 2.2 and 2.3). In practice the FT-SAE-EXT-KEY AKM (SAE-EXT-KEY combined with 802.11r), which gets added automatically once Fast Transition is enabled, keeps some clients from associating (a Samsung Galaxy Tab S10 FE) or makes them reboot shortly after connecting (a Poco X6). Plain SAE-EXT-KEY without FT was seen to work on the same tablet, but its interoperability is not well tested. Drop the fixed schema default and pick the default from the auth type in parse_encryption instead. Only default it on where it is both mandatory and safe to offer: on Compatibility mode (sae-compat) BSSes running an EHT htmode, which carry it in a separate RSN Override element that legacy clients ignore. Keep it off for WPA3-Personal (sae) and Transition (sae-mixed) mode, where it would sit in the main RSNE that a choking client cannot ignore, and off on non-EHT BSSes. An explicit 'option sae_ext_key 0/1' still overrides this per BSS. The SAE-EXT-KEY AKM in the sae-compat RSN Override 2 element now keys off config.sae_ext_key alone; the extra config.rsn_override_pairwise_2 guard is dropped, decoupling the AKM from the GCMP-256 pairwise cipher so each follows its own option. Fixes:a12cec9ea3("wifi-scripts: ucode: advertise SAE-EXT-KEY AKM alongside SAE") Assisted-by: Claude:claude-opus-4-8 Link: https://github.com/openwrt/openwrt/pull/24041 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
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