From: Larry Finger <Larry.Finger@lwfinger.net>
To: Rui Salvaterra <rsalvaterra@gmail.com>
Cc: linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org
Subject: Re: [BUG?] b43: can't connect to WPA3 network (nohwcrypt=1)
Date: Tue, 19 May 2020 19:16:45 -0500 [thread overview]
Message-ID: <29f5e3de-a32c-6292-9197-19dcc57fa6a3@lwfinger.net> (raw)
In-Reply-To: <CALjTZvYSJOx0xeMVkN6dHcGTdgW9O9NVbgXPKK4d6-31VX+0JQ@mail.gmail.com>
On 5/19/20 6:13 PM, Rui Salvaterra wrote:
> On Tue, 19 May 2020 at 21:36, Rui Salvaterra <rsalvaterra@gmail.com> wrote:
>>
>> Hi, Larry,
>>
>> On Tue, 19 May 2020 at 21:30, Larry Finger <Larry.Finger@lwfinger.net> wrote:
>>>
>>> From other drivers, it appears that handling WPA3 might be as simple as setting
>>> MFP_CAPABLE in the hardware capabilities. Please try this patch:
>>
>> Fantastic, thanks for the quick reply! I will do it ASAP and get back to you.
>
> Unfortunately, looks like in this driver it's not so simple, the
> association is still rejected. I looked at the other drivers too and,
> sure enough, they just set the MFP_CAPABLE flag unconditionally with
> software crypto (I would expect mac80211 to magically handle it, but
> with b43 it doesn't seem to be the case).
It is necessary to load the driver with option nohwcrypt set to 1. I expect that
you probably did that, but I forgot to mention it.
It would likely help if you can get verbose logs from wpa_supplicant.
Larry
next prev parent reply other threads:[~2020-05-20 0:16 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 14:18 [BUG?] b43: can't connect to WPA3 network (nohwcrypt=1) Rui Salvaterra
2020-05-19 20:30 ` Larry Finger
2020-05-19 20:36 ` Rui Salvaterra
2020-05-19 23:13 ` Rui Salvaterra
2020-05-20 0:16 ` Larry Finger [this message]
2020-05-20 8:24 ` Rui Salvaterra
2020-05-20 10:55 ` Rui Salvaterra
2020-05-20 20:08 ` Larry Finger
2020-05-20 20:28 ` Rui Salvaterra
2020-05-20 20:56 ` Larry Finger
2020-05-21 8:35 ` Rui Salvaterra
2020-05-21 9:07 ` Rui Salvaterra
2020-05-21 10:46 ` Michael Büsch
2020-05-21 11:30 ` Rui Salvaterra
2020-05-21 11:40 ` Michael Büsch
2020-05-21 14:10 ` Larry Finger
2020-05-21 14:52 ` Rui Salvaterra
2020-05-21 16:17 ` Rui Salvaterra
2020-05-21 18:59 ` Larry Finger
2020-05-21 19:19 ` Rui Salvaterra
2020-05-21 20:23 ` Rui Salvaterra
2020-05-21 21:47 ` Larry Finger
2020-05-22 10:19 ` Michael Büsch
2020-05-22 11:49 ` Kalle Valo
2020-05-22 13:46 ` Rui Salvaterra
2020-05-22 18:02 ` Larry Finger
2020-05-22 20:04 ` Rui Salvaterra
2020-05-22 20:40 ` Rui Salvaterra
2020-05-22 21:06 ` Larry Finger
2020-05-23 0:35 ` Rui Salvaterra
2020-05-23 21:17 ` Rafał Miłecki
2020-05-25 6:56 ` Kalle Valo
2020-05-22 17:15 ` Larry Finger
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=29f5e3de-a32c-6292-9197-19dcc57fa6a3@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rsalvaterra@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).