Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 441230 - Can't access network with WEP key
Can't access network with WEP key
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Dan Williams
Fedora Extras Quality Assurance
Depends On:
Blocks: F9Blocker
  Show dependency treegraph
Reported: 2008-04-07 06:39 EDT by Bastien Nocera
Modified: 2008-04-10 12:13 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-04-10 12:13:20 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 Bastien Nocera 2008-04-07 06:39:31 EDT

I use a 128-bit WEP key on my local network. The key is index 1.

NetworkManager can't connect, and will ask me for a new WEP key with "Key index:
2" already selected in the dialogue.

I set index 1 in the dialogue, but gnome-keyring-manager's record of the key, as
well as the output of iwconfig show me that it's using a completely different
key (iwconfig shows the key followed by '[2]').

This worked on rawhide about a week ago, and changing to a known working kernel
doesn't fix the problem.
Comment 1 Dan Williams 2008-04-08 13:30:26 EDT
I think there's a bug in applet svn < r647 that won't accept any indexes, I think.
Comment 2 Bastien Nocera 2008-04-08 15:04:35 EDT
I'm using:
Comment 3 Dan Williams 2008-04-08 15:20:30 EDT
Yeah, can you give the NM svn3547 RPM a shot when it hits rawhide?
Comment 4 Bastien Nocera 2008-04-08 15:57:25 EDT
Build didn't quite finish it seems, but the i386 package managed to get through.

Adding to the F9Blocker so that it gets built and tagged for the RC.
Comment 5 Dan Williams 2008-04-10 12:13:20 EDT
Should have shown up in rawhide already.

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