From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Valroff Date: Sat, 29 Oct 2011 18:34:20 +0200 Subject: [ath9k-devel] Can't associate with a particular AP In-Reply-To: <20111029162728.11193.qmail@stuge.se> References: <20111015045128.GP20598@kirya.net> <20111016150124.GA13160@kirya.net> <20111023142536.GA4633@kirya.net> <20111024062716.GA14603@infinet.ru> <20111024185932.GG4394@kirya.net> <20111029064151.GC11722@kirya.net> <20111029162728.11193.qmail@stuge.se> Message-ID: <20111029163420.GD11722@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 samedi 29 oct. 2011 ? 18:27:28 (+0200 CEST), Peter Stuge a ?crit?: > Adrian Chadd wrote: > > Ie, ath9k is not choosing which AP to associate with. > > Well, it can.. How can you force that? I've tried doing this in NetworkManager with no success (ie. same problems as without). > > I think the Linux wpa_supplicant code (which I bet is what's making > > decisions as to the BSSID's to be associating against, > > I can also associate without wpa_supplicant, if the AP does not > require WPA. It also fails to associate with my AP when no security is used (as explained, I have several SSID's on the same AP, one of them being used as a hotspot and gives the same issues as my private wlan). Cheers, Julien -- .''`. Julien Valroff ~ ~ : :' : Debian Developer & Free software contributor `. `'` http://www.kirya.net/ `- 4096R/ E1D8 5796 8214 4687 E416 948C 859F EF67 258E 26B1