Arowa Suliman [Tue, 5 Nov 2024 05:36:11 +0000 (05:36 +0000)]
Check last scan SSIDs before triggering new scan for hidden network
Commit 92374d59d4ef ("Enhance select_network() to trigger new scans in
some cases") introduced a redundant scan when selecting a hidden network
that was previously scanned and found. This occurs because the code only
checks for the condition `(wpa_s->no_suitable_network ||
wpa_s->last_scan_external)`, which doesn't cover the case where the last
scan successfully found the hidden SSID.
Save the scanned SSIDs from the last scan and updates the condition to
check if the hidden SSID was included. If the hidden SSID is not found
in `last_scan_ssids`, the code checks if the SSID was found in earlier
scan results. If not, it triggers a new scan. If the SSID is found, a
new scan is avoided, resulting in faster connection times.
Jouni Malinen [Thu, 26 Dec 2024 22:19:33 +0000 (00:19 +0200)]
Handle CONFIG_NO_WPA for wpa_sm_has_ptk_installed()
There was no empty wrapper for wpa_sm_has_ptk_installed() for the
CONFIG_NO_WPA=y builds. The previously renamed wpa_sm_has_ptk() wrapper
was still in place even though it is not used anymore, so rename it to
cover this newer need.
Tim Small [Wed, 23 Oct 2024 16:35:02 +0000 (17:35 +0100)]
mka: Accept MKPDU sent to any multicast address
Improve MKPDU 802.1X conformance by not requiring the PAE group address
(01-80-C2-00-00-03) to be used as the destination, but instead, allowing
any multicast address to be used. IEEE Std 802.1X-2020, 11.11.2
(Validation of MKPDUs) disallows only individual addresses as the
destination address.
IEEE Sts 802.1X-2010 and 802.1X-2020 both specify that MKPDU packets
should be discarded if their destination address is "an individual
address". ieee802_1x_kay_mkpdu_validity_check() previously also rejected
all destination addresses other than 01:80:c2:00:00:03 "Nearest non-TPMR
Bridge group address" (in contradiction to its comments).
This restriction may be a carry-over from IEEE Std 802.1X-2004, but is
explicitly discouraged in the 2010 and 2020 revisions (see 11.1.1
(Destination MAC address) and its references).
The additional restriction prevented wpa_supplicant and hostapd from
participating in MACsec communication in environments such as
third-party ("supplier") layer 2 networks.
Jouni Malinen [Thu, 26 Dec 2024 18:30:23 +0000 (20:30 +0200)]
tests: Make ap_cipher_tkip_countermeasures_sta2 more robust
Work around a race condition between Michael MIC error report processing
on the AP from two STAs and the 4-way handshake that might get started,
but not necessarily completed, during that window.
Vinayak Yadawad [Fri, 13 Dec 2024 08:45:27 +0000 (14:15 +0530)]
OWE: Fix SSID comparison in transition mode case
ret_ssid is a pointer to a pointer to the SSID and as such, it needs to
be referenced once here for the comparison just like ret_ssid_len. This
was broken recently as a part of duplicated code removal.
Fixes: ddfed3f08473 ("OWE: Reduce code duplication in OWE element parsing") Signed-off-by: Vinayak Yadawad <vinayak.yadawad@broadcom.com>
Jouni Malinen [Thu, 26 Dec 2024 10:30:22 +0000 (12:30 +0200)]
OWE: Accept only BSS entries with an actual SSID for ROAM command
An AP in OWE transition mode shows up in the BSS table twice due to use
of the hidden SSID. Since roaming requires the SSID to be known, don't
select the BSS entry with an empty SSID to force the one with the actual
SSID to be used when using the ROAM command to roam between APs that
might use OWE transition mode.
Nicolas Escande [Mon, 29 Apr 2024 10:13:25 +0000 (12:13 +0200)]
hostapd: Respect obss_interval on 40 MHz intolerant disconnect
When an AP is configured for HT operation on 40 MHz but has overlapping
BSS on the secondary channel, it will fall back to 20 MHz only. Also a
40 MHz AP will downgrade to 20 MHz while at least one 40 MHz intolerant
STA is connected.
However, in the current code, on such an AP, we do not check the
obss_interval parameter to be set on the last 40 MHz intolerant STA
disconnect and instead, start a timer that will unconditionnaly and
immediately bring the AP to 40 MHz operation even if it had overlapping
BSS.
A similar case was addressed for the 20/40 MHz co-ex report earlier in
commit d027c7b118fe ("Fix 20/40 MHz co-ex report processing with
obss_interval=0"), but this other case that gets called whenever a STA
entry is removed needs to have similar constraint on starting the timer.
Signed-off-by: Nicolas Escande <nico.escande@gmail.com>
Jouni Malinen [Wed, 25 Dec 2024 17:11:11 +0000 (19:11 +0200)]
tests: Set obss_interval for the test that verifies return to 40 MHz
This is in preparation for changing hostapd to require obss_interval to
be set to allow the channel bandwidth to be increased from 20 MHz to 40
MHz on disassociation of the last 40 MHz intolerant STA.
P2P2: Report R2 information in P2P-DEVICE-FOUND event
Add PCEA capability information, supported PASN types, and bootstrap
methods in P2P-DEVICE-FOUND event. This is needed to be able to start
P2P2 pairing with the discovered peer.
Signed-off-by: Andrei Otcheretianski <andrei.otcheretianski@intel.com>
According to the Wi-Fi Direct spec draft, address 3 in unicast USD
frames shall be set to the P2P Device Address of the sender (i.e., this
differs from the Wi-Fi Aware specification). Fix it.
Signed-off-by: Andrei Otcheretianski <andrei.otcheretianski@intel.com>
According to the Wi-Fi Direct spec draft, address 3 in multicast USD
frames shall be set to wildcard BSSID (i.e., this differs from the Wi-Fi
Aware specification). Fix it.
Signed-off-by: Andrei Otcheretianski <andrei.otcheretianski@intel.com>
Kan-Ru Chen [Sun, 22 Dec 2024 23:42:33 +0000 (08:42 +0900)]
Send CTRL-EVENT-SIGNAL-CHANGE message to control interfaces only
The default logging level for the CTRL-EVENT-SIGNAL-CHANGE message
may be repeated many times and fill the log file or journal.
For example https://bugzilla.redhat.com/show_bug.cgi?id=2309148 and
the first few results from searching CTRL-EVENT-SIGNAL-CHANGE on the
web contain various complaints and workarounds.
Change the logging method to wpa_msg_ctrl to avoid sending frequent
messages to the syslog but still allow the message to be consumed by
control interface monitors.
Jouni Malinen [Sun, 22 Dec 2024 22:55:09 +0000 (00:55 +0200)]
tests: Split hostapd_oom_wpa2_eap_connect into multiple test cases
This test case could take a long time to execute and it can be easily
split into a set of test cases that each cover a smaller range of
iterations (50 each for now). This is more robust and more efficient for
parallel VMs.
Petr Štetiar [Wed, 18 Dec 2024 07:50:18 +0000 (07:50 +0000)]
hostapd: hostapd_cleanup_iface_partial: Fix hw_features use after free
Currently when the iface is being cleaned up, the
hostapd_free_hw_features() is called which frees the underlying
hw_features and the struct is being NULLed, but the num_hw_features
counter is not being reset, thus following commonly used access
constructs:
for (i = 0; i < iface->num_hw_features; i++)
acs_cleanup_mode(&iface->hw_features[i]);
This might then lead to use after free and hostapd for example might
crash during configuration reload on disabled interfaces:
So lets fix it by resetting the num_hw_features counter to 0, so the
code will not try to access the freed memory in hw_features struct.
Reported-by: Mohammed SI ALI <mohammed.siali@softathome.com> Tested-by: Houssem Dafdouf <houssem.dafdouf_ext@softathome.com> Signed-off-by: Petr Štetiar <ynezz@true.cz> Signed-off-by: Petr Štetiar <petr.stetiar@prplfoundation.org>
Vinayak Yadawad [Wed, 4 Dec 2024 09:13:59 +0000 (14:43 +0530)]
EAPOL: Fix PMK setting for driver-based FT-SHA384
Currently in eapol callback PMK update for FT is done wrongly with the
default PMK length even in case of SHA384. SHA384 needs longer 48-octet
PMK. Accordingly, fix the offset and length of the PMK that is
configured to the driver for driver-based FT.
andrewrpope [Mon, 25 Nov 2024 21:11:52 +0000 (08:11 +1100)]
DPP: Handle EVENT_TX_WAIT_EXPIRE path for push button
The DPP push button state machine will get stuck if an off-channel PB
announcement is cancelled via EVENT_TX_WAIT_EXPIRE. Handle a
TX_WAIT_EXPIRE by calling wpas_dpp_pb_next(), moving the state machine
forward.
Signed-off-by: Andrew Pope <andrew.pope@morsemicro.com>
Ming Kuang [Mon, 23 Sep 2024 15:25:29 +0000 (23:25 +0800)]
Fix using invalid memory during driver deinit
The address of hapd_iface->bss[0]->drv_priv is stored before calling
hostapd_free_hapd_data() and then passed to hostapd_deinit_driver()
after the call. However, hostapd_free_hapd_data() may free the
hapd->drv_priv memory, which could lead to hostapd_deinit_driver() using
an invalid memory address that has already been freed.
Commit 7554565299a1 ("hostapd: Add ctrl_iface for
enabling/reloading/disabling interface") added this split design of
storing a copy of driver/drv_priv before some deinit steps and then
using the stored values. That was likely done based on the earlier
examples of similar split which was needed in some cases a long time ago
before commit f7c478337957 ("Split hostapd_interface_deinit() into
deinit and free parts") when hostapd_interface_deinit() freed bss[0] and
as such, those pointers could not have been used without making the
separate copy first. That is not needed anymore, so get rid of it here.
Jouni Malinen [Sun, 22 Dec 2024 21:04:51 +0000 (23:04 +0200)]
Update STA authorized flag for AP SME in driver cases for open network
With AP SME in hostapd/wpa_supplicant, TX status handler for
(Re)Association Response frame takes care of this, but with AP SME in
driver cases, ap_sta_set_authorized(1) is not sufficient to update the
driver flags for the STA, so cover that case as well.
Jouni Malinen [Sun, 22 Dec 2024 17:44:24 +0000 (19:44 +0200)]
tests: MAke sae_anti_clogging_during_attack more robust
Reset apdev[1] into a known state before using it as montior interface
since issues have been seen when the previous test case used it as a 5
GHz AP. In addition, handle sock.recv() timeout more gracefully.
For example, this test case sequences had issues:
ap_track_sta_force_2ghz sae_anti_clogging_during_attack
he160b sae_anti_clogging_during_attack
When building with the no std output setting (CONFIG_NO_STDOUT_DEBUG),
the build fails with an undefined reference for wpa_debug_stop_log().
Define this as an empty function along with the others at the top of
wpa_debug.h in case no std out is configured.
The Makefile is not properly set up to compile the sae_pk_gen target.
Enabling CONFIG_SAE=y and CONFIG_SAE_PK=y in the configuration is not
sufficient to compile. The linker complains about undefined references.
These additions must be made to the Makefile to get it to compile, at
least with gcc. Once this is done, 'make sae_pk_gen' can be run without
issue.
ext_password_file: Do not use wpa_config_get_line()
The file-based backed of the ext_password framework uses
wpa_config_get_line() to read the passwords line-by-line from a file.
This function is meant to parse a single line from the
wpa_supplicant.conf file, so it handles whitespace, quotes and other
characters specially.
Its behavior, however, it's not compatible with the rest of the
ext_password framework implementation. For example, if a passphrase
contains a `#` character it must be quoted to prevent parsing the
remaining characters as an inline comment, but the code handling the
external password in wpa_supplicant_get_psk() does not handle quotes.
The result is that either it will hash the enclosing quotes, producing a
wrong PSK, or if the passphrase is long enough, fail the length check.
As a consequence, some passphrases are impossible to input correctly.
To solve this and other issues, this patch changes the behaviour of the
ext_password_file_get() function (which was not documented in details,
at least w.r.t. special characters) to simply treat all characters
literally: including trailing whitespaces (except CR and LF), `#` for
inline comments, etc. Empty lines and full-line comments are still
supported.
Jouni Malinen [Sun, 22 Dec 2024 16:16:32 +0000 (18:16 +0200)]
Add empty inline functions for CONFIG_NO_WPA
These recently added functions were used outside ifder CONFIG_NO_WPA, so
they need to have the empty inline functions in wpa.h to avoid
compilation issues.
Jouni Malinen [Sun, 22 Dec 2024 11:26:25 +0000 (13:26 +0200)]
tests: Stop hlr_auc_gw more cleanly
Use the new TERMINATE command through the socket to stop hlr_auc_gw
instead of depending on killall. There seemed to be some kind of race
condition with UML that could prevent cleanup previously.
Jouni Malinen [Sun, 22 Dec 2024 08:49:27 +0000 (10:49 +0200)]
AP MLD: Do not try to set hapd->mld multiple times
Now that there is more than one path that could end up calling
hostapd_bss_setup_multi_link(), it looks like it was possible to end up
allocating the MLD context twice and that resulted in resource leaks.
Avoid this by explicitly checking that hapd->mld is not set before
trying to determine whether to set it to an existing context or create a
new one.
Jouni Malinen [Sat, 21 Dec 2024 20:31:07 +0000 (22:31 +0200)]
tests: Make country code clearing in dbus_interface more robust
Wait for the specific CTRL-EVENT-REGDOM-CHANGE events to try to avoid
test failures due to some race conditions and the US country code being
left effective at the end of the test case.
Jouni Malinen [Sat, 21 Dec 2024 10:19:03 +0000 (12:19 +0200)]
tests: More robust way of killing hung UML VMs
The uml_mconsole halt command may hang when trying to terminate a hung
UML VM, so check for a timeout on that operation and kill the UML
process directly if that happens. In addition, do not try to terminate a
specific VM more than once to avoid confusing debug log entries.
Allen Ye [Thu, 5 Sep 2024 05:55:30 +0000 (13:55 +0800)]
hostapd: Fix wrong puncturing bitmap in Bandwidth Indication subelement
The Bandwidth Indication subelement should present the puncturing bitmap
of channel switch request, but the bitmap returned by
hostapd_get_punct_bitmap() is the original one.
Co-developed-by: Money Wang <money.wang@mediatek.com> Signed-off-by: Allen Ye <allen.ye@mediatek.com>
hostapd: Fix length of Bandwidth Indication subelement
The default length of the Bandwidth Indication subelement should be
equal to the minimum size of ieee80211_bw_ind_element structure. The
previously used value truncated this subelement by one octet.
Fixes: c7e704bdf9c3 ("hostapd: Add Bandwidth Indication subelement support for channel switch") Signed-off-by: Shayne Chen <shayne.chen@mediatek.com> Signed-off-by: Allen Ye <allen.ye@mediatek.com>
Avoid EAPOL trigger in reassoc path for AP with 4-way handshake offload
Currently avoiding of EAPOL exchange for AP with 4-way handshake offload
is handled only in the new STA assoc path. Extended this to cover
skipping authentication trigger in case reassoc path without
disconnection as well.
In case of an AP MLD it is assumed that the multi link information
(hapd->mld) is already initialized by the time this function is called.
However, if the interface is added without bss_config parameter,
hostapd_bss_setup_multi_link() would bail out immediately as mld_ap
parameter isn't set yet. When the interface gets enabled later,
hapd->mld would be NULL resulting in NULL dereference.
Signed-off-by: Andrei Otcheretianski <andrei.otcheretianski@intel.com>
Benjamin Berg [Sun, 1 Sep 2024 16:31:34 +0000 (19:31 +0300)]
BSS: MLD: Parse all TBTT entries after an invalid link
We would incorrectly exit the loop that iterates all TBTT entries if an
entry is found with an invalid link ID. This commonly happens if the AP
reports a link for another AP (or just another AP in the same MBSSID
set). Change it to continue with the next TBTT entry so that all entries
are parsed and all links can be found.
Fixes: de5e01010cb2 ("wpa_supplicant: Support ML probe request") Signed-off-by: Benjamin Berg <benjamin.berg@intel.com>
Benjamin Berg [Sun, 1 Sep 2024 16:31:33 +0000 (19:31 +0300)]
BSS: MLD: Limit TBTT parsing to correct length
Logically, it makes more sense to pass the ap_info_len as that is the
length that the function is permitted to process. Effectively it does
not make a difference and the code was entirely safe, but change it
nontheless to be more correct.
Fixes: de5e01010cb2 ("wpa_supplicant: Support ML probe request") Signed-off-by: Benjamin Berg <benjamin.berg@intel.com>
Jintao Lin [Wed, 7 Aug 2024 21:48:01 +0000 (21:48 +0000)]
P2P: Consult driver capabilities before setting HE bit in GO's conf
p2p_go_he could be set to 1 in the global config file while the device
might only has a VHT Wi-Fi NIC. Consult driver capabilities before
setting the HE bit for the GO's configuration so that latter AP
configuration does not fail due to wrong AP configuration, like
hostapd_get_oper_centr_freq_seg0_idx().
This config bit is checked and set in wpa_supplicant_conf_ap_ht() based
on a more recent commit 3459c54ac78b ("mesh: Add support for HE mode"),
Thus there is no need to override this bit specifically for P2P GO using
this older approach.
Signed-off-by: Jintao Lin <jintaolin@chromium.org>
Jouni Malinen [Thu, 19 Dec 2024 23:06:57 +0000 (01:06 +0200)]
tests: Clear AP scan cache in prefer_ht40
It was possible for the HT40+ AP to fail to start 40 MHz channel due to
a conflicting AP in the scan results from a previous test case. This
happened, e.g., with the following test case sequence:
olbc prefer_ht40
Jouni Malinen [Thu, 19 Dec 2024 22:45:25 +0000 (00:45 +0200)]
tests: Disconnect after OCV tests showing valid OCI
These test cases that used external EAPOL handling to test hostapd
behavior left the STA in associated state at the end and that could
result in race conditions showing up as a new association related event
in the following test case. Minimize risk of that resulting in test case
failures by explicit disconnecting at the end of the test case.
This was found with this test case sequence:
autogo_many wpa2_ocv_ap_unexpected1 wpa2_ocv_sta_override_eapol
mesh: Use the correct 6 GHz operating class 137 for 320 MHz bandwidth
The 320 MHz case was not yet handled for setting the global operating
class for mesh in the 6 GHz band. That needs to use the operating class
137 instead of the default 131.
When requested to disconnect a station also handle the corresponding MLD
stations. This was previously done in commit c6f519ff15b2 ("AP: Support
deauthenticate/disassociate with MLD") for ap_sta_disassociate() and
ap_sta_deauthenticate(), but similar handling is needed for
ap_sta_disconnect() as well to cover some disconnection cases especially
from the Authenticator functionality.
Shivani Baranwal [Tue, 10 Dec 2024 09:51:37 +0000 (15:21 +0530)]
P2P: Check P2P 6 GHz capability to start P2P GO
Currently, when no forced channel frequency is included with the start
an autonomous P2P GO command, a 6 GHz channel might get selected if it
is a shared radio frequency irrespective of P2P 6 GHz capability. In
these cases we need to check whether P2P 6 GHz capability is supported
before proceeding with P2P GO start on a 6 GHz channel.
Wu Gao [Fri, 13 Dec 2024 07:16:24 +0000 (23:16 -0800)]
Add QCA vendor attributes to configure antenna selection
Add following attributes to configure antenna selection:
QCA_WLAN_VENDOR_ATTR_CONFIG_ANT_DIV_PROBE_COUNT_WLAN
QCA_WLAN_VENDOR_ATTR_CONFIG_ANT_DIV_PROBE_COUNT_BT
QCA_WLAN_VENDOR_ATTR_CONFIG_ANT_DIV_PROBE_WLAN_RSSI_THRESHOLD
QCA_WLAN_VENDOR_ATTR_CONFIG_ANT_DIV_PROBE_BT_RSSI_THRESHOLD
QCA_WLAN_VENDOR_ATTR_CONFIG_ANT_DIV_SWITCH_WLAN_RSSI_DIFF
QCA_WLAN_VENDOR_ATTR_CONFIG_ANT_DIV_SWITCH_BT_RSSI_DIFF
If WLAN or BT RSSI is lower than the threshold, the firmware will start
a probe and then get RSSI of other antenna, and then select a better
antenna if RSSI difference is larger than the setting.
Jouni Malinen [Wed, 18 Dec 2024 11:07:43 +0000 (13:07 +0200)]
tests: Add some more longer duration test cases to long_tests
These test cases seemed to take longer time with UML time-travel and it
is more efficient to run them in the beginning of the test sequence to
avoid leaving a single VM delaying completion of a parallel test run
with large number of VMs. In addition, it looks like some of these test
cases are much more reliable and faster to run at the beginning of a VM
lifetime than at the end.
Jouni Malinen [Wed, 18 Dec 2024 10:43:32 +0000 (12:43 +0200)]
tests: Terminate UML VM automatically if it seems to have stopped
There have been number of cases in which a UML VM seems to hang. Make
parallel-vm.py track how long it has been since last stdout input from a
VM and terminate the VM using uml_mconsole if there has been no updates
in ten seconds. This is in use only with UML, i.e., only if time-travel
is enabled, so 120 seconds of real calendar time should be enough time
for any test case to be completed.
Jouni Malinen [Tue, 17 Dec 2024 22:19:34 +0000 (00:19 +0200)]
tests: Check whether a terminated VM completed the last test case
If the VM process (e.g., UML) hangs and gets terminated forcefully,
parallel-vm.py did not report this as a failure. Check whether the last
started test case was completed when a VM terminates and if not, report
it as a test failure.
Jouni Malinen [Tue, 17 Dec 2024 22:14:41 +0000 (00:14 +0200)]
tests: Fix unexpected exit handling
Calculation of remaining VMs seemed to have been messed up in some of
the earlier design changes. Iterate over all VMs instead of check the
terminated VM context data multiple times.
Jouni Malinen [Tue, 17 Dec 2024 18:02:03 +0000 (20:02 +0200)]
tests: Run test cases that read process memory in the beginning
Those test cases seem to have some resource issues (i.e., taking
unexpectedly large amount of memory) with newer software versions
(showed up when upgrading from Ubuntu 22.04 to 24.04; maybe due to newer
python3 version?). This might be related to memory fragmentation and
allocated memory from hostapd/wpa_supplicant not getting fully freed in
a sense of minimizing the read process memory. Running the key lifetime
test cases in the beginning of each VM seems to avoid resource issues,
so reorder the test cases to do that.
Jouni Malinen [Tue, 17 Dec 2024 17:46:43 +0000 (19:46 +0200)]
tests: Work around compiler differences in forcing failures
Something in the compiler update when moving from Ubuntu 22.04 to 24.04
made these test cases unable to trigger one of the failure sequences.
Modify the failure pattern to avoid this.
Jouni Malinen [Sat, 14 Dec 2024 08:53:58 +0000 (10:53 +0200)]
tests: Get rid of invalid escape sequences
These started to show up as SyntaxWarning prints with a newer python3
version and there is really no need to maintain the old versions, so get
rid of the invalid escape sequences.
Vinay Gannevaram [Wed, 11 Dec 2024 19:41:43 +0000 (01:11 +0530)]
P2P2: Allow P2P2 client to connect to GO with preconfigured credentials
A P2P2 GO in PCC mode will allow connecting P2P and P2P2 clients. Such
GO can allow connections with P2P clients by skipping the provisioning
procedure. Add support to allow P2P client to initiate such direct
connection with preconfigured credentials.
Vinay Gannevaram [Wed, 11 Dec 2024 19:41:43 +0000 (01:11 +0530)]
P2P2: Handle join case without pending GO interface address
Fetch a BSS entry using bssid = NULL instead of 00:00:00:00:00:00 when
starting join without a specific GO interface address. This is needed
for P2P2 client joining a group with preconfigured credentials (i.e.,
skipping the provisioning step).
EHT: Fix HE center frequency for EHT 320 MHz with puncturing
Currently, oper_chwidth holds 320 MHz and he_oper_centr_freq_seg0_idx
holds the center frequency of the primary 160 MHz, causing the
calculation of the wrong seg0 from punct_update_legacy_bw() and
leading to connectivity issues with HE STA.
Start with the HE operating bandwidth instead of EHT operating bandwidth
to calculate seg0 to update the correct center frequency in HE Operation
element.
Mohan Kumar G [Fri, 6 Dec 2024 06:14:05 +0000 (11:44 +0530)]
AP MLD: Fix radar event processing
When a radar event is received in an AP MLD operating on a DFS channel,
nl80211_radar_event() iterates over all the BSSs available in drv to
find a link matching the frequency of the event. If a link match is
found, the radar handler function tries to switch to a new channel with
the same bandwidth. In case no valid channels are available it disables
and re-enables the interface, reallocating the drv BSSs. However, the
loop in nl80211_radar_event() function continues to access the old
deallocated BSSs' address in the next iteration, causing a crash.
Since the radar handler function handles the event for all BSSs in an
interface, there is no need to call it again once a link match is found.
Hence, fix this issue by exiting the loop after calling the handler if a
link match is found for the radar event.
Also, since the loop already checks all the BSSs, remove the handler
present before the loop.
Fixes: bfc89d757b72 ("nl80211: Handle radar event properly during MLO") Signed-off-by: Mohan Kumar G <quic_mkumarg@quicinc.com>
EHT: Update legacy bandwidth when puncturing is set in 320 MHz
Update lower bandwidth without puncturing for legacy clients when
the puncturing bitmap is set in 320 MHz. This updates the lower
bandwidth in HE and VHT Operation elements when the puncturing
bitmap is set in EHT 320 MHz.
projects / thirdparty / hostap.git / log
