Bugzilla – Full Text Bug Listing |
Summary: | Rates for Wi-Fi control responses are incorrectly selected | ||
---|---|---|---|
Product: | ns-3 | Reporter: | Dean Armstrong <deanarm> |
Component: | wifi | Assignee: | Dean Armstrong <deanarm> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | deanarm, nicola, ns-bugs |
Priority: | P3 | Keywords: | bug |
Version: | ns-3-dev | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://codereview.appspot.com/855042 |
Description
Dean Armstrong
2010-03-31 13:05:51 UTC
I've uploaded to codereview a proposed change to address this bug. It is here: http://codereview.appspot.com/855042 This change causes some tests to fail - specifically, the wireless/wifi-simple-adhoc-grid example, and the routing-olsr-regression testsuite. In this case it is actually the tests that are at fault (or, at least, need updating). In the wifi-simple-adhoc-grid test and the bug780-test part of the routing-olsr-regression testsuite, 802.11b rates were being requested with the Wi-Fi PHY standard left at the default of 802.11a. The fix here is to set the standard to 802.11b in the test. In the tx-regression-test part of routing-olsr-regression, the problem was that the reference traces needed to be updated given the control response rate fix. In this case I have also modified the test to set the standard to 802.11a for clarity. I have addressed these test issues in a separate changelist which is available for your perusal here: http://codereview.appspot.com/861041 Thank you very much for the detailed bug report and for the patches! I confirm this bug, the current code misinterprets the "modulation" (BPSK, QPSK, 16QAM) for the modulation class defined by section 9.6.1 in IEEE Std. 802.11-2007. I agree that your proposed fix works, the only thing I don't like is the introduction of the method WifiRemoteStationManager::GetPhy I would wait until we fix 871, to see if we can come with a modified patch that does not need this method. I am also fine with the changes to the tests and the regression traces, of course to be applied after we have a version of the patch that we agree upon. (In reply to comment #2) > I would wait until we fix 871 I mean bug 871 Fixed in changeset 6372:0fafd9716f44 on ns-3-dev. Exposed test issues and reference trace updates addressed in changeset 6373:5467d6ae6ebe. Hence marking resolved fixed. |