Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Michael Yartys <michael.yartys@protonmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Possible bug in iwlwifi
Date: Wed, 05 May 2021 18:48:38 +0200	[thread overview]
Message-ID: <333ba6b138390ca1f45b8ac2aab1152397c41bd7.camel@sipsolutions.net> (raw)
In-Reply-To: <0IuWBg5tqXtBE836_CvCmwVzEXWDOGZ4dyETg5_WBWUC8bMDR9vFORGkgY6_WBqSi61GYW07WwH6aVzkc2-zhqWYp5JugyjWU_Bg1leD0vk=@protonmail.com> (sfid-20210505_150701_630699_48CDE0E4)

On Wed, 2021-05-05 at 13:06 +0000, Michael Yartys wrote:
> Sorry for being a bit spammy here, but I forgot that I could simply
> run "iw scan" on one of my two routers to see how it sees the network
> on the other router:
> 
> $ iw dev wlan1 scan -u
> BSS redacted(on wlan1)

Hm. That looks fine.

Can you do it again with --debug? But then it's hard to redact things,
so maybe send it to me in private.

Thanks,
johannes


  reply	other threads:[~2021-05-05 17:31 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
2021-05-05 12:36     ` Michael Yartys
2021-05-05 13:06       ` Michael Yartys
2021-05-05 16:48         ` Johannes Berg [this message]
  -- 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=333ba6b138390ca1f45b8ac2aab1152397c41bd7.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=michael.yartys@protonmail.com \
    /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