Bug 224922 - NetworkManager 0.6.4 no Leap support
NetworkManager 0.6.4 no Leap support
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: NetworkManager (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Dan Williams
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2007-01-27 01:04 EST by Traxtopel
Modified: 2008-05-21 12:44 EDT (History)
1 user (show)

See Also:
Fixed In Version: RHBA-2008-0369
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-21 12:44:02 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Traxtopel 2007-01-27 01:04:11 EST
Description of problem:
There is currently no LEAP support in NetworkManager 0.6.4, Dan Williams asked
me to open a ticket to get NM 0.6.5 branch added to RHEL5 image before it ships.

Version-Release number of selected component (if applicable): NetworkManager-0.6.4-6

How reproducible:
Open gui, select Connect to Other wireless network, no LEAP option.
Comment 1 Matěj Cepl 2007-01-31 09:29:23 EST
For those who are as silly as I am, LEAP is
Comment 2 Matěj Cepl 2007-01-31 09:34:46 EST
Traxtopel, could you suggest an open source implementation of the protocol or
standard document describing its implementation?
Comment 3 Traxtopel 2007-01-31 11:22:36 EST
LEAP option is available in 0.6.5 cvs tree, it is kind of important for
enterprise customers, 
Comment 5 Dan Williams 2007-12-17 11:54:43 EST
leap support committed
Comment 10 errata-xmlrpc 2008-05-21 12:44:02 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.