diff options
author | Sultan Alsawaf <sultan@kerneltoast.com> | 2022-07-21 23:36:31 -0700 |
---|---|---|
committer | David Bauer <mail@david-bauer.net> | 2022-08-21 15:54:22 +0200 |
commit | 97213c733592349f152050dcb67299c37b68dfb6 (patch) | |
tree | a2067e75d235068ba3cebf545512a2302094e81d /target/linux | |
parent | ecd8f7e294a73d56906f7edcd8206ac6e304875c (diff) | |
download | upstream-97213c733592349f152050dcb67299c37b68dfb6.tar.gz upstream-97213c733592349f152050dcb67299c37b68dfb6.tar.bz2 upstream-97213c733592349f152050dcb67299c37b68dfb6.zip |
mac80211: parse the correct set of HE capabilities for AP mode
It is common for 802.11ax NICs to support more than just AP mode, which
results in there being a distinct set of HE capabilities for each mode. As
(bad) luck would have it, iw prints out info for each HE mode in sequential
order according to `enum nl80211_iftype`, and AP mode isn't always first.
As a result, the wrong set of HE capabilities can be parsed if an AP NIC
supports station (managed) mode or any other mode preceding AP mode, since
only the first set of HE capabilities printed by iw is parsed from awk's
output.
This has a noticeable impact on beamforming for example, since managed mode
usually doesn't have beamformer capabilities enabled, while AP mode does.
Hostapd won't be set up with the configs to enable beamformer capabilities
in this scenario, causing hostapd to disable beamforming to HE stations
even when it's supported by the AP.
Always parse the correct set of HE capabilities for AP mode to fix this.
This is achieved by trimming all of iw's output prior to the AP mode
capabilities, which ensures that the first set of HE capabilities are
always for AP mode.
Signed-off-by: Sultan Alsawaf <sultan@kerneltoast.com>
(cherry picked from commit f338f76a66a50d201ae57c98852aa9c74e9e278a)
Diffstat (limited to 'target/linux')
0 files changed, 0 insertions, 0 deletions