Bug 2532 – Inconsistencies between 802.11n MCS and NSS value reported in TXVECTOR

Bug 2532 - Inconsistencies between 802.11n MCS and NSS value reported in TXVECTOR


Summary:	Inconsistencies between 802.11n MCS and NSS value reported in TXVECTOR

Status:	RESOLVED FIXED

Product:	ns-3
Classification:	Unclassified
Component:	wifi
Version:	ns-3.26
Hardware:	All All

Importance:	P3 normal
Assigned To:	sebastien.deronne

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-10-26 15:28 UTC by sebastien.deronne
Modified:	2016-11-01 06:27 UTC (History)
CC List:	1 user (show)

See Also:

Attachments
patch to fix (3.48 KB, patch) 2016-10-26 15:28 UTC, sebastien.deronne	Details \| Diff
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description sebastien.deronne 2016-10-26 15:28:07 UTC

Created attachment 2639 [details]
patch to fix

When selecting a constant 802.11n rate higher than MCS 7 (let's choose MCS 31 as an example), we observe for the first frame sent by the non-AP station that TXVECTOR reports NSS = 1 iso 4 while the frame is transmitted using MCS 31 (i.e. 4 MIMO streams). 

After investigating, issue is due to the fact we do not read HT capabilities in the beacon frames. I also added some extra checks to stop simulation when impossible combinations are encountered.

Comment 1 sebastien.deronne 2016-10-30 04:23:23 UTC

This is the next fix I'd like to push

Comment 2 sebastien.deronne 2016-11-01 06:27:40 UTC

Pushed in changeset 12385:54003ae0e2d4