On Tue, 2008-06-03 at 08:28 +0200, Helmut Schaa wrote: > Am Mo 02 Jun 2008 17:00:24 CEST schrieb Dan Williams <[EMAIL PROTECTED]>: > > > On Sun, 2008-06-01 at 21:34 +0200, Will Stephenson wrote: > >> What needs to be done to get NM to autoconnect a wireless connection on > >> UserSettingsService startup? I can see KNM responding to GetSettings with > >> autoconnect=true, but NM then seems to ignore the connection. I am going > >> to > >> put some debug in NetworkManagerPolicy.c but could someone (Dan hopefully) > >> elaborate the way it should work, from a client's point of view? > > > > For wifi, look in nm-device-802-11-wireless.c, > > real_get_best_auto_connection(). That loops through all connections, > > and will match connections based on: > > > > a) if it's a wireless connection > > b) if it's autoconnect > > c) if it's got a wireless setting > > d) if it has a MAC address, if that MAC matches the device's MAC > > e) if there's a compatible AP in the device's scan list > > > > I'd suspect (e) first here actually. There may be a bug in the AP > > matching code, or the connection may just be wrong for the AP you're > > trying to connect to. If the call to nm_ap_check_compatible() for your > > AP is returning FALSE, get the iwlist output for the AP and then drill > > down into that function and see why it's returning FALSE. It's probably > > in the security stuff. > > The issue is related to (e). It's the same issue as in the mail I've > send you some days ago regarding "cipher preselection". NM will refuse > to autoconnect to a wireless connection if no ciphers are specified. > > I just worked around this issue by specifying default ciphers in KNM.
Should probably file a bug about this in bugzilla so we don't forget about it. Should be fixed eventually. Dan _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
