No switches on my card. Card came already attached to the MTB when I
bought it, looks like its just the raw AR9285 chip you can see here:
http://www.qca.qualcomm.com/media/product/product_79_file1.pdf
I'll try just using each antenna alone and see if one works. So which
channel transmits can be
Adrian Chadd wrote:
> Ie, ath9k is not choosing which AP to associate with.
Well, it can..
> 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.
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
Julien Valroff wrote:
> > > Ie, ath9k is not choosing which AP to associate with.
> >
> > Well, it can..
>
> How can you force that?
Force what, exactly?
> I've tried doing this in NetworkManager with no success (ie. same
> problems as without).
I would strongly avoid NetworkManager and wpa_s
On 30 October 2011 02:32, David Summers
wrote:
> No switches on my card. Card came already attached to the MTB when I bought
> it, looks like its just the raw AR9285 chip you can see here:
Ok. Checked the underside of the NIC? :)
> http://www.qca.qualcomm.com/media/product/product_79_file1.pdf
>
On 30 October 2011 03:27, Peter Stuge wrote:
> Adrian Chadd wrote:
>> Ie, ath9k is not choosing which AP to associate with.
>
> Well, it can..
How? All ath9k is doing is providing the raw frames to mac80211. The
decision as to what to associate to is done further up in the stack.
(The same is don
Adrian Chadd wrote:
> >> Ie, ath9k is not choosing which AP to associate with.
> >
> > Well, it can..
>
> How? All ath9k is doing is providing the raw frames to mac80211.
By "it" I of course mean "the kernel" :p
//Peter
___
ath9k-devel mailing list
at
