linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Witold Sowa <witold.sowa@gmail.com>
To: Samuel Ortiz <samuel@sortiz.org>
Cc: Christopher Piggott <cpiggott@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: scanning a specific ssid
Date: Fri, 20 Aug 2010 13:13:51 +0200	[thread overview]
Message-ID: <4C6E636F.2080606@gmail.com> (raw)
In-Reply-To: <1282302303.3662.5.camel@sortiz-mobl>

Samuel Ortiz pisze:
> Hi Christopher,
>
> On Thu, 2010-08-19 at 16:25 -0400, Christopher Piggott wrote:
>   
>> Hi,
>>
>> I wrote a small C++ program using libdbus-c++ to scan for access
>> points via wpa_supplicant's dbus interface.  It works very well, and I
>> can retrieve the list just fine.
>>
>> Now I want to cause it to scan for a specific SSID by issuing a probe,
>> but the dbus interface fi.epitest.hostap.WPASupplicant.Interface has
>> only one scan method, and it does not seem to take arguments.
>> (Looking at the source file ctrl_iface_dbus_handlers.c in function
>> wpas_dbus_iface_scan() you can see why - it doesn't handle or even
>> look at the arguments to the message).
>>
>> Is there another way to accomplish this?  
>>     
> I don't know which version of wpa_supplicant you're using, but the new
> D-Bus API (fi.w1.wpa_supplicant1.*) has a much more extended scanning
> API. You can pass SSIDs, channels, IEs and the scanning type to it.
>   
The new DBus API is present only in development (0.7.x) branch of
wpa_supplicant. 0.6.10 and earlier support only the old API which,
indeed, has very limited scanning options capabilities.

Witek.

  reply	other threads:[~2010-08-20 11:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-19 20:25 scanning a specific ssid Christopher Piggott
2010-08-20  7:45 ` Johannes Berg
2010-08-20 11:05 ` Samuel Ortiz
2010-08-20 11:13   ` Witold Sowa [this message]
2010-08-20 11:31     ` Johannes Berg

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=4C6E636F.2080606@gmail.com \
    --to=witold.sowa@gmail.com \
    --cc=cpiggott@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=samuel@sortiz.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).