Bug 1174897
| Summary: | Wired connection with 802.1x PEAP/MSCHAPv2 not working | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | willian.oki |
| Component: | NetworkManager | Assignee: | Lubomir Rintel <lkundrak> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 21 | CC: | dcbw, jbirch, psimerda, siology.io, vsilgalis, willian.oki |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-12-02 06:05:51 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
willian.oki
2014-12-16 17:24:29 UTC
can confirm i'm also seeing this bug on my network. I've seen this with PEAP/GTC as well. In my case, however, I think it's coming from wpa_supplicant not negotiating the connection because of self-signed certificates, and NetworkManager just being the messenger of failure. Is this what's happening to you, given this log line in your message? Dec 16 15:21:56 ni-92488-0 NetworkManager[765]: <info> (em1): device state change: config -> need-auth (reason 'supplicant-disconnect') [50 60 8] hi guys! it's working ok since 2 months ago (sorry for not updating). i'm pretty sure it was an issue on my network. If anyone could get some more information from verbose supplicant debug logs, that would be great. They may contain personal information, so don't paste them in here, but feel free to send them to my email address and I"ll extract the relevant bits. Here's the procedure: 1) mv /usr/sbin/wpa_supplicant / 2) killall -TERM wpa_supplicant 3) /wpa_supplicant -dddtu (and redirect to a logfile if you like, or just copy & paste terminal output into an editor) 4) reconnect, and wait for the log spew and the connection to fail If it is indeed certificate problems, you'll see that pretty clearly in the log output. Hi Dan, When I suffered from this issue, the wpa_supplicant logs clearly stated that they were rejecting the connection because the certificate was self-signed. There's some fun to be had there in terms of user experience around "If you're not going to accept the certificate, don't continue to prompt me for my password", but I think that's outside the remit of this ticket. Since I explicitly added a path to the certificate to use, the wpa_supplicant error disappears, and the original issue here disappears also. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 EOL if it remains open with a Fedora 'version' of '21'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 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 this bug is closed as described in the policy above. 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed. |