summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Add vendor attributes for forcing MLO power save and STR TXHEADpendingmainGururaj Pandurangi2023-05-041-0/+19
| | | | | | | | Add vendor attributes for EHT testbed STA configuration. This includes enabling STR MLMR mode and forcing power save on active MLO links for a defined number of beacon periods. Signed-off-by: Gururaj Pandurangi <quic_panduran@quicinc.com>
* Add vendor attributes for EHT OM control, EMLSR padding delayGururaj Pandurangi2023-05-041-9/+57
| | | | | | | | | | | Add vendor attributes related to MLO and EMLSR mode capability configuration for EHT testbed STA. It includes EHT OM control support and EMLSR padding delay configuration. Also, generalise the naming of HE OMI control enumeration to OMI control as it now consists of both HE and EHT OMI control fields. Signed-off-by: Gururaj Pandurangi <quic_panduran@quicinc.com>
* tests: WPA2-EAP AP with PMF required and EAPOL-LogoffJouni Malinen2023-05-041-0/+68
| | | | Signed-off-by: Jouni Malinen <quic_jouni@quicinc.com>
* Do not disconnect EAPOL-Logoff before authenticationJouni Malinen2023-05-046-24/+49
| | | | | | | | | | | | | | | | | | | | Some station devices are apparently sending the EAPOL-Logoff message in some cases before the initial authentication for WPA2/WPA3-Enterprise. hostapd would have forced a "post EAP-Failure" disconnection in 10 ms for such cases while still allowing the EAP authentication to try to complete. This is not ideal and could result in interoperability issues, so skip the forced disconnection in the particular case where the EAPOL-Logoff message is received before the first authentication is completed. In addition, disconnect the STA without starting new EAP authentication and the 10 ms delay if an EAPOL-Logoff message is received after authentication has been completed successfully. This results in cleaner behavior by avoiding the extra start of a new EAP authentication in a case where the STA is going to be disconnected shortly. Signed-off-by: Jouni Malinen <quic_jouni@quicinc.com>
* wpa_supplicant: Skip scan before starting a BSS in AP modeJintao Lin2023-04-281-1/+2
| | | | | | | | | When starting a new BSS as AP mode, the network configs have been passed in from the BSS config. There is no need to scan before creating a new BSS. Reuse connect_without_scan structure member to bypass scan when the mode is WPAS_MODE_AP. Signed-off-by: Jintao Lin <jintaolin@chromium.org>
* wpa_supplicant: Fix compiling without IEEE8021X_EAPOLNick Hainke2023-04-281-0/+2
| | | | | | | | | | | | | | | | | If IEEE8021X_EAPOL is not defined wpa_supplicant will not compile with following error: events.c: In function 'wpa_supplicant_connect': events.c:1827:14: warning: implicit declaration of function 'eap_is_wps_pbc_enrollee' [-Wimplicit-function-declaration] 1827 | if ((eap_is_wps_pbc_enrollee(&ssid->eap) && | ^~~~~~~~~~~~~~~~~~~~~~~ events.c:1827:43: error: 'struct wpa_ssid' has no member named 'eap' 1827 | if ((eap_is_wps_pbc_enrollee(&ssid->eap) && | ^~ Add ifdef statements around the calling function to fix the issue. Signed-off-by: Nick Hainke <vincent@systemli.org>
* Add missing driver entries to wpa_supplicant documentationBenjamin Poirier2023-04-282-0/+16
| | | | | | | There are possible more entries missing but I added only the ones I was actually able to build. Signed-off-by: Benjamin Poirier <bpoirier@nvidia.com>
* DPP: Remove argument requirement for DPP push button commandAndrew Pope2023-04-281-1/+1
| | | | | | | | | | The hostapd_cli command to initiate DPP push button mode mandates at least one argument to be provided. Arguments provided to the command are used to optionally supply configuration options when running in this mode. They are not strictly required for DPP push button mode to start. This patch removes the min requirement check on the command. Signed-off-by: Andrew Pope (andrew.pope@morsemicro.com)
* Add vendor attributes for MLO link active, EMLSR entry/exitGururaj Pandurangi2023-04-281-0/+24
| | | | | | | | Add vendor attributes related to MLO and EMLSR mode capability configuration for EHT DUT. This includes forcing active MLO links and invoking EMLSR mode entry or exit. Signed-off-by: Gururaj Pandurangi <quic_panduran@quicinc.com>
* tests: Additional 6 GHz band ACS coverageJouni Malinen2023-04-261-5/+22
| | | | Signed-off-by: Jouni Malinen <quic_jouni@quicinc.com>
* tests: Update regulatory database to VMsJouni Malinen2023-04-261-0/+0
| | | | | | | Update the wireless-regdb database to the wireless-regdb.git version of 2023-02-13. Signed-off-by: Jouni Malinen <quic_jouni@quicinc.com>
* Rename VHT elements to match the standardJouni Malinen2023-04-266-16/+16
| | | | | | | | | | Some of the information elements added in IEEE Std 802.11ax-2013 for VHT purposes have since then been taken into use for other cases and renamed to remove the "VHT" prefix in the standard. Update the defines for those elements in the implementation to match the names used in the current standard. Signed-off-by: Jouni Malinen <quic_jouni@quicinc.com>
* hostapd: Support channel switch to 320 MHz channelsRamya Gnanasekar2023-04-264-2/+40
| | | | | | | | Add validatation of center frequency, and filling of appropriate bandwidth in the channel switch wrapper when the channel switch is done to a 320 MHz channel. Signed-off-by: Ramya Gnanasekar <quic_rgnanase@quicinc.com>
* Fix file mode bitsJouni Malinen2023-04-261-0/+0
| | | | | | | The execute bits were not supposed to be added to a source code file. Fixes: 927dbfb453ed ("Fix 40 MHz channel bringup with ACS on the 6 GHz band") Signed-off-by: Jouni Malinen <quic_jouni@quicinc.com>
* tests: HE with ACS on 6 GHz using a 40 MHz channelJouni Malinen2023-04-251-0/+51
| | | | Signed-off-by: Jouni Malinen <quic_jouni@quicinc.com>
* Select 6 GHz mode correctly for ACS casesJouni Malinen2023-04-251-6/+21
| | | | | | | | Use the op_class configuration to determine whether to select the 5 GHz or 6 GHz mode for ACS. Without this, the first mode (5 GHz in most cases) would have been selected regardless of the op_class value. Signed-off-by: Jouni Malinen <quic_jouni@quicinc.com>
* Fix 40 MHz channel bringup with ACS on the 6 GHz bandHari Chandrakanthan2023-04-251-4/+3
| | | | | | | | | | | | | | | | | | When AP is brought up in HE40/EHT40 with ACS, the AP comes up with 20 MHz bandwidth. It is expected to come up with 40 MHz bandwidth. conf->secondary_channel does not hold the correct value and it leads to choosing 20 MHz in hostapd_set_freq_params(). conf->secondary_channel is filled using the hostapd config he_oper_centr_freq_seg0_idx. When AP is configured to use ACS, the hostapd config he_oper_centr_freq_seg0_idx is not valid as the channel is not known during bring up. So using the config he_oper_centr_freq_seg0_idx to fill the conf->secondary_channel does not work with ACS. Use op_class to determine the bandwidth and based on the bandwidth fill the conf->secondary_channel to address this ACS case. Signed-off-by: Hari Chandrakanthan <quic_haric@quicinc.com>
* Allow MLO disabled connection to legacy open/WPA2-Personal-only AP MLDsVeerendranath Jakkam2023-04-252-13/+34
| | | | | | | | | | | | | | | | | | | | | | | | | | wpa_supplicant was skipping MLD APs from network selection when the AP advertise legacy open, WPA2-Personal-only (PSK without SAE), or PMF disabled. However, there are already some early Wi-Fi 7 APs in the market which advertise legacy open, WPA2-Personal-only, or PMF disabled even though these combinations are unlikely to be allowed for Wi-Fi 7 in the end. To avoid connectivity issues with such APs, allow stations to connect with MLO disabled when an AP MLD is detected to advertise legacy open, WPA2-Personal-only (PSK without SAE), or PMF disabled. This reverts commit 7d8b96dcfdbb ("wpa_supplicant: Apply same restrictions for MLD as for 6 GHz BSS") except WEP and TKIP checks, i.e., AP MLDs which advertise only WEP or TKIP are still skipped from network selection. For the SME-in-wpa_supplicant case, skip configuring MLD parameters to the driver if the STA can connect only in legacy open, WPA2-Personal-only, or PMF disabled mode. For the SME-in-driver case, it is the driver's responsibility to initiate connection with MLO disabled with such APs. Signed-off-by: Veerendranath Jakkam <quic_vjakkam@quicinc.com>
* Update AP RSNE/RSNXE to RSN state machine on driver-selected BSS casesJouni Malinen2023-04-251-3/+3
| | | | | | | | | | | | | | | | | The driver-initiated BSS selection case and the "Network configuration found for the current AP" case ended up clearing the RSN state machine information on AP RSNE/RSNXE. That could result in incorrect behavior if some key management operations depended on accurate information. For example, this could result in not deriving the KDK as part of the PTK derivation and failing to complete 4-way handshake if both the AP and the STA indicated support for Secure LTF. If the scan results for the selected BSS are available, use those to update the RSN state machine AP RSNE/RSNXE similarly to the way this is done with wpa_supplicant selects the BSS instead of clearing that information in the RSN state machine. Signed-off-by: Jouni Malinen <quic_jouni@quicinc.com>
* tests: KDK derivation based on Secure LTF capabilityJouni Malinen2023-04-252-3/+98
| | | | | | | | This adds more production-like testing coverage for KDK derivation. Both SAE and OWE transition mode are covered. The latter has some corner cases that did not work correctly previously. Signed-off-by: Jouni Malinen <quic_jouni@quicinc.com>
* OWE: Update transition mode information on selecting a new BSSJouni Malinen2023-04-251-0/+12
| | | | | | | | | | | | | | | It is possible for a new BSS entry to be added for the hidden-SSID-OWE-BSS when running a new scan after having previously learned the hidden SSID during a previous OWE connection attempt. That new entry would not necessarily have the WPA_BSS_OWE_TRANSITION flag set and that would result in not being able to recognize the appropriate OWE profile when checking the association event against the transition mode configuration. Fix this by updating the BSS entry for OWE transition mode information for the cases where this might happen. Signed-off-by: Jouni Malinen <quic_jouni@quicinc.com>
* Fix determining mode for 6 GHz band when using hw_mode=anyXinyue Ling2023-04-211-1/+5
| | | | | | | | | | | When 6 GHz band is specified and hw_mode parameter is set to any, hostapd_determine_mode() may determine the wrong mode because there are two hw modes (5 GHz and 6 GHz) with HOSTAPD_MODE_IEEE80211A. This will cause 6 GHz AP to fail to start. Fix this by adding a check similar to the changes in commit 99cd453720d6 ("hw_feature: Correctly select mode in case of the 6 GHz band") into hostapd_determine_mode(). Signed-off-by: Jouni Malinen <quic_jouni@quicinc.com>
* Add support to fetch link layer stats per MLO linkShivani Baranwal2023-04-201-21/+153
| | | | | | | | | | | | | | | | | | | IEEE 802.11be enables multiple links between STA and AP. Each of the link has its own set of statistics. Add additional attributes required to fetch link layer statistics per MLO link. For MLO connection, per MLO link statistics will be sent with the new attribute QCA_WLAN_VENDOR_ATTR_LL_STATS_MLO_LINK. Also, cumulative statistics of all the MLO links will be sent outside QCA_WLAN_VENDOR_ATTR_LL_STATS_MLO_LINK to be compatible with legacy user space. For non-MLO connection, the statistics will be sent without being nested inside QCA_WLAN_VENDOR_ATTR_LL_STATS_MLO_LINK attribute. Co-authored-by: Veerendranath Jakkam <quic_vjakkam@quicinc.com> Signed-off-by: Veerendranath Jakkam <quic_vjakkam@quicinc.com> Signed-off-by: Shivani Baranwal <quic_shivbara@quicinc.com>
* Fix vendor attribute numbering and relocate attribute accordinglyShivani Baranwal2023-04-201-2/+3
| | | | | | | | | | The attributes QCA_WLAN_VENDOR_ATTR_LL_STATS_PAD and QCA_WLAN_VENDOR_ATTR_LL_STATS_IFACE_NF_CAL_VAL were allocated the same attribute number in error. QCA_WLAN_VENDOR_ATTR_LL_STATS_PAD attribute is known to not be used; thus, it is safe to be renumbered. Fixes: 1491fc64a820 ("Define QCA vendor per-enum 64-bit pad attributes") Signed-off-by: Shivani Baranwal <quic_shivbara@quicinc.com>
* Add a vendor specific roam status of background scan abortChunquan Luo2023-04-201-0/+3
| | | | | | | | When user space triggers a scan, the firmware aborts background scan, and uses the roam status QCA_ROAM_FAIL_REASON_CURR_AP_STILL_OK instead of "Invalid roam failures reason". Signed-off-by: Chunquan Luo <quic_chunquan@quicinc.com>
* Update QCA LL_STATS vendor commandAditya Kodukula2023-04-191-15/+68
| | | | | | | Define bitmap values used by LL_STATS vendor command and update the corresponding kernel documentation. Signed-off-by: Jouni Malinen <quic_jouni@quicinc.com>
* SAE: Fix expected AP MLD address info in a debug printVeerendranath Jakkam2023-04-191-1/+2
| | | | | | | | Print correct expected AP MLD address information when the AP MLD address validation fails in Authentication frames during external authentication. Signed-off-by: Veerendranath Jakkam <quic_vjakkam@quicinc.com>
* MLD STA: Do not fail on unknown IEs in Authentication framesVeerendranath Jakkam2023-04-191-2/+2
| | | | | | | | | | | Fail MLD address validation only if Authentication frames IE parsing actually failed, i.e., ignore all unknown IEs. This is needed to avoid authentication failure when the Authentication frames include IEs which are not handled by ieee802_11_parse_elems(), e.g., AKM Suite Selector IE. Signed-off-by: Veerendranath Jakkam <quic_vjakkam@quicinc.com>
* hostapd: Restore the flow of set beacon and WPA key initXin Deng2023-04-191-3/+3
| | | | | | | | | | | | hostapd start AP flow changed in commit 931e5d4f9e2e. However, that could cause a regression in a legacy AP driver where the set key operation for GTK, IGTK, and BIGTK before AP start (set beacon) would cause the driver to ignore the key set command. Restore the flow of the set beacon and WPA key init operations to make sure drivers can receive and set group keys correctly. Fixes: 931e5d4f9e2e ("mbssid: Configure all BSSes before beacon setup") Signed-off-by: Jouni Malinen <quic_jouni@quicinc.com>
* Export wpa_supplicant config item 'he' for external configurationChaoli Zhou2023-04-192-1/+2
| | | | | | | | | Export the "he" network profile item to be configurable from external client side, like wpa_cli or NetworkManager. This follows the earlier changes to allow the previously internal-only parameter (e.g., vht) to be used for additional purposes for AP mode. Signed-off-by: Chaoli Zhou <quic_zchaoli@quicinc.com>
* Allowed frequency list configuration for AP operationVeerendranath Jakkam2023-04-197-7/+94
| | | | | | | | | | | | Add support to configure the allowed frequency list for AP operation using a QCA vendor interface before NL80211_CMD_NEW_BEACON/ NL80211_CMD_START_AP. hostapd generates the allowed frequency list by intersecting user configured frequency list and all the frequencies advertised by the driver including disabled channels. If user doesn't specify allowed frequency list, all the frequencies advertised by the driver, including disabled channels, will be configured. Signed-off-by: Veerendranath Jakkam <quic_vjakkam@quicinc.com>
* tests: Update server and user certificates (2023)Jouni Malinen2023-04-1823-307/+315
| | | | | | | | At least some of the previous versions have expired, so need to re-sign these to avoid EAP test case failures. This contains updates from running tests/hwsim/auth_server/update.sh. Signed-off-by: Jouni Malinen <j@w1.fi>
* WMM: Advertise support for 16 PTKSA replay counters for non-AP STAJouni Malinen2023-04-188-5/+32
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | In theory, each device that supports WMM (or the IEEE 802.11 QoS for that matter) is expected to advertise how many replay counters it supports and the peer device is supposed to use that information to restrict the total number of different MSDU priorities (AC/UP) that might be used. In practice, this is not really done in deployed devices and instead, it is just assumed that everyone supports the eight different replay counters so that there is no need to restrict which MSDU priorities can be used. hostapd implementation of WMM has advertised support for 16 PTKSA replay counters from the beginning while wpa_supplicant has not had any code for setting the supported replay counter fields in RSNE, i.e., has left the value to 0 which implies that only a single replay counter is supported. While this does not really result in any real issues with deployed devices, this is not really correct behavior based on the current IEEE 802.11 standard and the WMM specification. Update wpa_supplicant to use similar design to the hostapd RSNE generation by setting the number of supported PTKSA replay counters to 16 whenever WMM is enabled. For now, this is done based on the association being for HT/VHT/HE/EHT and also based on the AP supporting WMM since it is much more likely for the local device to support WMM and eight replay counters (which can be indicated only with the value that implies support for 16 counters since there is no separate value for 8). Signed-off-by: Jouni Malinen <quic_jouni@quicinc.com>
* nl80211: Support for RNR elementsAloka Dixit2023-04-181-0/+22
| | | | | | | | | | | Add new nested netlink attribute, NL80211_ATTR_EMA_RNR_ELEMS, to send the reduced neighbor report (RNR) elements to the driver when EMA is enabled. This attribute includes the count of RNR elements and data at each index. While generating EMA beacons, the driver will include RNR group at a given index along with MBSSID group. The last element, if present, has RNR data common for all EMA beacons such as neighbor APs. Signed-off-by: Aloka Dixit <quic_alokad@quicinc.com>
* RNR: Add elements by default for EMA APAloka Dixit2023-04-184-22/+136
| | | | | | | | | | | | | | | | | | | | As per IEEE Std 802.11ax-2021, 11.1.3.8.3 Discovery of a nontransmitted BSSID profile, an EMA AP that transmits a Beacon frame carrying a partial list of nontransmitted BSSID profiles should include in the frame a Reduced Neighbor Report element carrying information for at least the nontransmitted BSSIDs that are not present in the Multiple BSSID element carried in that frame. Add this support by splitting the reduced neighbor report (RNR) in as many elements as the number of multiple BSSID elements. Each RNR element excludes the non-transmitting profiles already included in the MBSSID element at the same index. If present, the last additional group will have the data common for all EMA beacons such as neighbor AP information gathered through neighbor reports. The hwsim test case he_ap_ema demonstrates this support. Signed-off-by: Aloka Dixit <quic_alokad@quicinc.com>
* RNR: Skip interfaces on the same radio for MBSSIDAloka Dixit2023-04-181-2/+4
| | | | | | | | Do not include interfaces on the same radio in reduced neighbor report elements (RNR) as multiple BSSID elements from the same management frame already include these if MBSSID feature is enabled. Signed-off-by: Aloka Dixit <quic_alokad@quicinc.com>
* Sync with wireless-next.git include/uapi/linux/nl80211.hJouni Malinen2023-04-061-1/+23
| | | | | | This brings in nl80211 definitions as of 2023-03-30. Signed-off-by: Jouni Malinen <j@w1.fi>
* Add QCA vendor feature flag for allowed frequency listVeerendranath Jakkam2023-04-031-0/+4
| | | | | | | Add a vendor feature flag for the driver to indicate support for allowed frequency configuration in AP mode. Signed-off-by: Veerendranath Jakkam <quic_vjakkam@quicinc.com>
* Add QCA vendor interface to get connected channels utilizationAiny Kumari2023-04-031-0/+17
| | | | | | | | Add a new vendor command to trigger computation of connected channel statistics such as channel utilization in STA mode. Signed-off-by: Ainy Kumari <quic_ainykuma@quicinc.com> Signed-off-by: Veerendranath Jakkam <quic_vjakkam@quicinc.com>
* Add QCA vendor attribute to configure list of allowed frequencies for APVeerendranath Jakkam2023-04-031-0/+27
| | | | | | | | | | | | Define a new attribute QCA_WLAN_VENDOR_ATTR_CONFIG_AP_ALLOWED_FREQ_LIST to configure the full list of allowed frequencies for the AP operation. The configuration is valid only from the next BSS start until the BSS is stopped. The drivers shall filter out channels on top of this list of channels based on regulatory or other constraints. This can be used to specify user's choice of frequencies, allowed list of channels with static puncturing feature, etc. Signed-off-by: Veerendranath Jakkam <quic_vjakkam@quicinc.com>
* Add 40 and 80 MHz channels 165 and 173 for 5 GHz IBSS/meshSeevalamuthu Mariappan2023-03-291-4/+5
| | | | | | | | | Add the channels 165 and 173 in allowed channels for ht40_plus. Also add the allowed frequency 5825 (channel 165; channel center frequency index 171) for 80 MHz bandwidth. Signed-off-by: Seevalamuthu Mariappan <quic_seevalam@quicinc.com> Signed-off-by: Raj Kumar Bhagat <quic_rajkbhag@quicinc.com>
* 6 GHz: Fix secondary channel settingJouni Malinen2023-03-291-1/+1
| | | | | | | | | center_idx_to_bw_6ghz() does not return the bandwidth in MHz and as such, the check here against 20 (MHz) is never true. The returned value is greater than 0 for the over 20 MHz cases. Fixes: 15742566fd7c ("6 GHz: Fix operating class in Supported Operating Classes element") Signed-off-by: Jouni Malinen <quic_jouni@quicinc.com>
* Add 6 GHz channel validation during channel switchingAnilkumar Kolli2023-03-291-0/+20
| | | | | | | | | | | | | | | | | | | | The following command does not return FAIL, but it fails to update the beacon since the center frequency used in the command is not valid for 80 MHz bandwidth. hostapd_cli -i wlan0 chan_switch 5 6315 sec_channel_offset=1 \ center_freq1=6345 bandwidth=80 he Add condition check to validate the center frequency. Also, if user doesn't provide HE parameter in the hostapd_cli chan_switch command, by default HE should be enabled for 6 GHz frequency range. This is because, 6 GHz does not support legacy mode. Signed-off-by: Anilkumar Kolli <quic_akolli@quicinc.com> Co-developed-by: Aditya Kumar Singh <quic_adisi@quicinc.com> Signed-off-by: Aditya Kumar Singh <quic_adisi@quicinc.com>
* Set interface state as inactive if mesh bringup failsHari Chandrakanthan2023-03-291-0/+1
| | | | | | | | | | | | The STATUS command showed the interface state as SCANNING even if mesh bringup fails. This incorrect interface status can mislead scripts/applications that rely on interface status to bring up different type of virtual interfaces (AP/MESH) on a single radio. Fix this by setting the interface status as INACTIVE if mesh bringup fails. Signed-off-by: Hari Chandrakanthan <quic_haric@quicinc.com>
* Handle signal termination in hostapd_cli for all casesSai Pratyusha Magam2023-03-281-29/+42
| | | | | | | | | | | | | | hostapd_cli did not clean up the sockets and attachments to receive hostapd events when SIGTERM was used to terminate it in action script mode. Do proper cleanup by convering the action script processing functionality to use eloop similarly to the wpa_cli changes in commit 13f6f617eeca ("wpa_cli: Fix process termination in wpa_cli action mode case") and by registering the process termination signal handler for all cases instead of just for the interactive mode. Signed-off-by: Sai Pratyusha Magam <quic_smagam@quicinc.com>
* wlantest: MLO aware STA entry search for unprotected Data framesJouni Malinen2023-03-271-1/+5
| | | | | | | | | | | | Find a STA entry based on MLO affiliated link addresses for the case where an unprotected Data frame is being processed. This extends the changes in commit 228420e2d9a8 ("wlantest: Find a STA entry based on MLO affiliated link addresses") to cover the unencrypted case. This is needed in particular for the Null frames used for managing the power save state to avoid generating duplicate STA entries that can mess up key information for the following frames. Signed-off-by: Jouni Malinen <quic_jouni@quicinc.com>
* tests: Suite B 192-bit RSA with TLS 1.3Jouni Malinen2023-03-231-4/+25
| | | | Signed-off-by: Jouni Malinen <quic_jouni@quicinc.com>
* OpenSSL: Add TLS 1.3 signature algorithms for Suite BJouni Malinen2023-03-221-3/+17
| | | | | | | These are needed to allow the Suite B 192-bit negotiation to succeed when using TLS 1.3 (which is still disabled by default). Signed-off-by: Jouni Malinen <quic_jouni@quicinc.com>
* Add support to send 320 MHz bandwidth through vendor subcmdAiny Kumari2023-03-221-6/+2
| | | | | | | Extend QCA_WLAN_VENDOR_ATTR_CONFIG_CHANNEL_WIDTH to configure 320 MHz bandwidth to the driver/firmware. Signed-off-by: Ainy Kumari <quic_ainykuma@quicinc.com>
* EHT: Validate the puncturing bitmap for ACSAloka Dixit2023-03-171-1/+8
| | | | | | Validate the generated puncturing bitmap against non-OFDMA patterns. Signed-off-by: Aloka Dixit <quic_alokad@quicinc.com>
View Lorry Controller Status