Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Comment 1RHEL Program Management
2006-12-19 18:40:39 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
inclusion.
Comment 4RHEL Program Management
2007-03-21 23:52:30 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
release.
I am in the same boat with EAP-FAST support. I was able to get NM to connect to
this EAP-FAST wireless network once, but nothing since then.
I am able to connect to the above network with wpa_supplicant. Below is the
configuration:
network={
ssid="wlan"
proto=RSN
key_mgmt=WPA-EAP
pairwise=CCMP
eap=LEAP
identity="daly"
password="password"
ca_cert=""
mode=0
disabled=0
}
This configuration was generated through wpa_gui.
I see from the above that RHEL 5.2 was to have support for this type of network.
I'm currently 5.2 but am still having issues.
Comment 23RHEL Program Management
2008-07-16 16:08:19 UTC
Development Management has reviewed and declined this request. You may appeal
this decision by reopening this request.
(In reply to comment #31)
> Support is missing in F9 and F10 as well for EAP-FAST.
Yeah, but it's not gonna show up in F9 or F10 unless openssl gets updated there too.
NM still doesn't list EAP-FAST as an option in F11. I don't have a production EAP-FAST system available, but I'm pretty sure until that option is there, NM is still dead when it comes to EAP-FAST.
Comment 37Miroslav Vadkerti
2010-06-25 12:16:36 UTC
openssl now supports EAP-FAST, please update NM to support it also
Comment 42Chris Marcantonio
2011-10-21 15:49:27 UTC
I see this BZ is filed against RHEL6, but I also see previous bugs closed as dupes of this that were filed against Fedora, so I'm not sure if this is the most appropriate place to ask about the status of this in F16 as well. Can anyone provide any insight into EAP-FAST support in F16?
This BZ looks like it is tentatively flagged for RHEL 6.3, but that doesn't help too much with understanding the when this may land in Fedora.
Upstream commits to 0.8.x branch that we need to backport for this:
NM
91a58738622c30130a2f6dfa68da3a971a596534
8679f350e901282c22c7b0da5841588f4d3306e5
81a668ba3106913e2bb233217cca89965276fd3d
editor
0285856d58e5eff391bcf324b63d7985fd4c77a2
And also these commits from 0.8.x branch:
fec7fc4e01b113651ebb5486d9100245bd78f374
977e0db633d17dcb6e9324704d275d5475981cb8
ef9ef7133f0cccadd0ccd2cf57d9bea8aeebbd41
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2012-0832.html