All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrej Podzimek <andrej@podzimek.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Unreliable connection with AR5008 (AR5416/AR2122)
Date: Sat, 31 Oct 2009 21:03:31 +0100	[thread overview]
Message-ID: <4AEC9813.1020404@podzimek.org> (raw)
In-Reply-To: <43e72e890910311002y37288d92k77d3248df587d631@mail.gmail.com>


>>> 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.
> 
> This should not affect anything but.. can you try compiling and
> installin the latest git version of wpa_supplicant?

OK, compiled the current version from GIT.

I can still see deauthentications in the log. However, the network hasn't got stuck yet. It's too early to make a conclusion, I'll report back after two days or so.

There's a new line appearing in the logs before each deauthentication:

	ath9k: Two wiphys trying to scan at the same time

I haven't seen this one before.

Andrej

  parent reply	other threads:[~2009-10-31 20:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-31 15:32 [ath9k-devel] Unreliable connection with AR5008 (AR5416/AR2122) Andrej Podzimek
2009-10-31 16:03 ` Luis R. Rodriguez
2009-10-31 16:23   ` Andrej Podzimek
     [not found]   ` <4AEC6477.4010700@podzimek.org>
     [not found]     ` <43e72e890910311002y37288d92k77d3248df587d631@mail.gmail.com>
2009-10-31 20:03       ` Andrej Podzimek [this message]
2009-11-02 14:31       ` Andrej Podzimek

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=4AEC9813.1020404@podzimek.org \
    --to=andrej@podzimek.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.