On Mon, Oct 4, 2010 at 11:43 AM, Bruno Randolf <br1@xxxxxxxxxxx> wrote: > On Mon October 4 2010 10:27:47 Jonathan Guerin wrote: >> On Sun, Oct 3, 2010 at 4:48 AM, Maxim Levitsky <maximlevitsky@xxxxxxxxx> > 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 -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
