linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC 1/2] wireless:  Show sta_flags for status in /proc/net/wireless
Date: Thu, 30 Sep 2010 09:49:21 -0700	[thread overview]
Message-ID: <4CA4BF91.8070008@candelatech.com> (raw)
In-Reply-To: <1285861161.5137.5.camel@jlt3.sipsolutions.net>

On 09/30/2010 08:39 AM, Johannes Berg wrote:
> On Thu, 2010-09-30 at 08:31 -0700, Ben Greear wrote:
>
>> It would of course be easy to map them to a stable set of flags, but if you
>> don't want to fix /proc/net/wireless anyway, then I might as well do minimal changes
>> to make it easier to keep the patch in my own tree.
>>
>> Aside from listening to 'iw event', is there any way to know if a STA is scanning,
>> authenticated, associated, etc?  Some of this can be obtained from debugfs, but
>> that's not a fun api to code against...
>
> You can't get scanning, but auth/assoc should be visible in "iw dev
> <iface>  scan dump"

I find it a bit frustrating that it takes so many different commands
to find the information I'm looking for.

It looks like I'll need to integrate at least:

The information for the in-use BSS from 'scan dump', the info
from 'info', 'survey dump' for the active channel,
'station dump' (with additional of at least the counters that
used to be found in /proc/net/wireless),

If I were only doing one or two STA interfaces, that's not so bad,
but if I want to do hundreds, and update info relatively often,
that's going to be a lot of overhead!

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


      reply	other threads:[~2010-09-30 16:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-29 23:57 [RFC 1/2] wireless: Show sta_flags for status in /proc/net/wireless greearb
2010-09-29 23:57 ` [RFC 2/2] wireless: Report noise to /proc/net/wireless greearb
2010-09-30  7:45   ` Johannes Berg
2010-09-30 15:35     ` Ben Greear
2010-09-30  7:43 ` [RFC 1/2] wireless: Show sta_flags for status in /proc/net/wireless Johannes Berg
2010-09-30 15:31   ` Ben Greear
2010-09-30 15:39     ` Johannes Berg
2010-09-30 16:49       ` Ben Greear [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=4CA4BF91.8070008@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=johannes@sipsolutions.net \
    --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).