Red Hat Bugzilla – Bug 859664
NetworkManager cannot connect to WPA2-Enterprise
Last modified: 2014-02-05 07:16:24 EST
Description of problem:
In a fresh installation of F18-Alpha, Network Manager is unable to connect to WPA2-Enterprise wireless connections.
Version-Release number of selected component (if applicable):
Network Manager - NetowrkManager-0.9.7.0-1.git20120820.fc18.x86_64
Wireless adapter details
Intel Wireless 5100 AGN
driver - iwlwifi
Driver version - 3.6.0-0.rc6.git0.2.fc18.x86_64
Steps to Reproduce:
1. Install some DE
2. Try to connect to wireless (WPA2-enterprise)
Does not connect/respond at all. Does not even show the configuration screen to enter username/password.
Show configuration screen and accept (correct) username - password combination and connect to the network.
I have not yet tried to connect to WPA-Personal (at home). I will add comment here when I have tried that.
Has it worked for you in a previous versions?
Could you please grab /var/log/message file for us and 'dmesg' output as well?
(In reply to comment #1)
> Has it worked for you in a previous versions?
I have not tried the previous versions on bare metal. The above mentioned version was the first installation on bare metal.
> Could you please grab /var/log/message file for us and 'dmesg' output as
I have attached dmesg output. I will attach the log file when I try to connect to WPA2-Enterprise tomorrow.
Just for information - WPA2-Personal connects without problem with the same version of Network Manager.
Created attachment 622590 [details]
I reinstalled with F18 beta TC2, WPA2-enterprise connects fine. I do not what changed because the NetworkManager version is the same as in F18 Alpha.
I tried GNOME and XFCE using alpha and did the same thing now. It connects fine now.
Closing then, feel free to reopen should you encounter the problem again.
Reopening the bug.
I am seeing the same problem in a fresh installation using F18-Beta-TC3 netinstall image. Could not connect to WPA2-Enterprise.
Installation was done on to a hard disk that was partitioned using anaconda and installed only GNOME-Desktop.
I have attached dmesg output and /var/log/messages.
Created attachment 626699 [details]
Created attachment 626700 [details]
Hmm, I don't see any WPA-Enterprise relevant logs.
Would you run in a terminal:
# tail -f /var/log/messages
and then try to connect to the Enterprise network and copy the log messages spit on the terminal.
What I see in the logs is gdm crash:
Oct 13 14:34:16 localhost gdm: ******************* START **********************************
Oct 13 14:34:17 localhost gdm: [New LWP 1079]
Oct 13 14:34:17 localhost gdm: [Thread debugging using libthread_db enabled]
Consider to file that against gdm.
Same problem here.
Clicking on a WPA2-Enterprise Network in the nm-applet opens the GNOME control center network pane. When trying to click on a WPA2-Enterprise network nothing happens.
Unfortunately nothing is written to the logs. So I assume this might be an UI error from within GNOME Control Center that prevents NM from doing anything because it can't be triggered by the GNOME UI.
Creating the necessary ifcfg files on a Fedora 17 machine and copying them to the F18 machine works and the connection can be established. So I guess this supports my UI Bug theory ;)
Felix, thanks for investigating.
Any chance you could verify that the UI (I think control-center and/or gnome-shell applet) doesn't create ifcfg nor instructs NM to connect (you would see the logs in /var/log/messages).
And if there's a problem please file a bug against corresponding UI.
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '18'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 18's end of life.
Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior to Fedora 18's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.