From: Sheikh <sheikh@ismb.it>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k and 802.11n STBC / SM streams
Date: Fri, 18 Mar 2016 15:53:06 +0100 [thread overview]
Message-ID: <CANje=-x=6_JzCw3-0YfWymiPmW5fG7pgAsLToTNqmEebF+9aTw@mail.gmail.com> (raw)
Hi All,
I am setting up an ad-hoc network with 802.11n with two devices having the
AR9462 chipset that have two antennas. I would like to test the performance
of 802.11n in my physical setup using STBC and Spatial Multiplexing (SM)
configurations. My questions are as follows
1) How can I check the atheros modules are using the Space-Time Block
Coding (STBC) signal processing technique or the Spatial Multiplexing (SM)
technique.
2) How can I check the number of streams that are being used
3) Is there a way to force STBC or SM along with the number of streams.
I am using iw to set up the ad-hoc network using the following commands on
both the devices:
i
*w wlan0 set type ibssip link set wlan0 upiw dev wlan0 ibss join Adhocnet
5805 HT20iw dev wlan0 set bitrates ht-mcs-5 7 sgi-5 #or iw dev wlan0 set
bitrates ht-mcs-5 15 sgi-5 *
Following are the capabilities of the chipset:
*user at system:~# iw listWiphy phy0 max # scan SSIDs: 4 max scan IEs
length: 2257 bytes Retry short limit: 7 Retry long limit: 4
Coverage class: 0 (up to 0m) Device supports RSN-IBSS. Device
supports T-DLS. Supported Ciphers: * WEP40 (00-0f-ac:1) *
WEP104 (00-0f-ac:5) * TKIP (00-0f-ac:2) * CCMP
(00-0f-ac:4) * CMAC (00-0f-ac:6) Available Antennas: TX 0x3 RX
0x3 Configured Antennas: TX 0x3 RX 0x3 Supported interface modes:
* IBSS * managed * AP * AP/VLAN *
WDS * monitor * P2P-client * P2P-GO Band 1:
Capabilities: 0x11ef RX LDPC HT20/HT40
SM Power Save disabled RX HT20 SGI 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 Bitrates (non-HT):
* 1.0 Mbps * 2.0 Mbps (short preamble supported)
* 5.5 Mbps (short preamble supported) * 11.0 Mbps (short
preamble supported) * 6.0 Mbps * 9.0 Mbps
* 12.0 Mbps * 18.0 Mbps * 24.0 Mbps * 36.0
Mbps * 48.0 Mbps * 54.0 Mbps Frequencies:
* 2412 MHz [1] (16.0 dBm) * 2417 MHz [2] (17.0 dBm)
* 2422 MHz [3] (17.0 dBm) * 2427 MHz [4] (17.0 dBm)
* 2432 MHz [5] (17.0 dBm) * 2437 MHz [6] (17.0 dBm)
* 2442 MHz [7] (17.0 dBm) * 2447 MHz [8] (17.0 dBm)
* 2452 MHz [9] (17.0 dBm) * 2457 MHz [10] (16.0 dBm)
* 2462 MHz [11] (17.0 dBm) * 2467 MHz [12] (17.0 dBm)
* 2472 MHz [13] (17.0 dBm) * 2484 MHz [14] (20.0 dBm)
Band 2: Capabilities: 0x11ef RX LDPC
HT20/HT40 SM Power Save disabled RX HT20 SGI
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
Bitrates (non-HT): * 6.0 Mbps * 9.0 Mbps
* 12.0 Mbps * 18.0 Mbps * 24.0 Mbps *
36.0 Mbps * 48.0 Mbps * 54.0 Mbps
Frequencies: * 5180 MHz [36] (15.0 dBm) * 5200 MHz
[40] (15.0 dBm) * 5220 MHz [44] (15.0 dBm) * 5240 MHz
[48] (15.0 dBm) * 5260 MHz [52] (17.0 dBm) (no IR) *
5280 MHz [56] (15.0 dBm) (no IR) * 5300 MHz [60] (15.0 dBm) (no
IR) * 5320 MHz [64] (15.0 dBm) (no IR) * 5500 MHz
[100] (16.0 dBm) (no IR) * 5520 MHz [104] (17.0 dBm) (no IR)
* 5540 MHz [108] (17.0 dBm) (no IR) * 5560 MHz [112]
(17.0 dBm) (no IR) * 5580 MHz [116] (17.0 dBm) (no IR)
* 5600 MHz [120] (17.0 dBm) (no IR) * 5620 MHz [124] (17.0
dBm) (no IR) * 5640 MHz [128] (17.0 dBm) (no IR) *
5660 MHz [132] (17.0 dBm) (no IR) * 5680 MHz [136] (17.0 dBm)
(no IR) * 5700 MHz [140] (16.0 dBm) (no IR) * 5745
MHz [149] (17.0 dBm) * 5765 MHz [153] (17.0 dBm) *
5785 MHz [157] (17.0 dBm) * 5805 MHz [161] (17.0 dBm)
* 5825 MHz [165] (17.0 dBm) Supported commands: *
new_interface * set_interface * new_key *
start_ap * new_station * set_bss * authenticate
* associate * deauthenticate * disassociate *
join_ibss * remain_on_channel * set_tx_bitrate_mask
* frame * frame_wait_cancel * set_wiphy_netns *
set_channel * set_wds_peer * tdls_mgmt *
tdls_oper * probe_client * set_noack_map *
register_beacons * start_p2p_device * set_mcast_rate
* Unknown command (104) * connect * disconnect
Supported TX frame types: * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50
0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * managed: 0x00
0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0
0xf0 * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0
0xb0 0xc0 0xd0 0xe0 0xf0 * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50
0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * mesh point:
0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0
0xf0 * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * P2P-GO: 0x00 0x10 0x20 0x30
0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 *
P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0
0xc0 0xd0 0xe0 0xf0 Supported RX frame types: * IBSS: 0x40 0xb0
0xc0 0xd0 * managed: 0x40 0xd0 * AP: 0x00 0x20 0x40 0xa0
0xb0 0xc0 0xd0 * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* mesh point: 0xb0 0xc0 0xd0 * P2P-client: 0x40 0xd0 *
P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 * P2P-device: 0x40
0xd0 software interface modes (can always be added): *
AP/VLAN * monitor valid interface combinations: * #{
managed, WDS, P2P-client } <= 2048, #{ AP, P2P-GO } <= 8, total
<= 2048, #channels <= 1, STA/AP BI must match * #{ IBSS, AP } <=
1, total <= 1, #channels <= 1, STA/AP BI must match, radar detect
widths: { 20 MHz (no HT), 20 MHz } HT Capability overrides: *
MCS: ff ff ff ff ff ff ff ff ff ff * maximum A-MSDU length
* supported channel width * short GI for 40 MHz * max
A-MPDU length exponent * min MPDU start spacing Device supports
TX status socket option. Device supports HT-IBSS. Device supports low
priority scan. Device supports scan flush. Device supports AP scan.*
Following is the allowed usage of 5 GHz channels:
*user@system:~# iw reg getcountry 00: DFS-UNSET (2402 - 2472 @ 40), (6,
20), (N/A) (2457 - 2482 @ 40), (6, 20), (N/A), PASSIVE-SCAN (2474 -
2494 @ 20), (6, 20), (N/A), NO-OFDM, PASSIVE-SCAN (5170 - 5250 @ 160),
(6, 20), (N/A), PASSIVE-SCAN (5250 - 5330 @ 160), (6, 20), (N/A), DFS,
PASSIVE-SCAN (5490 - 5730 @ 160), (6, 20), (N/A), DFS, PASSIVE-SCAN*
I would really appreciate your kind help. Thanks
--
Regards,
Sheikh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20160318/eef436a0/attachment.htm
reply other threads:[~2016-03-18 14:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CANje=-x=6_JzCw3-0YfWymiPmW5fG7pgAsLToTNqmEebF+9aTw@mail.gmail.com' \
--to=sheikh@ismb.it \
--cc=ath9k-devel@lists.ath9k.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 read-only IMAP folder(s) and NNTP newsgroup(s).