For the past few weeks i have been trying to get NetworkManager to work with wireless. I found out it used wpa_supplicant to connect. When i tried it would always fail with a message in the logs like =================================================== Jan 28 08:33:50 [NetworkManager] <info> Error opening supplicant global control interface._ Jan 28 08:33:50 [NetworkManager] <WARN> real_act_stage2_config(): Activation (wlan0/wireless): couldn't connect to the supplicant._ =================================================== I tired the oldest version (0.5.7) and the latest in portage (0.6.4) and even the latest on the site (0.6.7) none seemed to work.. However playing around with each version i found wpa_supplicant-0.5.10 to acctually work with NetworkManager-0.6.6 It seems that theres a bug in wpa_supplicant with the global control interface, it would crash whenever accessed. Maybe we should require or even note that NetworkManager-0.6.6 should either require or recommend wpa_supplicant-0.5.10? By the way im using the ath9k driver. Reproducible: Always Steps to Reproduce: 1.install NM and wpa_supplicant(not version 0.5.10) 2.try to conenct to wireless. 3.FAIl 4.)install wpa_supplicant 0.5.10 5.)try NM.. 6.)Success! Actual Results: Success
Strike that.. its not workign again... It seems that network manager runs this command /sbin/wpa_supplicant -g /var/run/wpa_supplicant-global and when i try it.. it just freezes... lame!
This isn't a bugzilla problem.
*** Bug 256816 has been marked as a duplicate of this bug. ***
Would you mind trying networkmanger 0.7? Currently it's hard masked for testing, but should work much better than version 0.6.6 Rob
WIth networkmanager 0.7 wireless networks arent even listed anymore..
The only reason networks aren't listed is when wpa_supplicant isn't running. What happens when you run "wpa_supplicant -u". Also, did you restart dbus after installing networkmanager-0.7? NM-0.7 starts wpa_supplicant automatically over dbus, but dbus needs to know about it. You need fairly new wpa_supplicant and dbus-1.2.0+, but both should be installed as deps for NM anyway. Rob
Is this still a problem with current versions of wpa_supplicant and dbus? Please reopen if the bug still exists, thanks. fwiw, it (0.7.2 & 0.7.999) works for me with wpa_supplicant-0.6.9 && dbus-1.2.3-r1
