All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: linux-wireless@vger.kernel.org
Subject: ath9k:  /proc/net/wireless always shows status of 0
Date: Mon, 26 Jul 2010 12:49:09 -0700	[thread overview]
Message-ID: <4C4DE6B5.5080307@candelatech.com> (raw)

This is with today's wireless-testing (with no extra hacks)

[root@a230-ath9k ~]# cat /proc/net/wireless
Inter-| sta-|   Quality        |   Discarded packets               | Missed | WE
  face | tus | link level noise |  nwid  crypt   frag  retry   misc | beacon | 22
  wlan0: 0000   67.  -43.  -256        0      0      0      0      0        0

The interface is running WPA and is passing traffic, so I'd expect some sort of
useful status.  Is this a known issue?

[root@a230-ath9k ~]# iwconfig wlan0
wlan0     IEEE 802.11bgn  ESSID:"candela-n"
           Mode:Managed  Frequency:2.412 GHz  Access Point: 00:14:D1:C6:D2:54
           Bit Rate=117 Mb/s   Tx-Power=27 dBm
           Retry  long limit:7   RTS thr:off   Fragment thr:off
           Encryption key:off
           Power Management:off
           Link Quality=66/70  Signal level=-44 dBm
           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
           Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Thanks,
Ben

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


             reply	other threads:[~2010-07-26 19:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-26 19:49 Ben Greear [this message]
2010-07-26 22:00 ` ath9k: /proc/net/wireless always shows status of 0 Ben Greear
2010-07-26 22:54   ` Luis R. Rodriguez
2010-07-26 23:17     ` Ben Greear
2010-07-26 23:30       ` Luis R. Rodriguez
2010-07-26 23:36         ` Ben Greear
2010-07-26 23:51           ` Luis R. Rodriguez
2010-07-27  6:48           ` Johannes Berg
2010-07-27  6:54             ` Luis R. Rodriguez
2010-07-27 16:20               ` Ben Greear

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=4C4DE6B5.5080307@candelatech.com \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.