I've found that this bug is related to https://bugs.launchpad.net/bugs/41134. /usr/bin/wpa_supplicant is not listed in the process list unless you re-login to a network by using the 'connect to other wireless network' option in nm-applet. When I do login, wpa_supplicant -g /var/run/wpa_supplicant-global<#> is called, and I can see some activity going to the madwifi interface using iwenvent. I have gotten it to connect, but when a new key needs to be generated for leap, it looses the connection. I am going to try the patch by Andrew Jorgensen, and will let you know what the results are.
I've found that this bug is related to https:/ /bugs.launchpad .net/bugs/ 41134. /usr/bin/ wpa_supplicant is not listed in the process list unless you re-login to a network by using the 'connect to other wireless network' option in nm-applet. When I do login, wpa_supplicant -g /var/run/ wpa_supplicant- global< #> is called, and I can see some activity going to the madwifi interface using iwenvent. I have gotten it to connect, but when a new key needs to be generated for leap, it looses the connection. I am going to try the patch by Andrew Jorgensen, and will let you know what the results are.