From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.7 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id DAF55C433ED for ; Wed, 5 May 2021 12:37:11 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id A63E9613C0 for ; Wed, 5 May 2021 12:37:11 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233259AbhEEMiF (ORCPT ); Wed, 5 May 2021 08:38:05 -0400 Received: from mail1.protonmail.ch ([185.70.40.18]:36455 "EHLO mail1.protonmail.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229793AbhEEMh5 (ORCPT ); Wed, 5 May 2021 08:37:57 -0400 Date: Wed, 05 May 2021 12:36:46 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail; t=1620218219; bh=OqGOD3RMzm56+NArYxcQNbJWPMm+m2K65zTYVUe++Fc=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=WrIgwXQaLYuGx8S8cqAEIJU61aVe8N7rpFZvP3D807YwQa5WlNULX/ZYj9AphrEz/ 3q+PpqosGQkSWzbHgRdAB/RZuLMloIaisVLJH8MnKzRg+EseKSrS6b1AjC1MqYWznL r+E572qBFoCFt2UBRW0/NMW8Kke62l4Jedx0rwy4= To: Johannes Berg From: Michael Yartys Cc: "linux-wireless@vger.kernel.org" Reply-To: Michael Yartys Subject: Re: Possible bug in iwlwifi Message-ID: In-Reply-To: <_p2InUu49ZKWc_249MDFWW8bre6iNHIJDvsoV6Rsb3oLyWj7wat48aLpnqIDVeKZKwSq-uZ1Fy_wlDwHMYJ5-JacdxF75NL5fLvpWrNCUO8=@protonmail.com> References: <7a5d0173cbfdef24b1e74c0bfc8f7410ff044817.camel@sipsolutions.net> <_p2InUu49ZKWc_249MDFWW8bre6iNHIJDvsoV6Rsb3oLyWj7wat48aLpnqIDVeKZKwSq-uZ1Fy_wlDwHMYJ5-JacdxF75NL5fLvpWrNCUO8=@protonmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me= ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 On Wednesday, May 5th, 2021 at 2:25 PM, Michael Yartys wrote: > =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original = Message =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 > > On Wednesday, May 5th, 2021 at 2:09 PM, Johannes Berg johannes@sipsolutio= ns.net wrote: > > > On Wed, 2021-05-05 at 12:05 +0000, Michael Yartys wrote: > > > > > Hello > > > > > > I've been testing out WPA3/WPA2-mixed networks on my OpenWrt router, > > > > > > and I noticed whenever I enable 802.11r the network doesn't show up i= n > > > > > > the list of Wi-Fi networks in NetworkManager. I initially thought thi= s > > > > > > was due to some bug with wpa_supplicant, but running "iw dev wlp18s0 > > > > > > scan" also fails to list the network. If I'm not mistaken, iw doesn't > > > > > > use wpa_supplicant to scan for networks, so that rules out > > > > > > wpa_supplicant. That means something deeper in the stack is causing > > > > > > this, and my guess falls on iwlwifi. > > > > Indeed, that's super strange. > > > > Are you able to see the network from another linux machine, and could > > > > maybe do a packet capture there? Or maybe just do > > > > iw wlan0 scan dump -u > > > > on another system that can see it? > > Unfortunately my other laptop also has a Intel 7260 card and can't see th= e network. My iPad and Android phone are both able to see the network, but = they're unable to connect to it. I don't know if it's of any help, but here's what WiFiAnalyzer reports abou= t the network on my Android 11 phone: https://imgur.com/a/dn0HwhG > > > johannes