On 5/20/20 3:28 PM, Rui Salvaterra wrote:
On Wed, 20 May 2020 at 21:08, Larry Finger <Larry.Finger@xxxxxxxxxxxx> wrote:
I found this line in the b43 logs:
nl80211: NL80211_CMD_SET_PMKSA failed: -95 (Operation not supported)
Could we also see the supplicant log for the RaLink driver that works?
Sure thing, here you go! This one's much shorter, since the connection
was successful.
A quick difference - this one supports 3 additional ciphers:
vedder wpa_supplicant[376]: nl80211: Supported cipher 00-0f-ac:13
vedder wpa_supplicant[376]: nl80211: Supported cipher 00-0f-ac:11
vedder wpa_supplicant[376]: nl80211: Supported cipher 00-0f-ac:12
The one with :13 is for BIP-CMAC-256, :11 is BIP-GMAC-128, and :12 is
BIP-GMAC-256. I did not find a reference that says that these are needed for
WPA3, but I am suspicious.
Thus far, I have not found where the driver tells nl80211 what should be supported.
Perhaps, we were calling ieee80211_hw_set() in the wrong place. Try
diff --git a/drivers/net/wireless/broadcom/b43/main.c
b/drivers/net/wireless/broadcom/b43/main.c
index 39da1a4c30ac..211d6126734f 100644
--- a/drivers/net/wireless/broadcom/b43/main.c
+++ b/drivers/net/wireless/broadcom/b43/main.c
@@ -5569,7 +5569,10 @@ static struct b43_wl *b43_wireless_init(struct
b43_bus_dev *dev)
/* fill hw info */
ieee80211_hw_set(hw, RX_INCLUDES_FCS);
ieee80211_hw_set(hw, SIGNAL_DBM);
-
+ if (modparam_nohwcrypt) {
+ printk(KERN_INFO "b43: Setting MFP_CAPABLE\n");
+ ieee80211_hw_set(hw, MFP_CAPABLE);
+ }
hw->wiphy->interface_modes =
BIT(NL80211_IFTYPE_AP) |
BIT(NL80211_IFTYPE_MESH_POINT) |
In addition, check that the printk message is seen in dmesg.
Larry
