You mean the ignore CA certificate checkbox? On my system it seems to work fine. If checked, it doesn't ever ask for a cert; in the edit connections window, under the wireless security tab, the "No CA certificate is required" checkbox remains checked; and there is no mention of CA certs in /etc/NetworkManager/system-connetcions/[NetworkName]. So this bit seems fine to me. What's bothering me, is that nonetheless it just doesn't connect anymore. I can't check if using a cert would make any difference, as my faculty doesn't provide one. But I assume Zacharias did test it both ways (CA and no-CA), getting same results. It could easily be related to a kernel update, though. Or to a NetworkManager one, since this is happening on at least three differently branded cards: your Intel, my Atheros and Sacharias' Broadcom. And all three brands are VERY common, btw...
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1473088 Title: network manager peap mschapv2 authentication stopped working Status in network-manager-applet package in Ubuntu: Confirmed Bug description: Probably in a recent update, the connection to our MSCHAPv2 / PEAP network with security set to WPA/WPA2 Enterprise. It worked a few weeks back, but not any more. Many users have issues that are posted here: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1104476 Decided to make a new bug report because it is probably a new issue. Trying to connect fails and throws another screen where the password can be filled in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1473088/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
