Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Can one program see another's scan-results?
Date: Tue, 10 Jul 2012 21:22:38 +0200	[thread overview]
Message-ID: <1341948158.4475.33.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4FFC805B.909@candelatech.com>

On Tue, 2012-07-10 at 12:19 -0700, Ben Greear wrote:
> On 07/10/2012 12:08 PM, Johannes Berg wrote:
> > On Tue, 2012-07-10 at 12:02 -0700, Ben Greear wrote:
> >> Is there a way to open a netlink socket and have it receive
> >> all scan results (even those requested by other applications)?
> >
> > What do you mean by scan results? The results themselves? No, they are a
> > dump and unicast to one application. The fact that a scan finished? Yes,
> > of course.
> 
> I'd like the results themselves..for instance, just piggyback on whatever
> supplicant is already doing to get periodic updates, and of course I'd
> end up requesting some scans myself from time to time if a user wanted
> an immediate update.
> 
> I was hoping it could be something like just listening for network-device
> and route updates like netlink already supports.
> 
> Since scanning is relatively slow and expensive, it seems like a good
> idea to allow re-using the results...

Well, umm.. you can just request the results? A la "iw wlan0 scan dump"?

johannes


  reply	other threads:[~2012-07-10 19:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-10 19:02 Can one program see another's scan-results? Ben Greear
2012-07-10 19:08 ` Johannes Berg
2012-07-10 19:19   ` Ben Greear
2012-07-10 19:22     ` Johannes Berg [this message]
2012-07-10 19:31       ` Ben Greear
2012-07-10 19:39         ` 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=1341948158.4475.33.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=greearb@candelatech.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