Re: Forcing a BSSID, unchecking "Connect automatically" doesn't work

[Dan Williams <dcbw redhat com>]

On Tue, 2009-03-10 at 14:58 -0400, Chuck Anderson wrote:
> I'm trying to force a specific BSSID (testing 802.11n in fact) but 
> NetworkManager keeps trying to associate to the other BSSID's (APs) on 
> the same ESSID.  In fact, it popped up with a dialog to set up the 
> encryption settings, etc. (WPA TLS) because it couldn't use the 
> connection profile that I forced the BSSID on.  So I let it create 
> another Auto profile, set up the encryption, and then unchecked the 
> "Connect automatically"...but guess what?  It still connects 
> automatically.
> 
> How do I force NetworkManager to ignore all BSSID's for a specific 
> ESSID, except for the one I want?

Can you post some of the NM log output?  You should see NM sending
"bssid" to wpa_supplicant.  If NM sends that, and you still see the
driver connecting to random BSSIDs, then that's purely a driver problem.
You should be able to recreate the issue with plain wpa_supplicant as
well, using the 'bssid' key in a network block to tell the driver to
only use that BSSID.  This is highly driver/stack dependent, so it could
be a bug in the mac80211 stack too, if you're using one of the mac80211
drivers.

Dan