From: Bruno Randolf <br1@einfach.org>
To: Jonathan Guerin <jonathan@guerin.id.au>
Cc: Maxim Levitsky <maximlevitsky@gmail.com>,
Ben Greear <greearb@candelatech.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Can 'iw' show the current tx-power?
Date: Mon, 4 Oct 2010 10:43:07 +0900 [thread overview]
Message-ID: <201010041043.07551.br1@einfach.org> (raw)
In-Reply-To: <AANLkTin0G=_JjtDytJYgwYdh=AQZs=S-518XgChA9Voo@mail.gmail.com>
On Mon October 4 2010 10:27:47 Jonathan Guerin wrote:
> On Sun, Oct 3, 2010 at 4:48 AM, Maxim Levitsky <maximlevitsky@gmail.com>
wrote:
> > On Sat, 2010-10-02 at 10:23 -0700, Ben Greear wrote:
> >> On 10/02/2010 08:21 AM, Maxim Levitsky wrote:
> >> > On Fri, 2010-10-01 at 21:37 -0700, Ben Greear wrote:
> >> >> It seems it can set it, but I don't see any command to print out
> >> >> the current value?
> >> >>
> >> >> Thanks,
> >> >> Ben
> >> >
> >> > This is pretty much last missing feature from iw.
> >>
> >> Maybe that and current operating transfer rate? I can't
> >> seem to find that anywhere other than 'iwconfig'...
> >
> > iw wlan0 link shows that.
>
> This does not work in adhoc mode:
>
> # iw dev wlan0 info
> Interface wlan0
> ifindex 4
> type IBSS
>
> # iw dev wlan0 link
> Not connected.
the TX rate is different for each station (and basically for each individual
packet too) so it does not make sense to show that for the "link" (what ever
"link" may mean in the context of ad-hoc...).
iw wlan0 station dump
can show you the last TX rate for each station, but again, the rate can and
will change on a per-packet basis.
there is no such thing as a "current transfer rate".
bruno
next prev parent reply other threads:[~2010-10-04 1:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-02 4:37 Can 'iw' show the current tx-power? Ben Greear
2010-10-02 15:21 ` Maxim Levitsky
2010-10-02 17:23 ` Ben Greear
2010-10-02 18:48 ` Maxim Levitsky
2010-10-04 1:27 ` Jonathan Guerin
2010-10-04 1:43 ` Bruno Randolf [this message]
2010-10-04 1:46 ` Jonathan Guerin
2010-10-04 2:07 ` Bruno Randolf
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=201010041043.07551.br1@einfach.org \
--to=br1@einfach.org \
--cc=greearb@candelatech.com \
--cc=jonathan@guerin.id.au \
--cc=linux-wireless@vger.kernel.org \
--cc=maximlevitsky@gmail.com \
/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).