Skip to content

luci-mod-network: add WiFi 7 (802.11be / EHT) advanced configuration options - #8461

Open
prokowsoftware wants to merge 1 commit into
openwrt:masterfrom
prokowsoftware:luci-mod-network/wifi7-eht-options
Open

prokowsoftware wants to merge 1 commit into
openwrt:masterfrom
prokowsoftware:luci-mod-network/wifi7-eht-options

Conversation

@prokowsoftware

Copy link
Copy Markdown

Summary

PR #7302 (merged Oct 2024) added basic 802.11be mode selection (EHT htmodes) but did not expose advanced EHT-specific configuration options in the UI. This PR adds the missing options.

New options in the Advanced tab (radio device):

  • Disable EHT (802.11be) (disable_eht) — fall back to 802.11ax (WiFi 6 / HE)
  • Punctured Channel Bitmap (punct_bitmap) — bitmask of 20 MHz sub-channels to exclude; shown only for EHT160 and EHT320 modes
  • EHT SU Beamformer (eht_su_beamformer) — enable Single-User Transmit Beamformer capability
  • EHT MU Beamformer (eht_mu_beamformer) — enable Multi-User Transmit Beamformer capability

New option in the Wireless Security tab (interface):

  • SAE Password Element (sae_pwe) — selects the mechanism for SAE password element derivation (H&P, H2E, or both); H2E is required for WiFi 7 on 6 GHz; shown only for sae and sae-mixed encryption modes

Testing

Tested on a Radxa device with QCN9274 (802.11be) card running OpenWrt.

@castiel652

Copy link
Copy Markdown
Contributor
  • Disable EHT (802.11be) (disable_eht) — fall back to 802.11ax (WiFi 6 / HE)

Is this for client mode?

@prokowsoftware

Copy link
Copy Markdown
Author
  • Disable EHT (802.11be) (disable_eht) — fall back to 802.11ax (WiFi 6 / HE)

Is this for client mode?

No, disable_eht here is for AP mode only. In a typical deployment, the AP advertises its capabilities via beacons and the client adapts accordingly — so disabling EHT on the AP side is sufficient to fall back to 802.11ax (HE).

disable_eht is also supported by wpa_supplicant (client mode), but that use case is niche — it would only be needed if you want a station to avoid EHT even when the AP offers it (e.g. for debugging or compatibility testing). We didn't include it here as it's outside the scope of this PR.

@castiel652

Copy link
Copy Markdown
Contributor

No, disable_eht here is for AP mode only. In a typical deployment, the AP advertises its capabilities via beacons and the client adapts accordingly — so disabling EHT on the AP side is sufficient to fall back to 802.11ax (HE).

Okay so what's the point of this option?
Just select AX mode?

@prokowsoftware

Copy link
Copy Markdown
Author

Good question. The difference is subtle but useful in practice:

When you set htmode to an HE (WiFi 6) mode, you reconfigure the entire radio — channel width, beamforming, everything — for 802.11ax.

disable_eht lets you keep your EHT channel configuration (e.g. EHT320) but disable the 802.11be-specific features, so the AP falls back to HE for client associations. This is useful for:

  • Compatibility testing — verifying how your network behaves without EHT without changing the channel plan
  • Mixed environments — keeping a wide channel (320 MHz) while serving older clients that struggle with EHT negotiation
  • Debugging — isolating whether an issue is EHT-specific

If you want to permanently run in WiFi 6 mode, yes — just select an HE htmode. disable_eht is more of a diagnostic/transitional toggle.

@prokowsoftware

Copy link
Copy Markdown
Author

To be honest, the main motivation for this PR was sae_pwe. We were unable to properly configure our AP with WPA3/SAE — clients kept failing to associate — until we set sae_pwe=2 (H&P + H2E). Without this option exposed in the UI, it required manual UCI editing every time.

The EHT options came along naturally as we were already working with WiFi 7 hardware (QCN9274) and the wireless configuration page.

@prokowsoftware

Copy link
Copy Markdown
Author

We are also waiting for a newer kernel in OpenWrt (6.12+) to properly support MLO (Multi-Link Operation). Once that lands in a stable release, we plan to extend this with MLO configuration options as well.

@castiel652

Copy link
Copy Markdown
Contributor
  • Mixed environments — keeping a wide channel (320 MHz) while serving older clients that struggle with EHT negotiation

320MHz is EHT only.

until we set sae_pwe=2 (H&P + H2E).

Which version of OpenWrt are you using?
AFAIK this is the default since 22.03.

@systemcrash

Copy link
Copy Markdown
Contributor

And the additional options are available in the wifi scripts?

@Neustradamus

Copy link
Copy Markdown

@prokowsoftware: Nice work, thanks!

Have you seen recent @castiel652 and @systemcrash comments?

@prokowsoftware

Copy link
Copy Markdown
Author

