NM as it is in CVS today cannot always connect to the LEAP network in my work. Sometimes wpa_supplicant is able to associate to the AP, and some times it isn't. I discovered that setting the SSID of the network on the interface before launching wpa_supplicant solves the problem. The patch containing the change is attached. What do you think? Can you apply this? Unfortunately I don't use other wireless networks so I don't know if this has any nasty consequence...
--
[]'s
Thiago Jung Bauermann
diff -u -p -r1.84 nm-device-802-11-wireless.c
--- src/nm-device-802-11-wireless.c 4 Aug 2006 15:46:05 -0000 1.84
+++ src/nm-device-802-11-wireless.c 11 Aug 2006 04:56:25 -0000
@@ -2911,9 +2911,13 @@ real_act_stage2_config (NMDevice *dev,
NMActStageReturn ret = NM_ACT_STAGE_RETURN_FAILURE;
NMData * data = nm_act_request_get_data
(req);
const char * iface;
+ const char * essid;
gboolean ask_user = FALSE;
g_assert (ap);
+
+ essid = nm_ap_get_orig_essid (ap);
+ nm_device_802_11_wireless_set_essid (self, essid);
supplicant_cleanup (self);
_______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
