Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp10170707rwb; Fri, 25 Nov 2022 01:44:23 -0800 (PST) X-Google-Smtp-Source: AA0mqf6ah2wNf6BVQeJPcHbVfKEEDRCzm18XOkGtBFuFGzHyjvjnnBotfEMZIlRjUBRaOb0Vw/zD X-Received: by 2002:a17:902:bd42:b0:186:9c2b:3a39 with SMTP id b2-20020a170902bd4200b001869c2b3a39mr17768908plx.115.1669369462807; Fri, 25 Nov 2022 01:44:22 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1669369462; cv=none; d=google.com; s=arc-20160816; b=c8poyyEVHfUhS0VU2l5zBbgEY0Bu5GFixXKcuLCg+DO1hn7BT8crxQidCALdcHPaMW 3tJ5FRD+nzdo9nMnzkHmlX2ZolBI+FYqTDnU+mCgcm7xxk+VBjzNNpbB88lCbEq2AcgS rzZuvoxZ6B6QvcZ0eH+3DvQ//R063eVNF4+PyZKYj2blQzS1FM4DR7CCNZ0q6UZklt22 laWNb+oIBFrXg60DGPA3GgZmyQq7Yh/QyQo2zUGH+NGOo7x+BwjE6b9u8mIKtzAwiHv8 GasnU35yzj7vVblNuECwksg0IZC+DXrlKXxXs2oELJXizBBvCqTDate9wt/gxflIYiB9 FOKw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent :content-transfer-encoding:references:in-reply-to:date:to:from :subject:message-id:dkim-signature; bh=Aa7Ti6qDDUxCyl6kPQ5pglUYqGOHdSvpDB7Y9K2Y1+g=; b=bhjQEpc6M4XGd6FE16yuDPxhwhufAVal58tk4zBjA6DwIe4lOOgWmx2lxT/EiHtZrM dLyFZx774HoMgJRNbySTzQ7g1/Ty6BZxdgheQTnMF/QnlWuNh0O+FTHzBm4XfKTOZHUV TA4bNEbKO+i1GZYMUpQMIPUw020P2yzwA20auW32IS8rfhMxqmHLXs98xgvvmmsR8Air SVw0U/bB5vhDfaMB5o28fkgSsXutS3mNITFPeKqMWQxTj3elPCSkKmBUKzqOoY42OVW8 QgY/0e5Bitog+AoxeastGNn8SIG7UNmkKvarTfd2WMN/BjBW00JjIlN1l/CaefNxt7Dj 18hw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@sipsolutions.net header.s=mail header.b=Vdjs47l6; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=REJECT dis=NONE) header.from=sipsolutions.net Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id c34-20020a634e22000000b00422c003b4c9si2943140pgb.46.2022.11.25.01.44.11; Fri, 25 Nov 2022 01:44:22 -0800 (PST) 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; Authentication-Results: mx.google.com; dkim=pass header.i=@sipsolutions.net header.s=mail header.b=Vdjs47l6; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=REJECT dis=NONE) header.from=sipsolutions.net Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229548AbiKYJfd (ORCPT + 67 others); Fri, 25 Nov 2022 04:35:33 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52314 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229452AbiKYJfc (ORCPT ); Fri, 25 Nov 2022 04:35:32 -0500 Received: from sipsolutions.net (s3.sipsolutions.net [IPv6:2a01:4f8:191:4433::2]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7158C27FC0 for ; Fri, 25 Nov 2022 01:35:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sipsolutions.net; s=mail; h=MIME-Version:Content-Transfer-Encoding: Content-Type:References:In-Reply-To:Date:To:From:Subject:Message-ID:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-To: Resent-Cc:Resent-Message-ID; bh=Aa7Ti6qDDUxCyl6kPQ5pglUYqGOHdSvpDB7Y9K2Y1+g=; t=1669368931; x=1670578531; b=Vdjs47l6NqX/5nPlbe0GU6xGU3YWO00K5bJeGgv7vnuYoTF bm0Q04kHyb2Kcj2VE/u9FZHvzDDWXRoSMdXLFPIIn/0taENTqVxi5S3HpOh6MyJ6xB4GVyk1AzVPe PgW/ibT70BSf36noeHFIplpbKDvxonyJLHG9fKPT5fh8ZPKyXD5yWl/9qjv4oAdQkidqgNRTUDcoK e8TX5B0AIOIlwCCqCaIqTeg8iPv/j3clXqCXuXxHHckoCZXeq3VXj3CeQhFPxowk3qQwrANXXwgrl 0YikwF9K7JSdWbdC3SKHu/9XjWzdTVhkytoaefhd3kaQEnFXGS4g4iQt/2t9fC2A==; Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.96) (envelope-from ) id 1oyV7J-008oKY-2m; Fri, 25 Nov 2022 10:35:29 +0100 Message-ID: Subject: Re: PRO/Wireless 2200BG Intel WPA3 SSID connection problem #1 From: Johannes Berg To: Ioannis Barkas , linux-wireless@vger.kernel.org Date: Fri, 25 Nov 2022 10:35:28 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.44.4 (3.44.4-2.fc36) MIME-Version: 1.0 X-malware-bazaar: not-scanned X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org Hi, > This period I have been dealing with WLANs as I have added a new WPA3 > SSID and fell on some trouble and limitations(more messages will > follow on this). >=20 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. > Long story short, some WLAN cards do not work and > some Android based mobile phones do not work(like my Android 12 based > SAMSUNG M31 which is not detecting such SSIDs at all!). On one hand, > vendors like Atheros have done a good job. As a result, all cards were > able to connect successfully at SSID using the WPA3 encryption. This > includes miniPCI, PCI, miniPCIe, Cardbus and USB adapters. >=20 This probably means they use SW crypto for everything. > On the > other hand vendors like Intel haven't done a really good job. miniPCI > cards from Intel are out of question due to legacy driver and custom > 802.11 implementation. Initial miniPCIe cards like 4965 series do not > support it similar to many iwlwifi cards. I believe that all iwlwifi > supported cards should be able to use WPA3. What makes you believe that? > My 2006 Atheros cards > connect successfully so I expect the same for intel cards launched a > decade after the old Atheros cards otherwise we should blacklist such > devices to save lots of noise from bug reports about undetected > networks.=C2=A0 Umm, no? Why would we break NICs that work well with most existing networks, just not WPA3 ones? > Hopefully the Intel team will fix everything so that noone > will not need to switch cards on laptops.=C2=A0 >=20 Unlikely. The newest Intel NIC in your list was 6205, which was released in 2011. Without wpa_supplicant logs I'm not even sure why it's broken, but likely the reason is that it doesn't advertise management frame protection support since the firmware handles certain management frames, and there was no hardware offload for those at the time. (This might be a difference to Atheros NICs.) >=20 > It can't connect to WPA3 2,4GHz SSID and I got no logs. Well, you should look at wpa_supplicant logs. johannes