From: Pavel Roskin <proski@gnu.org>
To: Daniel Drake <dsd@laptop.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Making sense of cfg80211_scan_request.n_ssids
Date: Tue, 02 Aug 2011 18:10:06 -0400 [thread overview]
Message-ID: <4E3875BE.9070504@gnu.org> (raw)
In-Reply-To: <CAGq3pz40rsMudofq6Njr0_h1G=EqEigGL-NkODj8Rb6h2bMGMQ@mail.gmail.com>
On 08/02/2011 01:35 PM, Daniel Drake wrote:
> Hi,
>
> I'm looking at libertas scanning code, and I'm wondering exactly what
> the cfg80211_scan_request.n_ssids field is supposed to mean.
>
> I would guess that it is supposed to indicate how many SSIDs should be
> explicitly scanned for. However, this doesn't seem to be the case.
>
> iwlist eth0 scan essid test
> iw dev eth0 scan ssid test
>
> Both of those commands result in libertas being called with
> cfg80211_scan_request with n_ssids=1 and the "test" SSID present in
> cfg80211_scan_request.ssids[0], as expected.
>
>
> iwlist eth0 scan
> iw dev eth0 scan
>
> Both of those commands result in libertas being called with
> cfg80211_scan_request with n_ssids=1 and a zero-length SSID present in
> cfg80211_scan_request.ssids[0].
> Is this a bug? I would expect it to be passed n_ssids=0 in this case.
I believe n_ssids is the number of probe requests to be sent per
channel. It scanning for all SSIDs, one probe request is sent. It is
only for passive scanning that we don't need any probes.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2011-08-02 22:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 17:35 Making sense of cfg80211_scan_request.n_ssids Daniel Drake
2011-08-02 22:10 ` Pavel Roskin [this message]
2011-08-08 8:37 ` Johannes Berg
2011-08-09 9:36 ` Luciano Coelho
2011-08-09 9:40 ` Johannes Berg
2011-08-09 9:42 ` Luciano Coelho
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=4E3875BE.9070504@gnu.org \
--to=proski@gnu.org \
--cc=dsd@laptop.org \
--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).