This service will be undergoing maintenance at 20:00 UTC, 2017-04-03. It is expected to last about 30 minutes
Bug 249681 - NetworkManager does not appear to save a changed/new WEP key and connect to WAP
NetworkManager does not appear to save a changed/new WEP key and connect to WAP
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
i386 Linux
low Severity low
: ---
: ---
Assigned To: Dan Williams
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-07-26 09:05 EDT by Sankarshan Mukhopadhyay
Modified: 2007-11-30 17:12 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-11-23 23:35:50 EST
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 Sankarshan Mukhopadhyay 2007-07-26 09:05:54 EDT
Description of problem:

Using NetworkManager to connect to a Wireless Access Point with a WEP key. The
WEP used to initially connect had changed in between, NetworkManager prompts for
the new WEP key, but on input (verified by ShowKey) does not save the key and
connect to the network. The same system can connect to the network when using

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

How reproducible:

Steps to Reproduce:
1. Use NetworkManager to connect to a network with 64/128 bit Hex WEP
2. Change WEP key
3. Attempt to use NetworkManager to save the new key and reconnect
Actual results:

NetworkManager prompts for new WEP key but does not connect

Expected results:

NetworkManager to save the new key and connect

Additional info:

The same machine can connect to the Wireless Network using Wifi Radar and
changing the WEP keys
Comment 1 Sankarshan Mukhopadhyay 2007-11-23 23:35:03 EST
This seems to have been fixed with F8(Werewolf). Thank you. :)

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