Bug 172955 - [ath] 11n does not work in adhoc mode
Summary: [ath] 11n does not work in adhoc mode
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: wireless (show other bugs)
Version: 10.0-CURRENT
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-wireless (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-22 13:20 UTC by Johann Hugo
Modified: 2018-05-28 19:44 UTC (History)
0 users

See Also:


Attachments
file.txt (8.51 KB, text/plain)
2012-10-22 13:20 UTC, Johann Hugo
no flags Details
node-1.txt (18.28 KB, text/plain; charset="UTF-8")
2012-10-22 20:19 UTC, Johann Hugo
no flags Details
node-2.txt (11.95 KB, text/plain; charset="UTF-8")
2012-10-22 20:19 UTC, Johann Hugo
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Johann Hugo 2012-10-22 13:20:00 UTC
802.11n does not work between two 802.11n wifi devices when they are configured in ADHOC mode. 11n works if the same two devices are configured as an AP/CLient mode.

HW = gateworks ARM
OS = FreeBSD 10.0-CURRENT
Build = arm-10-20121011
Wifi = RouterBOARD R52nM = AR9220

- Disabling ampdu does not have any effect - ifconfig wlanX -ampdu 
- Looks like the MCS rate stuff isn't being setup or negotiated right.

Fix: Patch attached with submission follows:
How-To-Repeat: - Configure two atheros 802.11n wifi adapters in ADHOC mode. 
- Transfer some data between the two devices. 
- Run athratestats - note that it never uses rates above 54Mbps.

static_rix (-1) ratemask 0x0
[ 250] cur rate 54  Mb since switch: packets 4 ticks 154414
[ 250] last sample (6  Mb) cur sample (0 ) packets sent 239
[ 250] packets since sample 8 sample tt 0

[1600] cur rate 54  Mb since switch: packets 1 ticks 154465
[1600] last sample (48  Mb) cur sample (0 ) packets sent 36699
[1600] packets since sample 6 sample tt 644

   TX Rate     TXTOTAL:TXOK       EWMA          T/   F     avg last xmit
[ 9  Mb:1600]        1:1        (100.0%)        1/   0  1848uS 27480
[18  Mb:1600]       21:21       (100.0%)       21/   0  1124uS 39024
[24  Mb:1600]       63:63       (100.0%)       70/   0  1000uS 39117
[36  Mb: 250]        1:1        (100.0%)        1/   0   464uS 27378
[36  Mb:1600]     1976:1976     (100.0%)     2133/   0   909uS 39130
[48  Mb:1600]    13231:13231    (100.0%)    14283/   0   675uS 39130
[54  Mb: 250]      238:238      (100.0%)      238/   0   444uS 154482
[54  Mb:1600]    21407:21407    (100.0%)    23177/   0   644uS 154465
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2012-10-22 16:52:32 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-wireless

reclassify.
Comment 2 Adrian Chadd freebsd_committer 2012-10-22 20:57:42 UTC
Right, it looks like the adhoc nodes are advertising HTCAP in the
beacons; however it's not actually treating that node as HT capable.

Something needs to "upgrade" those nodes to HT.


Adrian
Comment 3 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 19:44:22 UTC
batch change:

For bugs that match the following
-  Status Is In progress 
AND
- Untouched since 2018-01-01.
AND
- Affects Base System OR Documentation

DO:

Reset to open status.


Note:
I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.