Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp2363014rwb; Fri, 2 Dec 2022 08:47:56 -0800 (PST) X-Google-Smtp-Source: AA0mqf76vZZG3O0aqLiMtSWHQaY/VNIo1khT08HH1rQixe/xmP0+7ja1ZrJY3cZ7A+uxTCjY7USi X-Received: by 2002:aa7:db13:0:b0:46b:aee1:3b46 with SMTP id t19-20020aa7db13000000b0046baee13b46mr11895705eds.44.1669999676351; Fri, 02 Dec 2022 08:47:56 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1669999676; cv=none; d=google.com; s=arc-20160816; b=p8S0gzVTOhE0qC8KGW0Zr5HC5Eiq4B5Yuxbg6BhcPOY2+OPJpWigO68t1r7YH/WmUB W8IECtPQ00DZr+2ByjHQX0DoeOkwxjmXYCb66wTJiyjzkQC1IT/gMufHxzMAEPAqQVfG X0uH8db1Wktpz8t2An9GDj/Q6tOACE07vMuU2nH5dbpMP+H4nzhgzqoKn0pbkZNfnwLa h382vjcw3Btji8hDYGA1/5+4I+ir8BLDwnNNJ9qAwrgFaUabffDBCTWbDPma+2jaSyyw hX2DLjGT/tYGtzaG81WMg1KFGO3WW2GCQq2u9E7RaDWlmNfBciURDUt7qvNCSbyToVgG 8PLw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:to:references:message-id :content-transfer-encoding:cc:date:in-reply-to:from:subject :mime-version; bh=5x0UAf0sMQ0MPpe8uIs58zg6qeTu55CftKvx5J+vSoE=; b=0D276n0bTSJ1KieGKWuXgSaIi6HceJOb0Rnn4O+q1ZEkjwHbINyQh6A9ocFuLVJaPK FMNBo8QTRzNPEWvod75nBi148J4xLu21/4DxnZiRbrmrsmLC/VxwsH7rgfHFXjiBICyR cbngga8PLxb1eHRI4MV9uSCUnqHCz8oMjXfCmhlscXMwxcc3y+DmOzUb9P6N6TRIC6zV rrRK8o7TDgjrjh7V5rPza46sPjoYVbWmgWQ74SNmkgXUsmcndM5cdldVOCBwIPEbFXgp OWODCAaWyH5hCEAZypRIB8OgBTTLldf+YKDRNrdpTIflSWSqCQX8God7m/H1vCPk0J0D dK7w== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id nc16-20020a1709071c1000b007a7fc67c880si7091389ejc.71.2022.12.02.08.47.24; Fri, 02 Dec 2022 08:47:55 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233880AbiLBQcx (ORCPT + 66 others); Fri, 2 Dec 2022 11:32:53 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53718 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233332AbiLBQcc (ORCPT ); Fri, 2 Dec 2022 11:32:32 -0500 Received: from mail.holtmann.org (coyote.holtmann.net [212.227.132.17]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id CB1F24A5AD for ; Fri, 2 Dec 2022 08:32:29 -0800 (PST) Received: from smtpclient.apple (p4fefca0f.dip0.t-ipconnect.de [79.239.202.15]) by mail.holtmann.org (Postfix) with ESMTPSA id C899DCECFF; Fri, 2 Dec 2022 17:32:28 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\)) Subject: Re: Bug report: Can connect with 'wext', but not 'nl80211' From: Marcel Holtmann In-Reply-To: <20221202131315.GD444432@w1.fi> Date: Fri, 2 Dec 2022 17:32:28 +0100 Cc: "Matthias G." , Johannes Berg , linux-wireless@vger.kernel.org, hostap@lists.infradead.org Content-Transfer-Encoding: 7bit Message-Id: References: <1235df2ba1757a5917dc21455fa8c1d0a48bb2c4.camel@gmx.de> <20221202131315.GD444432@w1.fi> To: Jouni Malinen X-Mailer: Apple Mail (2.3696.120.41.1.1) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, 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 Matthias, >>> Sounds like the AP is broken and doesn't like some elements wpa_s >>> includes when nl80211 has certain capabilities ... > >> Just for reference, both my Windows 10 and my Android phone can connect >> to this 'Congstar'-labelled device without further configuration. I >> don't know what Windows and Android are doing behind the scenes though. > > If you have a means for capturing wireless sniffer traces of the frames > exchanged between the AP and these various station devices, it would be > useful to take a look at what the exact differences in the Association > Request frame contents. For the nl80211 interface case itself, it would > be interesting to see what is the exact information element that makes > the AP misbehave, e.g., by removing them one by one (this might be > either in wpa_supplicant or kernel) until the association succeeds. you can run iwmon (from iwd package) to capture the nl80211 traffic and it will decode the frames for you. You might want to also compare it to running iwd instead of wpa_supplicant since I have some vague memory we had this kind of issue and handled it somehow. Regards Marcel