Thanks for the review, @castiel652 and @systemcrash!


320MHz is EHT only.

You're correct, and thank you for the correction. 320 MHz channel width is defined exclusively in IEEE 802.11be (EHT) - there is no 802.11ax (HE) equivalent. Using disable_eht with EHT320 would force the AP to fall back to 160 MHz at most for HE associations. That part of my description was inaccurate.

The realistic use cases for disable_eht are:

  • Keeping an EHT80/EHT160 channel plan while temporarily forcing 802.11ax associations (e.g., compatibility testing without changing the channel width)
  • Isolating whether a connectivity issue is EHT-specific

AFAIK sae_pwe is the default since 22.03.

Even if hostapd's compiled-in default is correct, the option was not exposed in the LuCI UI - so users had no way to see what value was in effect or change it without manual UCI editing.

In our specific case (OpenWrt 24.10, QCN9274, 6 GHz), client associations were failing with WPA3/SAE until we explicitly set sae_pwe 2 via UCI. Whether that was a default issue or something hardware/driver-specific, having the option visible in the UI makes it debuggable and explicit - which is useful regardless of the default.

This PR targets OpenWrt 24.10, where the EHT htmodes were introduced in #7302.


And the additional options are available in the wifi scripts?

Yes - all five options map to hostapd configuration keys that are handled by OpenWrt's mac80211.sh wireless scripts in 24.10:

UCI option hostapd config key
disable_eht disable_eht
punct_bitmap punct_bitmap
eht_su_beamformer eht_su_beamformer
eht_mu_beamformer eht_mu_beamformer
sae_pwe sae_pwe

We tested disable_eht, punct_bitmap, and sae_pwe on a Radxa device with QCN9274 (802.11be) running OpenWrt 24.10. If any of these are missing from the wireless scripts for other branches, that would be a separate issue in openwrt/openwrt.

@castiel652

Copy link
Copy Markdown
Contributor
  • Keeping an EHT80/EHT160 channel plan while temporarily forcing 802.11ax associations (e.g., compatibility testing without changing the channel width)

Use HE80/HE160?????

In our specific case (OpenWrt 24.10, QCN9274, 6 GHz), client associations were failing with WPA3/SAE until we explicitly set sae_pwe 2 via UCI. Whether that was a default issue or something hardware/driver-specific, having the option visible in the UI makes it debuggable and explicit - which is useful regardless of the default.

You should check the hostapd conf file

This PR targets OpenWrt 24.10, where the EHT htmodes were introduced in #7302.

No. This PR targets master branch. Check again.

Yes - all five options map to hostapd configuration keys that are handled by OpenWrt's mac80211.sh wireless scripts in 24.10:

Are you sure about the first four options?

@systemcrash

Copy link
Copy Markdown
Contributor

Is this for 24.10 only? ( meaning that 25.12 works fine? )

@prokowsoftware

Copy link
Copy Markdown
Author

@systemcrash @castiel652 — thanks for the continued discussion!

To answer your question directly: we're planning to test the latest OpenWrt (25.x) this week. Our changes were developed and tested against 24.10.2, so we haven't yet verified whether they're required on the latest tree or whether some of the issues we encountered (particularly the sae_pwe default and EHT-related UI behavior) are already addressed there.

We'll report back once we've had a chance to run through it on current master.

@systemcrash

Copy link
Copy Markdown
Contributor

If this works against 25.12 and master (where it should always be tested first) then it can go in.

@openwrt-ai openwrt-ai left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed 1 new commit; 1 inline issue found (frontend-only EHT options with no backend consumer on master).


Generated by Claude Code

Comment on lines +1042 to 1059
o = ss.taboption('advanced', form.Flag, 'disable_eht', _('Disable EHT (802.11be)'), _('Disable IEEE 802.11be (WiFi 7 / EHT) operation and fall back to 802.11ax (WiFi 6 / HE).'));
o.rmempty = true;

o = ss.taboption('advanced', form.Value, 'punct_bitmap', _('Punctured Channel Bitmap'), _('Bitmask of 20 MHz sub-channels to exclude (puncture) in the operating channel. Each bit represents one 20 MHz sub-channel; setting a bit to 1 disables that sub-channel. Applies only to EHT160 and EHT320 modes.'));
o.datatype = 'range(0,65535)';
o.placeholder = '0';
o.rmempty = true;
o.depends('htmode', 'EHT160');
o.depends('htmode', 'EHT320');

o = ss.taboption('advanced', form.Flag, 'eht_su_beamformer', _('EHT SU Beamformer'), _('Enable IEEE 802.11be (WiFi 7) Single-User Transmit Beamformer capability.'));
o.default = '1';
o.rmempty = true;

