It seems it can set it, but I don't see any command to print out
the current value?
Thanks,
Ben
--
Ben Greear <[email protected]>
Candela Technologies Inc http://www.candelatech.com
On Mon October 4 2010 10:46:45 you wrote:
> On Mon, Oct 4, 2010 at 11:43 AM, Bruno Randolf <[email protected]> wrote:
> > On Mon October 4 2010 10:27:47 Jonathan Guerin wrote:
> >> On Sun, Oct 3, 2010 at 4:48 AM, Maxim Levitsky <[email protected]>
> >
> > 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".
>
> With iwconfig, we can set a fixed rate, shouldn't this be what we
> expect to see as the 'rate'?
it only makes sense if you set a single fixed rate.
> Speaking of, is there a particular reason why we still have to use
> iwconfig to set the rate as well?
a TX bitrate mask has been added to iw in version 0.9.21:
commit 0db5d893ecf2ce4538af6fdcae3d94f2f83757e2
Author: Johannes Berg <[email protected]>
Date: Fri Sep 24 17:44:07 2010 +0200
version 0.9.21
* transmit power support
* TX bitrate mask support
* more informative scan output
* make it build on old systems
you can use it like this, e.g.: "iw wlan0 set bitrates legacy-2.4 12 18 24"
this is much more flexible than the iwconfig way, as it allows a bitmap of TX
rates which can be used. again this is a reason why it does not make sense to
show a single TX bitrate, but i guess this TX bitmap could/should be shown
somewhere.
bruno
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.
Best regards,
Maxim Levitsky
On Mon October 4 2010 10:27:47 Jonathan Guerin wrote:
> On Sun, Oct 3, 2010 at 4:48 AM, Maxim Levitsky <[email protected]>
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
On Mon, Oct 4, 2010 at 11:43 AM, Bruno Randolf <[email protected]> wrote:
> On Mon October 4 2010 10:27:47 Jonathan Guerin wrote:
>> On Sun, Oct 3, 2010 at 4:48 AM, Maxim Levitsky <[email protected]>
> 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".
With iwconfig, we can set a fixed rate, shouldn't this be what we
expect to see as the 'rate'?
Speaking of, is there a particular reason why we still have to use
iwconfig to set the rate as well?
>
> bruno
>
Thanks,
--
Jonathan Guerin
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'...
Thanks,
Ben
>
> Best regards,
> Maxim Levitsky
--
Ben Greear <[email protected]>
Candela Technologies Inc http://www.candelatech.com
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.
Best regards,
Maxim Levitsky
On Sun, Oct 3, 2010 at 4:48 AM, Maxim Levitsky <[email protected]> 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.
>
> Best regards,
> ? ? ? ?Maxim Levitsky
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at ?http://vger.kernel.org/majordomo-info.html
>
Thanks,
--
Jonathan Guerin