Bug 2338 – WifiMode selected for control frames may sometimes be invalid

Bug 2338 - WifiMode selected for control frames may sometimes be invalid


Summary:	WifiMode selected for control frames may sometimes be invalid

Status:	RESOLVED FIXED

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

Importance:	P5 normal
Assigned To:	sebastien.deronne

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-03-16 01:13 EDT by Tom Henderson
Modified:	2016-03-21 15:54 EDT (History)
CC List:	1 user (show)

See Also:

Attachments
patch to fix (23.14 KB, patch) 2016-03-19 04:29 EDT, sebastien.deronne	Details \| Diff
final patch (21.52 KB, patch) 2016-03-21 14:37 EDT, sebastien.deronne	Details \| Diff
Show Obsolete (1) 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 Tom Henderson 2016-03-16 01:13:30 EDT

MinstrelHt model is asserting under some configurations for different channel widths and nss.  As reported by Matias, the problem is due to the txVector used on BlockAcks, where the txVector is selected not by MinstrelHt but by the WifiRemoteStationManager using the last used mode.  The last used mode for data may result in an invalid mode for control once the control channel width drops to 20 MHz.

To reproduce on debug build of changeset 12052:f8ce7407add5:

  ./waf --run "minstrel-ht-wifi-manager-example --nss=3 --standard=802.11ac"

asserts with:

Testing 802.11ac... assert failed. cond="channelWidth != 20", file=../src/wifi/model/wifi-mode.cc, line=165

Comment 1 sebastien.deronne 2016-03-19 04:29:49 EDT

Created attachment 2348 [details]
patch to fix

This patch fixes the issues.
I still need to clean it a bit for a better readability.

Comment 2 sebastien.deronne 2016-03-21 14:37:29 EDT

Created attachment 2349 [details]
final patch

Comment 3 sebastien.deronne 2016-03-21 15:54:00 EDT

fixed in changeset 12057:3b0fe1cef64f