Thiago Bauermann wrote: > 2006/8/11, Robert Love <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>: > > On Fri, 2006-08-11 at 02:01 -0300, Thiago Bauermann wrote: > > 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... > Well, it probably does not hurt anything. But we should not need it. > > > I forgot to mention the AP doesn't broadcast its SSID. Even when > connecting without using NM (just using wpa_supplicant) I still need > to "iwconfig ath0 essid foonet" before launching wpa_supplicant. I don't know if it's completely relevant to this discussion as I did not try Thiago's patch, but I am experiencing problems too with my AP which doesn't broadcast its SSID. It appears in the applet when I manually ask to connect, but the actual connection only succeeds after several trials. Like Thiago, when I don't use NM, I always have to to "iwconfig wlan0 essid <myssid>" before lauching wpa_supplicant.
My driver : ndiswrapper (Netgear wg511 softmac) Best regards, Timothée _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
