From: Michael Yartys <michael.yartys@protonmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Possible bug in iwlwifi
Date: Wed, 05 May 2021 12:25:04 +0000 [thread overview]
Message-ID: <_p2InUu49ZKWc_249MDFWW8bre6iNHIJDvsoV6Rsb3oLyWj7wat48aLpnqIDVeKZKwSq-uZ1Fy_wlDwHMYJ5-JacdxF75NL5fLvpWrNCUO8=@protonmail.com> (raw)
In-Reply-To: <7a5d0173cbfdef24b1e74c0bfc8f7410ff044817.camel@sipsolutions.net>
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Wednesday, May 5th, 2021 at 2:09 PM, Johannes Berg <johannes@sipsolutions.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 in
> >
> > the list of Wi-Fi networks in NetworkManager. I initially thought this
> >
> > 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 the network. My iPad and Android phone are both able to see the network, but they're unable to connect to it.
>
> johannes
next prev parent reply other threads:[~2021-05-05 12:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 12:05 Possible bug in iwlwifi Michael Yartys
2021-05-05 12:09 ` Johannes Berg
2021-05-05 12:25 ` Michael Yartys [this message]
2021-05-05 12:36 ` Michael Yartys
2021-05-05 13:06 ` Michael Yartys
2021-05-05 16:48 ` Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2013-01-24 20:51 Maciek Zarzycki
2013-01-27 20:59 ` Maciek Zarzycki
2013-01-27 21:25 ` Sedat Dilek
2013-01-27 21:27 ` Sedat Dilek
2013-01-27 21:49 ` Maciek Zarzycki
2013-01-27 21:59 ` Sedat Dilek
2013-01-29 19:32 ` Maciek Zarzycki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='_p2InUu49ZKWc_249MDFWW8bre6iNHIJDvsoV6Rsb3oLyWj7wat48aLpnqIDVeKZKwSq-uZ1Fy_wlDwHMYJ5-JacdxF75NL5fLvpWrNCUO8=@protonmail.com' \
--to=michael.yartys@protonmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).