netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Bcm43xx-dev@lists.berlios.de, netdev@vger.kernel.org
Subject: Re: Wireless statistics for bcm43xx-d80211
Date: Wed, 19 Jul 2006 09:56:19 -0400	[thread overview]
Message-ID: <1153317379.2537.2.camel@localhost.localdomain> (raw)
In-Reply-To: <44BDB400.40408@lwfinger.net>

On Tue, 2006-07-18 at 23:24 -0500, Larry Finger wrote:
> I have gotten most things working to produce wireless statistics through /proc/net/wireless for
> bcm43xx-d80211; however, I have one problem that I have not yet been able to solve. When I do a 'cat
> /proc/net/wireless', the following is printed:
> 
> Inter-| sta-|   Quality        |   Discarded packets               | Missed | WE
>   face | tus | link level noise |  nwid  crypt   frag  retry   misc | beacon | 20
> wmaster0: 0000  100.    0.    0.       0      0      0      0      0        0
>   wlan1: 0000  100.  -26.  -67.       0      0      0      0      0        0
> 
> Based on the numbers obtained using bcm43xx-softmac for my interface, the numbers for level and 
> noise for wlan1 are what I expected (in dBm). The link value has not yet been finished. The main 
> problem is that the wireless kicker applet for KDE, which I use for a display, is only looking at 
> the first line, and never sees the wlan1 data - only the wmaster0 results.
> 
> Is there some way to detect that the master interface is being interrogated, and return data for the
> attached STA instead?

Actually, now that I think about it, why are _any_ applets
screen-scraping /proc/net/wireless anymore?  If they profess to be a
wireless applet, yet screenscrape /proc/net/wireless, that's suspect
right there.  The ioctls for status are quite well-defined and haven't
changed in a very long time (ie, SIOCGIWRANGE).

On the flip side, /proc/net/wireless has been supported since the dawn
of time (ok, not really) and is the textual interface for reporting
wireless statistic, but maybe that shouldn't be the case anymore.

Dan



  parent reply	other threads:[~2006-07-19 13:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-19  4:24 Wireless statistics for bcm43xx-d80211 Larry Finger
2006-07-19 11:13 ` Dan Williams
     [not found] ` <44BDB400.40408-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2006-07-19 12:59   ` Michael Buesch
2006-07-19 13:56 ` Dan Williams [this message]
     [not found]   ` <1153317379.2537.2.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2006-07-19 19:42     ` Larry Finger

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=1153317379.2537.2.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=Bcm43xx-dev@lists.berlios.de \
    --cc=Larry.Finger@lwfinger.net \
    --cc=netdev@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).