Re: NM is not being smart in a specific situation

[Dan Williams <dcbw redhat com>]

On Tue, 2006-08-22 at 13:36 -0400, Robert Love wrote:
> On Tue, 2006-08-22 at 12:57 -0400, JP Rosevear wrote:
> 
> > It does this already.
> 
> NM will only initiate the connection if the BSSID matches, but which AP
> it actually associates to is up to the device.  Thus NM might decide to
> connect to your corporate AP but connect instead to an Ad-Hoc of the
> same name.

Though; we had discussed storing the mode of the network in the
info-daemon/GConf/Kconfig/whatever too, and ignoring access points of
that ESSID that don't match the mode.  That sounds reasonable to me.

Dan

> The only way to fix this is to disable roaming and bind to a specific
> BSSID, which is not ideal for many users.
> 
> 	Robert Love
> 
> 
> _______________________________________________
> NetworkManager-list mailing list
> NetworkManager-list gnome org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list