Re: [ipw3945-devel] forcing 802.11a association

[James Ketrenos <jketreno linux intel com>]

dragoran wrote:
> Derek Atkins wrote:
>> Dan Williams <dcbw redhat com> writes:
>>
>>   
>>>> Like I said, "the BSSID is the same on both (a) and (b/g)", so, yes,
>>>> my AP (a D-Link) has the same BSSID/MAC on both bands.  I do not
>>>> believe there is any way for me to change this.  In fact, it uses
>>>> the same BSSID/MAC on ALL three "interfaces" (802.3, 802.11a, and 802.11b/g)
>>>>       
>>> Whee.  So drivers internally now have to differentiate a specific access
>>> point based on the (band, BSSID, SSID) tuple, which I'm pretty sure not
>>> many do.
>>>     
>> Um, all the drivers have ALWAYS done this.  The iwl3945 is the first
>> driver NOT to differentiate them!  The madwifi and the ipw3945 drivers
>> certain work "correctly" in my situation.
>>
>>   
> is this a known bug (feature?) in the iwlwifi drivers / ratescale alg ?

Sounds like a gap in mac80211's ability for userspace to specify band 
priority for association.  The drivers just tune to a band/channel and
send frames; they no longer control which AP is selected.  With ipw3945,
I believe if all things were equal, priority was given to the 2.4GHz 
band.

I believe mac80211 honors the userspace channel selection as part of its
AP selection criteria so userspace could pick the band by picking the 
channel vs. the actual band mode.

Or am I misunderstanding the question?

James

> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Ipw3945-devel mailing list
> Ipw3945-devel lists sourceforge net
> https://lists.sourceforge.net/lists/listinfo/ipw3945-devel