o = ss.taboption('advanced', form.Flag, 'eht_mu_beamformer', _('EHT MU Beamformer'), _('Enable IEEE 802.11be (WiFi 7) Multi-User Transmit Beamformer capability.'));
o.default = '1';
o.rmempty = true;
}

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Frontend-only options with no backend consumer on master. None of disable_eht, punct_bitmap, eht_su_beamformer, or eht_mu_beamformer are read by the wifi-scripts in openwrt/openwrt. The ucode hostapd generator passes options through an explicit allow-list, and the EHT branch only forwards ieee80211be / eht_oper_chwidth / eht_oper_centr_freq_seg0_idx: https://github.com/openwrt/openwrt/blob/f37476a856ee67e75e3b9c9a24b6ba97350e26bc/package/network/config/wifi-scripts/files-ucode/usr/share/ucode/wifi/hostapd.uc#L450-L457 — the four names above appear nowhere in files-ucode/ or in the legacy files/lib/netifd/hostapd.sh, and there are no matching entries in wireless.wifi-device.json. As written, setting these in the UI will silently do nothing on current master.

For contrast, the HE equivalents he_su_beamformer / he_mu_beamformer are both declared in the device schema and explicitly appended in the HE branch (hostapd.uc L436), which is the pattern these new EHT options would need to follow on the backend side.

The PR body states these map to hostapd keys "in 24.10", but per the discussion thread the change must work against master/25.x. Either the corresponding openwrt/openwrt wifi-scripts support needs to land first (and be referenced here as a dependency), or these four options should be dropped from this PR. sae_pwe is unaffected — it is genuinely consumed. Which daemon/script is expected to read these four on master?


Generated by Claude Code

@openwrt openwrt Bot added the not following guidelines Pull request does not follow formatting guidelines label Jul 8, 2026
@prokowsoftware
prokowsoftware force-pushed the luci-mod-network/wifi7-eht-options branch from d01628d to a5f493f Compare July 11, 2026 16:43

@openwrt-ai openwrt-ai left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed 1 new commit; no new issues found. The head commit is a rebase of the previously reviewed commit onto a newer base with identical file contents (no code changes since the last review).


Generated by Claude Code

Comment on lines +2205 to +2206
o.depends('encryption', 'sae');
o.depends('encryption', 'sae-mixed');

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sae-compat is missing here: the backend applies sae_pwe to psk-sae-compat too (ap.uc:116-124),`` and the neighbouring SAE options (gcmp256, `sae_ext_key`) already list it.

Suggested change
o.depends('encryption', 'sae');
o.depends('encryption', 'sae-mixed');
o.depends('encryption', 'sae');
o.depends('encryption', 'sae-mixed');
o.depends('encryption', 'sae-compat');

Generated by Claude Code

o.value('0', _('Hunting-and-Pecking (H&P) only'));
o.value('1', _('Hash-to-Element (H2E) only'));
o.value('2', _('H&P and H2E (recommended for WiFi 7 / 6 GHz)'));
o.default = '2';

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A ListValue with default = '2' writes sae_pwe=2 on the next save, which overrides the backend's band-dependent default of 1 (H2E only) on 6 GHz (ap.uc:119-123)`` and the PPSK exemption. Add an empty "automatic" entry and make it the default, so nothing gets written unless the user picks a value.


Generated by Claude Code

…options

Add advanced wireless configuration options for IEEE 802.11be (WiFi 7 /
EHT) to the network wireless view:

- disable_eht: allow falling back to 802.11ax (HE) operation
- punct_bitmap: preamble puncturing bitmap for EHT160/EHT320 modes
- eht_su_beamformer / eht_mu_beamformer: SU/MU transmit beamformer
  capabilities
- sae_pwe: SAE password element derivation mechanism (H&P / H2E), with
  H2E required for WiFi 7 (802.11be) on the 6 GHz band

These map to the corresponding hostapd options and are exposed under the
advanced and encryption tabs of the wireless configuration.

Signed-off-by: Daniel Meyer <prokowsoftware@gmail.com>
@prokowsoftware
prokowsoftware force-pushed the luci-mod-network/wifi7-eht-options branch from b6408be to 7e3bece Compare November 13, 2026 15:34
@openwrt openwrt Bot removed the not following guidelines Pull request does not follow formatting guidelines label Nov 13, 2026
@prokowsoftware

Copy link
Copy Markdown
Author

Thanks everyone for the review. An honest status update:

This work was developed and tested against 24.10.2 on a Radxa board with a QCN9274 (802.11be) radio. The project it was part of has since been cancelled and we've had to return the hardware, so I can no longer verify the options against master / 25.12 as @systemcrash asked.

The formality check is now fixed — author and Signed-off-by use a real address.

I don't want to block this indefinitely. If someone with WiFi 7 hardware is able to confirm the backend wiring (mac80211.sh) on master, I'm happy for this to be picked up or taken over. The sae_pwe option in particular stands on its own regardless of the EHT bits. Otherwise, feel free to close — I'd rather be upfront than leave an untested PR hanging.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants