From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: Aditya Garg <gargaditya08@live.com>, Janne Grunau <j@jannau.net>,
<devnull+j.jannau.net@kernel.org>
Cc: <asahi@lists.linux.dev>, <brcm80211-dev-list.pdl@broadcom.com>,
<brcm80211@lists.linux.dev>, <kvalo@kernel.org>,
<linus.walleij@linaro.org>, LKML <linux-kernel@vger.kernel.org>,
<linux-wireless@vger.kernel.org>,
Hector Martin <marcan@marcan.st>, <stable@vger.kernel.org>
Subject: Re: [PATCH] wifi: brcmfmac: cfg80211: Handle SSID based pmksa deletion
Date: Sun, 04 Aug 2024 13:04:25 +0200 [thread overview]
Message-ID: <1911d0fdea8.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com> (raw)
In-Reply-To: <MA0P287MB021725DE596EF4E5294FA5DDB8BD2@MA0P287MB0217.INDP287.PROD.OUTLOOK.COM>
On August 4, 2024 8:27:04 AM Aditya Garg <gargaditya08@live.com> wrote:
> Hi
>
> WPA3 is broken on T2 Macs (atleast on 4364) for a long time. I was under
> the impression brcmfmac doesn't support it.
>
> Anyways, I've asked a fedora user to compile a kernel with CONFIG_BRCMDBG.
>
> If you want logs without it, look over here:
> https://pastebin.com/fnhH30JA
Not sure what to make of this. The interface comes up without any obvious
error and then another interface is created by another driver:
[ 7.006441] rtl8xxxu 1-8.3:1.0 wlp0s20f0u8u3: renamed from wlan0
That interface connects:
[ 9.103599] wlp0s20f0u8u3: authenticate with 98:da:c4:af:1f:c2 (local
address=2e:87:9a:a9:38:66)
[ 9.103605] wlp0s20f0u8u3: send auth to 98:da:c4:af:1f:c2 (try 1/3)
[ 9.109051] wlp0s20f0u8u3: authenticated
[ 9.110202] wlp0s20f0u8u3: associate with 98:da:c4:af:1f:c2 (try 1/3)
[ 9.126945] wlp0s20f0u8u3: RX AssocResp from 98:da:c4:af:1f:c2
(capab=0x1431 status=0 aid=5)
[ 9.127678] usb 1-8.3: rtl8xxxu_bss_info_changed: HT supported
[ 9.128606] wlp0s20f0u8u3: associated
Is brcmfmac setup to connect to the same access point. There are a lot of
unknowns here.
Regards,
Arend
> ________________________________________
> From: Janne Grunau <j@jannau.net>
> Sent: 04 August 2024 11:49
> To: Aditya Garg; devnull+j.jannau.net@kernel.org
> Cc: arend.vanspriel@broadcom.com; asahi@lists.linux.dev;
> brcm80211-dev-list.pdl@broadcom.com; brcm80211@lists.linux.dev;
> kvalo@kernel.org; linus.walleij@linaro.org; LKML;
> linux-wireless@vger.kernel.org; Hector Martin; stable@vger.kernel.org
> Subject: Re: [PATCH] wifi: brcmfmac: cfg80211: Handle SSID based pmksa deletion
>
> Hej,
>
> On Sun, Aug 4, 2024, at 05:10, Aditya Garg wrote:
>> Hi
>>
>> wpa_supplicant 2.11 broke Wi-Fi on T2 Macs as well, but this patch
>> doesn't seem to be fixing Wi-Fi. Instead, it's breaking it even on
>> older 2.10 wpa_supplicant. Tested by a user on bcm4364b2 wifi chip with
>> a WPA2-PSK [AES] network. dmesg output:
>
> On bcm4377, bcm4378 and bcm4388 (chipsets used in M1/M2 macs)
> WPA3-SAE and WPA2-PSK still works with Fedora's wpa_supplicant 2.10.
> Fedora's package carried SAE offload patches in 2.10.
> wpa_supplicant 2.11 still doesn't work with this patch but it prevents a
> kernel oops after a disconnect (due to an authentication timeout in the
> current broken state) in wpa_supplicant.
>
> I'll continue to debug the wpa_supplicant 2.11
>
> best regards,
> Janne
next prev parent reply other threads:[~2024-08-04 11:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-04 3:10 Aditya Garg
2024-08-04 5:15 ` Arend Van Spriel
2024-08-04 6:19 ` Janne Grunau
2024-08-04 6:26 ` Aditya Garg
2024-08-04 11:04 ` Arend Van Spriel [this message]
2024-08-04 11:37 ` Janne Grunau
2024-08-05 6:25 ` Janne Grunau
2025-02-09 19:10 ` Aditya Garg
-- strict thread matches above, loose matches on Subject: below --
2024-08-03 19:52 Janne Grunau via B4 Relay
2024-08-07 8:09 ` Neal Gompa
2024-08-08 8:25 ` Arend van Spriel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1911d0fdea8.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=asahi@lists.linux.dev \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=devnull+j.jannau.net@kernel.org \
--cc=gargaditya08@live.com \
--cc=j@jannau.net \
--cc=kvalo@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®