Re: NM is not being smart in a specific situation

[JP Rosevear <jpr novell com>]

On Thu, 2006-08-17 at 23:09 -0300, Thiago Bauermann wrote:
> Hey folks,
> 
> For some weird reason some days there is an ad hoc, non encrypted AP
> with the same
> SSID of the corporate network I'm trying to connect to. I don't know
> if it's
> the IT department playing games or just some fellow co-worker trying
> to 
> setup his own network in the office. The fact is that the Ad-Hoc AP
> confuses 
> NM,  which tries to connect to it instead of the right master AP.
> 
> I think there's something wrong here. NM should be smart enough to
> connect to the right 
> AP and not be fooled by a mere Ad-Hoc AP with a clashing ESSID. I feel
> this is even
> a security issue, because it is a way to fool NM to connect to an AP
> it shouldn't...
> 
> I see these options to make NM work better in this scenario: 
> 
> 1. NM should try to connect only to APs with BSSIDs which it has
> already connected to in the past
> (i.e., a BSSID which is stored in
> gconf's /system/networking/wireless/networks/<ESSID>/bssids)

It does this already.

-JP
-- 
JP Rosevear <jpr novell com>
Novell, Inc.