From: Johannes Berg <johannes@sipsolutions.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: coekbe <coekbe@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: [RFC][PATCH] rtl8192cu: completing beaconing support
Date: Tue, 04 Sep 2012 10:15:40 +0200 [thread overview]
Message-ID: <1346746540.3737.3.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <50440156.5020300@lwfinger.net> (sfid-20120903_030117_121240_2694CB76)
On Sun, 2012-09-02 at 20:01 -0500, Larry Finger wrote:
> On 09/02/2012 06:20 PM, Johannes Berg wrote:
> >
> > Just FYI -- that's not guaranteed if "iw scan" returns results, you'd
> > have to run "iw scan passive" to make sure you pick up beacons rather
> > than just probe responses.
>
> That is good to know. Unfortunately, 'iw wlan0 scan passive' run as an
> unprivileged user results in "command failed: Operation not permitted (-1)".
> When I run it as root, then I get "command failed: Operation not supported
> (-95)". I am assuming that my version of iw (0.9.22) is not new enough.
Seems like, though it's a bit strange that'd you'd get operation not
supported. Not sure why that is.
> When I run 'iwlist scan' in unprivileged mode, I did see the beacon, thus I got
> the right answer.
You can't run "iwlist scan" in unprivileged mode either, in this mode
it'll just return the existing results list that is still there due to
wpa_supplicant (or some other process) triggering a scan.
If you want to check if you saw a beacon, you can run
iw wlan0 scan dump -b
and check if it prints
"Information elements from Beacon frame:"
for that AP.
johannes
prev parent reply other threads:[~2012-09-04 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-02 18:50 [RFC][PATCH] rtl8192cu: completing beaconing support coekbe
2012-09-02 23:02 ` Larry Finger
2012-09-02 23:20 ` Johannes Berg
2012-09-03 1:01 ` Larry Finger
2012-09-04 8:15 ` Johannes Berg [this message]
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=1346746540.3737.3.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Larry.Finger@lwfinger.net \
--cc=coekbe@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).