Is there any progress on the Enterprise aspects of this bug? It seems that NM is trying too hard and specifying more parameters than are required in most cases by wpa_supplicant. Some method of not specifying the phase2 authentication options would be very interesting to see as, at least in my case, wpa_supplicant authenticates perfectly (and quickly) without these options. I'm sure they were added with the best of intentions to support those people that need to specify them but a way of skipping that phase would be good.
For accessing my work network I've now resorted to a script to stop NM, unload and reload the iwlagn driver, start wpa_supplicant and then run dhclient after authentication completes. The entire script execution takes about as long as a single rotation of the connect animation in nm-applet.
Is there any progress on the Enterprise aspects of this bug? It seems that NM is trying too hard and specifying more parameters than are required in most cases by wpa_supplicant. Some method of not specifying the phase2 authentication options would be very interesting to see as, at least in my case, wpa_supplicant authenticates perfectly (and quickly) without these options. I'm sure they were added with the best of intentions to support those people that need to specify them but a way of skipping that phase would be good.
For accessing my work network I've now resorted to a script to stop NM, unload and reload the iwlagn driver, start wpa_supplicant and then run dhclient after authentication completes. The entire script execution takes about as long as a single rotation of the connect animation in nm-applet.
Thanks,
Mark.