So I went through and compared the log messages from the (unsuccessful) plasmoid attempt to connect vs. the (successful) nm-applet attempt to connect to PEAP. There were two differences (before connection failure) that I saw:
PLASMOID: Apr 7 08:48:22 nightfall NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-EAP' Apr 7 08:48:22 nightfall NetworkManager: <info> Config: added 'auth_alg' value 'OPEN' Apr 7 08:48:22 nightfall NetworkManager: <info> Config: added 'phase2' value 'autheap=MSCHAPV2' NM-APPLET: Apr 7 09:39:47 nightfall NetworkManager: <info> Config: added 'key_mgmt' value 'IEEE8021X' Apr 7 09:39:47 nightfall NetworkManager: <info> Config: added 'phase2' value 'auth=MSCHAPV2' There were intervening lines, but they were the same for each configuration. So, perhaps networkmanager isn't recognizing 'autheap' or 'WPA-EAP', whereas it DOES regcognize 'auth' and 'IEEE8021X'? -- Network Manager Plasmoid won't connect to "WPA Enterprise" AP's in Jaunty https://bugs.launchpad.net/bugs/334052 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-widget-network-manager in ubuntu. -- kubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
