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;
Date:   Fri, 2 Dec 2022 15:13:15 +0200
From:   Jouni Malinen <j@w1.fi>
To:     "Matthias G." <maps4711@gmx.de>
Cc:     Johannes Berg <johannes@sipsolutions.net>,
        linux-wireless@vger.kernel.org, hostap@lists.infradead.org
Subject: Re: Bug report: Can connect with 'wext', but not 'nl80211'
Message-ID: <20221202131315.GD444432@w1.fi>
References: <1235df2ba1757a5917dc21455fa8c1d0a48bb2c4.camel@gmx.de>
 <f694e9d9dbf36b870f278f8eabed14d5dede55aa.camel@sipsolutions.net>
 <f8dea92e4fa8e26bd1cc7ff8c6ba6ccd4843d8eb.camel@gmx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <f8dea92e4fa8e26bd1cc7ff8c6ba6ccd4843d8eb.camel@gmx.de>
Precedence: bulk

On Thu, Dec 01, 2022 at 06:45:01PM +0100, Matthias G. wrote:
> On Wed, 2022-11-30 at 21:29 +0100, Johannes Berg wrote:
> > 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.

-- 
Jouni Malinen                                            PGP id EFC895FA