Wireshark-bugs: [Wireshark-bugs] [Bug 8894] New: Tx MCS set is not interpreted properly in WLAN
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 03 Jul 2013 18:40:56 +0000
Bug ID 8894
Summary Tx MCS set is not interpreted properly in WLAN beacon frame
Classification Unclassified
Product Wireshark
Version SVN
Hardware x86
OS All
Status UNCONFIRMED
Severity Normal
Priority Medium
Component Wireshark
Assignee bugzilla-admin@wireshark.org
Reporter sriramkishan@gmail.com
CC chaitanya.mgit@gmail.com 

Created attachment 11141 [details]
beacon frame with HT capabilty info

Build Information:

--
Summary:Transmit MCS set is not interpreted properly in the Wireshark.

Description:
In the beacon HT capabilities even for a 2x2 or 3x3 AP (supporting multiple Tx
spatial streams ) the Tx max number of spatial streams is always intepreted as
following
" Tx Maximum Number of Spatial Streams Supported: 1 spatial stream (0x0000)"
which is incorrect.

With reference to the IEEE standard 802.11-2012 table 8.126 (pg 608)

According to the table spatial
Tx Maximum Number Spatial Streams Supported is when transmitting:
Set to 0 for 1 spatial stream
Set to 1 for 2 spatial streams
Set to 2 for 3 spatial streams
Set to 3 for 4 spatial streams

Only the above one is considered without considering the conditions mentioned
in the table. 
This mis-interpretation needs to be fixed to show the correct Tx maximum number
of spatial streams supported by the AP.

check the beacon frame attached for reference.

You are receiving this mail because:
  • You are watching all bug changes.