Bug 300431
Summary: | Cannot connect to a wireless network with WEP | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Cameron Meadors <cmeadors> |
Component: | NetworkManager | Assignee: | Dan Williams <dcbw> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | desktop-bugs <desktop-bugs> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 5.1 | CC: | vbenes |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-05-16 13:06:07 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Cameron Meadors
2007-09-21 14:33:43 UTC
Does NM ever ask you for a new key? If after entering the new key, does a successful connection happen? If a successful connection does happen, is the new key stored in the keyring? If the key is wrong and NM can't connect, it _should_ ask you for a new key by bringing up the wireless key dialog. If that's not coming up (yet the applet claims it's waiting for a key) then it might be bug #223119. This issues was complicated by various suspend resume testing. I was prompted for a new key after it failed to connect. I gave it the correct key and it still failed. I deleted the key from gconf and still couldn't connect. I then rebooted and tried again. This time it asked me for the key and connected. I will have to set up a test env to reproduce since I now have the new key working. Any idea if you're still seeing this with latest RHEL? Pretty sure 5.1 still had NM 0.6.x, while we udpated to NM 0.7 in 5.2. Which would require a retest. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. |