From: Thomas Klute <thomas2.klute@uni-dortmund.de>
To: Michael McElroy <mikem388@gmail.com>
Cc: Krishna Chaitanya <chaitanya.mgit@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: CLI scan tool needed
Date: Wed, 31 Jul 2013 23:24:10 +0200 [thread overview]
Message-ID: <51F9807A.6080000@uni-dortmund.de> (raw)
In-Reply-To: <CAJt7DwzwyOKso_zNyemnX0LdXvtrWiuoaRJ8dnN8FKVjxiaayg@mail.gmail.com>
Am 31.07.2013 22:51, schrieb Michael McElroy:
> Thanks Krishna, but all it returns is OK. Running the version 2.0 of
> wpa_supplicant.
I think the command you want is "scan_results" instead of "scan", so
"wpa_cli -i <interface> scan_results" over all. ;-)
> On Wed, Jul 31, 2013 at 4:30 PM, Krishna Chaitanya
> <chaitanya.mgit@gmail.com> wrote:
>> On Wed, Jul 31, 2013 at 11:57 PM, Michael McElroy <mikem388@gmail.com> wrote:
>>> Using the backports project, I have one of the latest ralink driver
>>> going on an arm processor running 2.6.29 along with all nl80211 parts.
>>> Works great, thank you! The last piece I need is to get the to SSID
>>> list, their security protocols, and signal strength. I'm looking for
>>> output similar to 'wilist scanning'. 'iw scan' gives a lot of info but
>>> not quite what I need without a lot of massaging.
>>
>> "wpa_cli -i <interface> scan"
>> this should give you the required info, if you are already running the
>> wpa_supplicant.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2013-07-31 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 18:27 CLI scan tool needed Michael McElroy
2013-07-31 20:30 ` Krishna Chaitanya
2013-07-31 20:51 ` Michael McElroy
2013-07-31 21:24 ` Michael McElroy
2013-07-31 21:24 ` Thomas Klute [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=51F9807A.6080000@uni-dortmund.de \
--to=thomas2.klute@uni-dortmund.de \
--cc=chaitanya.mgit@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mikem388@gmail.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;
as well as URLs for NNTP newsgroup(s).