55

My university uses WPA2 Enterprise encryption for students to login their wireless. In NetworkManager I have keyed in everything that they needed

  • Security : WPA & WPA2 Enterprise
  • Authentication : Protected EAP (PEAP)
  • CA certificate is not needed
  • PEAP version : Automatic
  • Inner authentication : MSCHAPv2
  • Username and Password are correct.

Everytime I try to connect, I get a window asking me to input my password over and over again

  • 2
    I have the same problem on my work's WPA2/PEAP/MSCHAPv2 network. I know this is old, but as of today, it still doesn't work on Ubuntu including the release candidate 19.04. However, I was fiddling with Fedora 29 and connecting works right away! This also works right away on Arch using Xorg and GNOME/NetworkManager GUI or KDE and NetworkManager. I'm not sure why it doesn't on Ubuntu/Mint/Debian/or OpenSUSE distributions like it does on Arch and Fedora >=29. (note it does NOT work on Fedora 28. I had the same input password dialog over and over just like you on Fedora 28). – FrostedCookies Mar 15 at 5:43
  • Is this a good reason to migrate to Fedora? – Leonardo Castro May 6 at 12:16
37

There is a bug report here: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1104476

A workaround is to remove the line

system-ca-cert=true

from the configuration file found in /etc/NetworkManager/system-connections/

  • It worked for me, I had exactly the same issue as the OP. – Vincenzo Pii Mar 26 '14 at 8:20
  • 2
    still happening on 14.04 (current beta) – prusswan Apr 12 '14 at 7:29
  • Yep, still in 14.04. – Reece Jun 4 '14 at 20:25
  • still doesn't work without this line... – Sanjay Manohar Jul 29 '14 at 22:28
  • 1
    This answer did not work for me. The line isn't present in later ubuntu versions. Oddly I have the same symptoms in Fedora version 28 but version 29 now works (arch does as well) OpenSUSE both tumbleweed and Leap15 don't work. Ubuntu 18.04, 18.10 and todays' 19.04 preview snapshot do not work. There's some setting that must be causing the issue that is not longer present in Fedora 29 or Arch but remains in Ubuntu that causes this issue. – FrostedCookies Mar 15 at 5:53
24

Here's a work around.

  1. Open a terminal (Alt + F2) and run the following commands:

    cd /etc/NetworkManager/system-connections
    sudo touch SSID #SSID is the name of the profile, e.g. eduroam
    sudo nano SSID
    
  2. Then edit the "SSID" profile as following:

    [ipv6]
    method=auto
    
    [connection]
    id=SSID #(e.g.EDUroam)
    uuid=9e123fbc-0123-46e3-97b5-f3214e123456 #unique uuid will be created upon creation of this profile
    type=802-11-wireless
    
    [802-11-wireless-security]
    key-mgmt=wpa-eap
    auth-alg=open
    
    [802-11-wireless]
    ssid=SSID
    mode=infrastructure
    mac-address=0A:12:3C:DA:C1:A5
    security=802-11-wireless-security
    
    [802-1x]
    eap=peap;
    identity=studentid123123
    phase2-auth=mschapv2
    password=mypass123123
    
    [ipv4]
    method=auto
    

Modify the above file and it should work.

  • 3
    It works! Thanks @keith! Here are the changes I had to do: (1) removed the line system-ca-cert=true and (2) replaced password-flags=1 with password=mypassword. – Marcelo Jul 24 '14 at 12:57
7

I had the same problem at work I followed the instructions and changed the system-ca-cert=false but I also had to go in and change the wireless driver settings once I made the changes it connected right up. check out the link where I got the info below

http://wireless.kernel.org/en/users/Documentation/wpa_supplicant

-o<driver> and -O<ctrl>

/usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.service

[D-BUS Service]
Name=fi.epitest.hostap.WPASupplicant
Exec=/sbin/wpa_supplicant -u -f /var/log/wpa_supplicant.log
User=root

[D-BUS Service]
Name=fi.epitest.hostap.WPASupplicant
Exec=/sbin/wpa_supplicant -u -onl80211 -O/var/run/wpa_supplicant
User=root
  • Appending the second entry to my file worked for me, thanks! – Matthew Read Jun 16 '15 at 21:17
  • Adding -onl80211 solved for me, thanks! – Tamas Hegedus Mar 17 '16 at 11:22
2

You might also need to specify the Domain of your enterprise by adding it before the username like so: Domain Name\Username beside commenting/deleting the above mentioned line..

0

I assume that you're using self-signed certificate (you said: "CA certificate is not needed"). If so, make sure that the certificate is trusted by you when establishing the connection.

  • 3
    No, by not needed I mean they do not require us to use any certificate while connecting. – Balraj McCoy Apr 10 '13 at 11:02
  • 1
    I don't understand what's the purpose of using PEAP without the certificate, but OK. Are you able to connect on any other OSes than Ubuntu? I'm having the same WiFi infrastructure in my company, so maybe I'll be able to help. – Guardian Apr 10 '13 at 11:20
  • I'm able to connect using Windows fine. There's a guide on Windows connection here : studentprojects.wordpress.com/tutorial/… which I followed on Windows and it worked fine. Tried replicating it in Ubuntu and it failed. – Balraj McCoy Apr 10 '13 at 12:14
  • @Guardian you've apparently never tried PEAP-MSCHAPv2. First you connect only with username and password, then it allows you to download certificate. I've seen in this in around 5 universities already. And I have no idea how to download certificate after I've connected to network. wicd allows to connect without certificate. – holms Jan 18 '17 at 6:55
  • I too do not need to download a certificate for work on any device (MacOS, iOS, Android, or Windows 10. Just Linux has problems. However oddly, the same exact config on Fedora 29 works but Fedora 28 doesn't. It doesn't work on any version of ubuntu including the 19.04 release candidate despite it using a newer version of kernel, NM, and wpa_supplicant – FrostedCookies Mar 15 at 5:45
0
  1. Try resetting your password (by contacting the sys admin or using an online form to send password reset link to your email address)
  2. via network manager gui, edit the wifi connection to update the password field with the new one and save.
  3. Reconnect to your wifi and it should be working now!

protected by Community Jun 17 '15 at 0:48

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.