After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 560398 - Unable to connect to WPA2 Enterprise PEAP network since 0.7.0
Unable to connect to WPA2 Enterprise PEAP network since 0.7.0
Status: RESOLVED OBSOLETE
Product: NetworkManager
Classification: Platform
Component: general
0.7.x
Other Linux
: Normal major
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2008-11-11 19:59 UTC by Kristian Rasmussen
Modified: 2009-06-29 15:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
iwscan showing the network attempted to connect to (1.00 KB, text/plain)
2008-11-11 20:00 UTC, Kristian Rasmussen
Details

Description Kristian Rasmussen 2008-11-11 19:59:51 UTC
In 0.6.6 (Ubuntu hardy) I used the following configuration to connect succesfully to my school's network:

Security: WPA2 Enterprise
EAP Method: [default, don't remember which]
Key type: [default, don't remember which]
Phase 2 Type: [default, don't remember which]
Identity: myusername
Password: mypassword
Anonymous identity: [blank]
Client Certificate File: mycertificate.cer
CA Certificate File: (none)
Private Key File: (none)
Private Key Password: [blank]

After upgrading to 0.7.0 (Ubuntu intrepid), I have tried every possible configuration in the new "Connect to" dialog. This is my best bet, but does not work either:
Security: WPA & WPA2 Enterprise
Authentication: PEAP
Anonymous identity: [blank]
CA Certificate: mycertificate.cer
PEAP Version: Version 1
Inner Authentication: MSCHAPv2
User Name: myusername
Password: mypassword

Attempting to connect simply fails and returns me to the "connect to" dialog. To my non-programmer-eyes the problem could seem to be something about the "Client Certificate File" option no longer existing?
Comment 1 Kristian Rasmussen 2008-11-11 20:00:53 UTC
Created attachment 122450 [details]
iwscan showing the network attempted to connect to
Comment 2 Dan Williams 2008-11-12 15:31:24 UTC
Try switching the PEAP version to 0.  Does that work?
Comment 3 Kristian Rasmussen 2008-11-12 15:33:02 UTC
No, doesn't change anything.
Comment 4 Yoann Juet 2008-12-17 20:12:56 UTC
Same issue after upgrading to NM 0.7. WPA and WPA2 Enterprise encryption modes seem to be broken. Like many others, I cannot connect to the international wireless roaming service eduroam (http://www.eduroam.org) now propagated to my University.
Comment 5 Kristian Rasmussen 2009-01-22 15:38:15 UTC
This seems to be the same: https://bugzilla.redhat.com/show_bug.cgi?id=388471

Has that fix been included upstream? And if so, has the Ubuntu team taken notice of it?
Comment 6 Dan Williams 2009-01-22 16:07:08 UTC
Fedora tracks upstream NetworkManager very closely, so the bug is definitely fixed upstream.  You'll have to ping the Ubuntu guys to see if they have pulled it in.
Comment 7 Tobias Mueller 2009-06-29 15:02:00 UTC
I assume this issue is OBSOLETE as per comment #6. If not, please reopen.