|
Bugzilla – Full Text Bug Listing |
| Summary: | Inconsistencies between 802.11n MCS and NSS value reported in TXVECTOR | ||
|---|---|---|---|
| Product: | ns-3 | Reporter: | sebastien.deronne |
| Component: | wifi | Assignee: | sebastien.deronne |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ns-bugs |
| Priority: | P3 | ||
| Version: | ns-3.26 | ||
| Hardware: | All | ||
| OS: | All | ||
| Attachments: | patch to fix | ||
This is the next fix I'd like to push Pushed in changeset 12385:54003ae0e2d4 |
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.