From: Pat Erley <pat-lkml@erley.org>
To: James <bjlockie@lockie.ca>
Cc: linux-wireless Mailing List <linux-wireless@vger.kernel.org>
Subject: Re: higher N rates
Date: Sat, 24 Sep 2011 11:35:23 -0400 [thread overview]
Message-ID: <4E7DF8BB.1040807@erley.org> (raw)
In-Reply-To: <4E7D4EC4.2040506@lockie.ca>
On 09/23/2011 11:30 PM, James wrote:
> $ iw dev wlan0 scan
>
> printed this for my N (only) router:
>
> Supported rates: 1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0
> Extended supported rates: 6.0 9.0 12.0 48.0
>
> Why doesn't it print the higher N rates?
I may be WAY off base here, but I believe iw dev wlan0 scan reports
what's shown in the beacons, and not what rates are actually negotiable.
Beacons only directly advertise 'pre-n' rates (the basic 802.11abg rates).
If you look at more of the scan results, you should see something like:
HT capabilities:
Capabilities: 0x11ce
HT20/HT40
SM Power Save disabled
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 0-15
HT operation:
* primary channel: 36
* secondary channel offset: above
* STA channel width: any
* RIFS: 0
* HT protection: no
* non-GF present: 0
* OBSS non-GF present: 0
* dual beacon: 0
* dual CTS protection: 0
* STBC beacon: 0
* L-SIG TXOP Prot: 0
* PCO active: 0
* PCO phase: 0
Which outlines the 802.11n parameters that your device and the AP can use
to negotiate 802.11n operation. Perhaps there is something more that should
be reported, but you'll see throughputs in the 802.11n range WHEN it's
warranted. With my DSL connection, I rarely see rates above 9mbit in use (my
DSL is 1.5mbit down).
Pat
next prev parent reply other threads:[~2011-09-24 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-24 3:30 higher N rates James
2011-09-24 15:35 ` Pat Erley [this message]
2011-09-24 18:09 ` Arend Van Spriel
-- strict thread matches above, loose matches on Subject: below --
2011-09-23 2:02 James
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=4E7DF8BB.1040807@erley.org \
--to=pat-lkml@erley.org \
--cc=bjlockie@lockie.ca \
--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 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).