From mboxrd@z Thu Jan  1 00:00:00 1970
From: Alex Hacker <hacker@epn.ru>
Date: Mon, 24 Oct 2011 12:27:16 +0600
Subject: [ath9k-devel] Can't associate with a particular AP
In-Reply-To: <20111023142536.GA4633@kirya.net>
References: <20111003163605.GA3739@kirya.net>
	<CAD2nsn3=Bo9Ygzvv+9E_=JLx3CkQRqCufy+YY+SwJm=x4twsKg@mail.gmail.com>
	<20111004183514.GC3463@kirya.net> <20111005042406.GA3734@kirya.net>
	<20111015045128.GP20598@kirya.net>
	<CAD2nsn06MR5LLmi0yEC9=-DpjqREBU+Up5AAPx344nJcdh5fig@mail.gmail.com>
	<20111016150124.GA13160@kirya.net>
	<CAJ-VmokrVE+qVV721aSG933JUZ37kQ2z+j_OyYXFGEZRVvOLbQ@mail.gmail.com>
	<20111023142536.GA4633@kirya.net>
Message-ID: <20111024062716.GA14603@infinet.ru>
List-Id: <ath9k-devel.lists.ath9k.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: ath9k-devel@lists.ath9k.org

Hi guys!
There is a two APs with the same ESSID on the same frequency. The first has a
signal level 100000 times lower then the second one. The AR9285 equipped PC
is more sensetive or has better antenna then others. It tries to connect
to very weak neighboring AP with probably invalid key. I don't know why
wpa_suppicant prefer incorrect AP but IMO it is not a driver issue.
Simpliest solution is to select different ESSID for your AP.
Regards,
Alex.