linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Dan Kosek <daniel.kosek@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: iw scanning broken?
Date: Sat, 4 Aug 2018 21:19:30 +0200	[thread overview]
Message-ID: <5B65FC42.3010604@broadcom.com> (raw)
In-Reply-To: <C17ECAF6-E13C-40DB-A582-C9945D9BE7D7@gmail.com>

On 8/4/2018 3:08 PM, Dan Kosek wrote:
> If you enter the following command, you should get a single channel scan:
>
> sudo iw wlan0 scan freq 2412
>
> You do not.  Instead you get a full (all) channels scan, which takes 3-5 seconds.

Do you have any logs to support that claim. Please note that the command 
returns all BSS-es that are listed in wireless subsystem, ie. in 
cfg80211. That includes BSS-es found in previous scans unless their 
lifetime expired. What happens if you do...

$ sudo iw wlan0 scan freq 2412 flush

> This has been tested on Raspberry Pi Raspian 9 and Peppermint OS 7 ( Linux 4.4.0-53-generic #74-Ubuntu) with the same results.
>
> i believe iw is broken or some command knowledge is missing.

So what drivers are involved. Please include kernel logs.

Regards,
Arend

  reply	other threads:[~2018-08-04 21:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-04 13:08 iw scanning broken? Dan Kosek
2018-08-04 19:19 ` Arend van Spriel [this message]
     [not found]   ` <0ED1D417-F3DA-41EC-BE23-B0D3F736D255@gmail.com>
2018-08-06  9:17     ` Arend van Spriel
     [not found]       ` <D466CC31-C56F-46F0-B189-2B10702701C6@gmail.com>
2018-08-08  2:25         ` Dan Kosek

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=5B65FC42.3010604@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=daniel.kosek@gmail.com \
    --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).