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: Wed, 20 May 2020 15:08:24 -0500 [thread overview]
Message-ID: <263e247c-3bf9-6d42-996b-bc513efe4b71@lwfinger.net> (raw)
In-Reply-To: <CALjTZvaPi2FL-epk-Vd2wOLye2O0J8G5aZPsqzHXt2b7u=HyuQ@mail.gmail.com>
On 5/20/20 5:55 AM, Rui Salvaterra wrote:
> On Wed, 20 May 2020 at 09:24, Rui Salvaterra <rsalvaterra@gmail.com> wrote:
>>
>> Hi, Larry,
>>
>> On Wed, 20 May 2020 at 01:16, Larry Finger <Larry.Finger@lwfinger.net> wrote:
>>>
>>> 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.
>>
>> Yes, of course. I don't use modules, so I pass b43.nohwcrypt=1 in the
>> kernel command line. I confirmed in sysfs the nohwcrypt parameter is
>> correctly set to 1.
>>
>>> It would likely help if you can get verbose logs from wpa_supplicant.
>>
>> No problem! Attached is a wpa_supplicant -d log. Let me know if you
>> need extra verbosity.
>>
>> Thanks,
>> Rui
>
> By the way, I just tested with WPA2 forcing MFP (pmf=3 in the Network
> Manager connection) and it also doesn't connect.
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?
Larry
next prev parent reply other threads:[~2020-05-20 20:08 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
2020-05-20 8:24 ` Rui Salvaterra
2020-05-20 10:55 ` Rui Salvaterra
2020-05-20 20:08 ` Larry Finger [this message]
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=263e247c-3bf9-6d42-996b-bc513efe4b71@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).