From: Felix Fietkau <nbd@openwrt.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] how to config AR9280 for operation as 1X1 or other ideas
Date: Tue, 29 Mar 2011 17:28:11 +0200 [thread overview]
Message-ID: <4D91FA8B.5050606@openwrt.org> (raw)
In-Reply-To: <AANLkTi=3kmv6T4H_scdFkGtk09exKjD0RYKprHXmQB-6@mail.gmail.com>
On 2011-03-29 5:16 PM, Larry Vaden wrote:
> On Tue, Mar 29, 2011 at 9:36 AM, Felix Fietkau<nbd@openwrt.org> wrote:
>>
>> In order to debug this properly, please send a dump of the rate control
>> stats of both sides:
>> cat /sys/kernel/debug/ieee80211/phy0/netdev:wlan0/stations/*/rc_stats
>>
>> And also a dump of the channel busy time:
>> iw wlan0 survey dump
>>
>> This might help narrow down the cause of this issue.
>>
>> - Felix
>
> Felix, this is from the AP. Similar information from the CPE will
> require a short trip since the connection is not good enough to
> support ssh. Information from the CPE will follow shortly. This
> information is before your recommended changes.
>
> root at OpenWrt:~# cat /etc/config/wireless
> config wifi-device radio0
> option type mac80211
> option channel 5
> option macaddr 00:15:6d:4e:f1:46
> option hwmode 11ng
> option htmode HT5
HT5? Did you add any custom patches, or is this a configuration error?
> list ht_capab SHORT-GI-40
> list ht_capab TX-STBC
> list ht_capab RX-STBC1
> list ht_capab DSSS_CCK-40
> # REMOVE THIS LINE TO ENABLE WIFI:
> option disabled 0
> option uapsd 0
What's the 'uapsd' option for?
> root at OpenWrt:~# cat
> /sys/kernel/debug/ieee80211/phy0/netdev:wlan0/stations/*/rc_stats
> type rate throughput ewma prob this prob this
> succ/attempt success attempts
> HT20/LGI t MCS0 6.1 98.5 100.0 0( 0)
> 148 199
> HT20/LGI PMCS1 7.1 60.4 12.5 0( 0)
> 413 533
> HT20/LGI MCS2 5.8 35.2 0.0 0( 0)
> 2183 2898
> HT20/LGI MCS3 4.8 23.1 0.0 0( 0)
> 2743 4346
> HT20/LGI MCS4 4.4 15.6 0.0 0( 0)
> 6744 12776
> HT20/LGI MCS5 0.0 5.9 0.0 0( 0)
> 8 123
> HT20/LGI MCS6 0.0 0.0 0.0 0( 0)
> 0 106
> HT20/LGI MCS7 0.0 0.0 0.0 0( 0)
> 0 106
> HT20/LGI T MCS8 9.6 82.2 100.0 1( 1)
> 267 392
> HT20/LGI MCS9 7.4 35.7 25.0 0( 0)
> 4434 6183
> HT20/LGI MCS10 0.0 0.0 0.0 0( 0)
> 110 398
> HT20/LGI MCS11 0.0 0.0 0.0 0( 0)
> 2 106
> HT20/LGI MCS12 0.0 0.0 0.0 0( 0)
> 0 104
> HT20/LGI MCS13 0.0 0.0 0.0 0( 0)
> 0 106
> HT20/LGI MCS14 0.0 0.0 0.0 0( 0)
> 0 106
> HT20/LGI MCS15 0.0 0.0 0.0 0( 0)
> 0 106
>
> Total packet count:: ideal 15455 lookaround 1661
> Average A-MPDU length: 1.0
> type rate throughput ewma prob this prob this
> succ/attempt success attempts
> HT20/LGI TtPMCS0 1.9 30.5 25.0 1( 4)
> 240 1331
> HT20/LGI MCS1 0.0 0.0 0.0 0( 0)
> 0 2
> HT20/LGI MCS2 0.0 0.0 0.0 0( 0)
> 0 2
> HT20/LGI MCS3 0.0 0.0 0.0 0( 0)
> 0 2
> HT20/LGI MCS4 0.0 0.0 0.0 0( 0)
> 0 2
> HT20/LGI MCS5 0.0 5.9 0.0 0( 0)
> 1 46
> HT20/LGI MCS6 0.0 0.0 0.0 0( 0)
> 0 2
> HT20/LGI MCS7 0.0 0.0 0.0 0( 0)
> 0 3
> HT20/LGI MCS8 0.0 6.9 0.0 0( 0)
> 35 174
> HT20/LGI MCS9 0.0 9.2 0.0 0( 0)
> 27 108
> HT20/LGI MCS10 0.0 6.9 0.0 0( 0)
> 14 115
> HT20/LGI MCS11 0.0 0.0 0.0 0( 0)
> 0 2
> HT20/LGI MCS12 0.0 0.0 0.0 0( 0)
> 0 1
> HT20/LGI MCS13 0.0 0.0 0.0 0( 0)
> 0 3
> HT20/LGI MCS14 0.0 0.0 0.0 0( 0)
> 0 3
> HT20/LGI MCS15 0.0 0.0 0.0 0( 0)
> 0 3
The packet counts seem rather low, so the client is probably
reconnecting frequently. You should try to find out what triggers the
disconnects. Anything interesting in the kernel log about connection
loss? Maybe something in the wpa_supplicant debug log?
>
> Total packet count:: ideal 331 lookaround 36
> Average A-MPDU length: 1.0
> root at OpenWrt:~# iw wlan0 survey dump
> Survey data from wlan0
> frequency: 2412 MHz
> noise: -97 dBm
> channel active time: 37 ms
> channel busy time: 12 ms
> channel receive time: 0 ms
> channel transmit time: 0 ms
> Survey data from wlan0
> frequency: 2417 MHz
> Survey data from wlan0
> frequency: 2422 MHz
> Survey data from wlan0
> frequency: 2427 MHz
> Survey data from wlan0
> frequency: 2432 MHz [in use]
> noise: -107 dBm
> channel active time: 108058390 ms
> channel busy time: 21908872 ms
> channel receive time: 3395958 ms
> channel transmit time: 2010797 ms
>20% busy time with only about 5% combined rx/tx time, I guess there's
some interference on the channel which might be messing with your signal
as well. Please try different channels and compare the survey output there.
- Felix
next prev parent reply other threads:[~2011-03-29 15:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 13:33 [ath9k-devel] how to config AR9280 for operation as 1X1 or other ideas Larry Vaden
2011-03-29 14:36 ` Felix Fietkau
2011-03-29 15:08 ` Larry Vaden
2011-03-29 15:31 ` Felix Fietkau
2011-03-29 15:16 ` Larry Vaden
2011-03-29 15:28 ` Felix Fietkau [this message]
2011-03-29 16:04 ` Larry Vaden
2011-03-29 17:23 ` Felix Fietkau
2011-03-29 17:55 ` Larry Vaden
2011-03-29 16:08 ` Larry Vaden
2011-03-29 17:21 ` Felix Fietkau
2011-03-29 17:25 ` Larry Vaden
2011-03-29 17:33 ` Felix Fietkau
2011-03-29 17:38 ` Larry Vaden
2011-03-29 17:43 ` Felix Fietkau
2011-03-29 16:25 ` Larry Vaden
2011-03-29 17:20 ` Felix Fietkau
2011-03-29 18:16 ` Larry Vaden
2011-03-29 15:34 ` Larry Vaden
2011-03-29 15:38 ` Larry Vaden
2011-03-29 15:47 ` Larry Vaden
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D91FA8B.5050606@openwrt.org \
--to=nbd@openwrt.org \
--cc=ath9k-devel@lists.ath9k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.