the work-around mentioned above still works for me. I just verified.
I suspect that for those that find it not to work, this will be related to how 
certificates are handled. Specifically if the network demands they be present 
on the device. That should also be taken into account.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241986

Title:
  Cannot connect to WPA/WPA2, EAP-PEAP, MSCHAPV2 network

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1241986/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to