Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
From:   Ioannis Barkas <jnyb.de@gmail.com>
Date:   Sun, 27 Nov 2022 20:29:56 +0200
Message-ID: <CADUzMVbgf2dcu0yM=XO37GbTvgGK=mJpfELHrqDqbBECSuLKJg@mail.gmail.com>
Subject: Re: PRO/Wireless 2200BG Intel WPA3 SSID connection problem #1
To:     linux-wireless@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

> Well, keep in mind that WPA3 requires all kinds of new things, and the
> *most recent* NIC you tried is already ~11 years old afaict.
Yes and no. Yes it needs new things. No this is not the case here. I
tested cards from 2021 back to 2003.

> This probably means they use SW crypto for everything.
Sounds good to me since it works.

> What makes you believe that?
The fact that some just work. Why not use SW crypto on legacy devices?

> Umm, no? Why would we break NICs that work well with most existing
> networks, just not WPA3 ones?
You got it wrong here. What I mean is to use a flag that some devices
are not WPA3 compatible. That way when an attempt to connect at such
an SSID would print a message suggesting to use a WPA2 network. This
will help novice users and save time from bug reports. Most routers
now support WPA3.

> Unlikely. The newest Intel NIC in your list was 6205, which was released
> in 2011.
That is a good one :) I have much more hardware than I need. I just
sent what made errors here. Rest assured that I have tested all intel
cards including mPCIe and CNVi M2 except the AX411. Also do not own
any wimax ones from Intel and Marvell based cards. To be honest,
tomorrow I will receive two more mPCIe cards having PCIe adapter using
Mediatek chips for testing since we had only two of them borrowed from
ADSL routers and are locked at 5GHz only operation. But they connected
successfully to a 5GHz WPA3 SSID.

> Well, you should look at wpa_supplicant logs.
Will do tomorrow as I will switch to custom 6.0 as well since I have
another one card facing issues. A Cardbus based Atheros ath9k failing
WPA3 without any logs so will hopefully check both.

> And btw, your clock is off by a day:
Debian default time zone was set to US by default but switched to MX
Linux today since I could not bare Gnome! Used the right time zone now