For cross akm roaming function, we have two ways in supplicant :
1. Open source way.
2. Broadcom specific way.
Originally, Broadcom projects follow way 2 due to the limitation of the driver.
For now, we plan to move all Broadcom projects to follow way 1 to make supplicant code clean and downsteam without conflict.
For those projects which is ready for way 1, we control it to follow way 1 with WIFI_BRCM_OPEN_SOURCE_MULTI_AKM config.
For the rest of Broadcom projects, we still follow way 2 until the multiple AKMs is fully supported by driver and verified.
For ongoing Broadcom project, we also need to exercise the open source path in supplicant to do multiple AKM configuration to comply with WFA Wifi 7 AKM24 specification (b/331896542 ).
Bug: 246871098
Test: AU drop test
Test: Cross AKM roaming test
Flag: EXEMPT enable control flag for aosp akms
Change-Id: I2594e3741d5be1c055d364104639b3d55336a5a7
It has an effect on following case:
If STA firstly connected with 6ghz channel AP and Application create p2p group without config, wpa_supplicant also tried to select STA-associated channel(in this case, i.e. 6ghz ch).
Bug: 281733591
Test: atest android.net.wifi.cts.ConcurrencyTest#testPersistentGroupOperation
Change-Id: I6b65624649f7b5fff320ec1c70979b450afce1aa
The correct path should be under /data,
or it is not writable.
wpa_supplicant now support p2p overlay configuration, a unified
wpa_supplicant init entry can be used.
Bug: 238601241
Test: create a group and check this group is persisted
after reboot
Change-Id: I3c5523626de22c26cb562c03e9fbd7aabf6d98e7
Update WIFI_HAL_INTERFACE_COMBINATIONS for 1.6 HAL, which should
explicitly specify AP_BRIDGED for bridged AP.
Bug: 207055799
Test: build
Change-Id: Ibc9ee2a5b0d446e7fe4ad4022da1a086a042e235
Set ieee80211w=1 config item in the hostapd config file
based on the feature flag, BOARD_HOSTAPD_CONFIG_80211W_MFP_OPTIONAL.
This enables management frame protection and prevents denial of
service when an attacker sends deauthentication frames to the
clients connected to the SoftAp.
Bug: 197874458
Test: Connected STAs to Pixel SofAp and confirmed from the
sniffer logs that PMF capabilities are exchanged and the required
management frames are protected.
Change-Id: I6f23fd82eeec97d80d808c90ad48901eda630646
move wifi configurations from BoardConfig-common.mk to wifi/BoardConfig-wifi.mk.
So, each project can decide whether it should share the same configurations or create a new one on their own.
Bug: 208159314
Test: ifconfig after attempting STA+SAP concurrency.
Change-Id: Id2474df377f242528be661fefe712d7203cdddf8
Bug: 194132777
Test: connect STA to 2.4GHz and verified that p2p is able to come up in
5GHz DBS mode.
Change-Id: I07fb6b586b89f66fd105673d47b2d2367c30e487
Use default wifi channel 11 if interference from band 40
renders all 2.4GHz wifi channels unsafe for coex.
Bug: 198345384
Test: adb shell cmd wifi set-coex-cell-channels lte 40 2400000 200000 -1
0, verify that coex log does not contain unsafe channel 11
Change-Id: Ifd90ed1846bc9897a88244b5fdc964143c00d702
