[ath9k-devel] Unreliable connection with AR5008 (AR5416/AR2122)

[Andrej Podzimek <andrej@podzimek.org>]

> That's a pretty wild conclusion given that minstrel is not used on
> ath9k. ath9k uses its own rate control algorithm. Can you please try
> bisecting between 2.6.29 and 2.6.30? It would be of much help.

So the ieee80211_default_rc_algo option of mac80211 has no meaning at all?

Unfortunately, I can't find the commit that caused the problem. Don't have enough time for so many compilations and experiments. Anyway, there have been disassociation problems since I bought the card, so I'm not perfectly sure if the failures were absent or just hidden by the fact that there were few people walking thorugh the building during summmer holidays.

Anyway, a slightly modified version of my question: Are there any alternative rate control algorithms? Trying one of them might be a good thing to start with...

> What AP do you have? What AP setup settings do you have?

I tried three (or perhaps even more) APs. The problem was the same everywhere. I only know the type of one of them: Zyxel NBG-420N. It's set to WPA2 with EAP-TLS authentication. It does *not* provide any detailed WiFi configuration (DTIM period, RTS/fragmentation threshold, beacon interval and the like).

The Zyxel AP is a standard basic AP for home computing. The other three (or more) APs are enterprise-class devices that form a big network with roaming inside a university building. Zyxel NBG-420N supports 802.11n, whereas all the other APs only support 802.11g.

Andrej



-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6087 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20091031/52eb0e39/attachment.bin