From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Valroff Date: Sat, 29 Oct 2011 08:41:51 +0200 Subject: [ath9k-devel] Can't associate with a particular AP In-Reply-To: <20111024185932.GG4394@kirya.net> References: <20111004183514.GC3463@kirya.net> <20111005042406.GA3734@kirya.net> <20111015045128.GP20598@kirya.net> <20111016150124.GA13160@kirya.net> <20111023142536.GA4633@kirya.net> <20111024062716.GA14603@infinet.ru> <20111024185932.GG4394@kirya.net> Message-ID: <20111029064151.GC11722@kirya.net> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org Le lundi 24 oct. 2011 ? 20:59:32 (+0200 CEST), Julien Valroff a ?crit?: > Hi Alex, > > Le lundi 24 oct. 2011 ? 08:27:16 (+0200 CEST), Alex Hacker a ?crit?: > > 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. > > No, I can confirm there is only one AP with the same ESSID. > > However, the same AP has several ESSIDs on the same channel (some being > hidden), with the following MAC addresses. The first 4 cells are "mine": > > % iwlist wlan0 scan | grep -e "Cell" -e "ESSID" > Cell 01 - Address: C6:6E:27:A6:BE:A4 > ESSID:"Kirya" > Cell 02 - Address: C6:6E:27:A6:BE:A5 > ESSID:"" > Cell 03 - Address: C6:6E:27:A6:BE:A7 > ESSID:"" > Cell 04 - Address: C6:6E:27:A6:BE:A6 > ESSID:"FreeWifi" > Cell 05 - Address: 5C:33:8E:EE:80:F9 > ESSID:"Livebox-7bd6" > Cell 06 - Address: 6A:17:33:4D:E4:4D > ESSID:"SFR WiFi Public" > Cell 07 - Address: 00:24:D4:62:A0:BD > ESSID:"FreeWifi" > Cell 08 - Address: 00:24:D4:60:F5:09 > ESSID:"FreeWifi" > Cell 09 - Address: 00:19:7D:78:69:89 > ESSID:"Livebox-A380" > Cell 10 - Address: 00:0A:78:9F:11:16 > ESSID:"OLITEC" > Cell 11 - Address: 00:24:D4:60:F5:08 > ESSID:"freebox_DIZIEN" > Cell 12 - Address: 00:17:33:4D:E4:4C > ESSID:"NEUF_E448" > Cell 13 - Address: 6A:17:33:D0:86:C5 > ESSID:"SFR WiFi Public" > Cell 14 - Address: 00:16:41:8C:72:BB > ESSID:"Livebox-f3f9" > Cell 15 - Address: 00:24:D4:62:A0:BC > ESSID:"Freebox-A6F7EB" Cell 01 - Address: 82:71:98:B6:C3:76 ESSID:"FreeWifi" Cell 02 - Address: 82:71:98:B6:C3:74 ESSID:"Kirya" Cell 03 - Address: 82:71:98:B6:C3:75 ESSID:"" Cell 04 - Address: 82:71:98:B6:C3:77 ESSID:"" Cell 05 - Address: 00:24:D4:62:A0:BD ESSID:"FreeWifi" Cell 06 - Address: 5C:33:8E:EE:80:F9 ESSID:"Livebox-7bd6" Cell 07 - Address: 00:19:70:5D:E0:03 ESSID:"Livebox-2418" Cell 08 - Address: 00:24:D4:60:F5:08 ESSID:"freebox_DIZIEN" Cell 09 - Address: 00:16:41:8C:72:BB ESSID:"Livebox-f3f9" Cell 10 - Address: 00:19:7D:78:69:89 ESSID:"Livebox-A380" Cell 11 - Address: 00:18:E7:3C:B8:92 ESSID:"Livebox-0EE8" This doesn't cause any issue with the other drivers I use, but couldn't it be the cause of the issues with ath9k? Cheers, Julien -- .''`. Julien Valroff ~ ~ : :' : Debian Developer & Free software contributor `. `'` http://www.kirya.net/ `- 4096R/ E1D8 5796 8214 4687 E416 948C 859F EF67 258E 26B1