I disagree with that last comment as this isn't a LEAP issue, but rather with the configuration options available within KNetworkManager.
I can connect to any network using any valid security configuration as long as wpa_supplicant is used. If I use KNetworkManager, I can only connect consistenly to networks using Pre-Shared Keys. It doesn't matter if it is WPA or WEP and and Personal vs. Enterprise. The only configuration option that differs from the GUI and wpa_supplicant.conf is the "pairwise" option. By using wpa_supplicant and this option, I can consistenly connect to a PEAP/WPA/TKIP/MsCHAPv2/RADIUS Wireless network (please see attached working wpa_supplicant.conf file). I cannot do this using KNetworkManager - even including v0.2 from Gutsy. This issues described above are the same issues I experienced (exactly) with Edgy, Feisty, and now Gutsy (to Tribe 3 so far) with both KNetworkManger 0.1 and 0.2. I would suggest that the KNetworkManager GUI have all of the options that are available in wpa_supplicant. ** Attachment added: "'Sterilized' Working wpa_supplicant.conf file" http://launchpadlibrarian.net/8775467/wpa_supplicant.conf -- networkmanager can't use PEAP or TTLS https://bugs.launchpad.net/bugs/107321 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
