Bug 454342 - rt2x00 (rt61pci) fails to associate with wpa-encrypted network
rt2x00 (rt61pci) fails to associate with wpa-encrypted network
Status: CLOSED DUPLICATE of bug 453390
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
9
i686 Linux
low Severity medium
: ---
: ---
Assigned To: John W. Linville
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-07 15:58 EDT by Klaas Hölscher
Modified: 2008-07-07 16:09 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-07-07 16:09:51 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Klaas Hölscher 2008-07-07 15:58:04 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9) Gecko/2008061015 Firefox/3.0

Description of problem:
The NetworkManager uses the rt2x00-rt61pci driver as with previous versions, but after the upgrade to the mentioned kernel it fails to associate, the applet ass for the passphrase, tries to connect, asks again, ..

-------------
from dmesg:
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:0e:2e:65:99:35
wlan0: RX authentication from 00:0e:2e:65:99:35 (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:0e:2e:65:99:35
wlan0: RX AssocResp from 00:0e:2e:65:99:35 (capab=0x411 status=0 aid=193)
wlan0: invalid aid value 193; bits 15:14 not set
wlan0: associated
wlan0: switched to short barker preamble (BSSID=00:0e:2e:65:99:35)
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: switched to long barker preamble (BSSID=00:0e:2e:65:99:35)
wlan0: RX disassociation from 00:0e:2e:65:99:35 (reason=8)
wlan0: disassociated
wlan0: associate with AP 00:0e:2e:65:99:35
wlan0: RX deauthentication from 00:0e:2e:65:99:35 (reason=6)
wlan0: deauthenticated
wlan0: authenticate with AP 00:0e:2e:65:99:35
wlan0: RX authentication from 00:0e:2e:65:99:35 (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:0e:2e:65:99:35
wlan0: RX ReassocResp from 00:0e:2e:65:99:35 (capab=0x411 status=0 aid=193)
wlan0: invalid aid value 193; bits 15:14 not set
wlan0: associated
wlan0: RX disassociation from 00:0e:2e:65:99:35 (reason=8)
wlan0: disassociated
wlan0: associate with AP 00:0e:2e:65:99:35
wlan0: RX deauthentication from 00:0e:2e:65:99:35 (reason=6)
wlan0: deauthenticated
wlan0: no IPv6 routers present
wlan0: authenticate with AP 00:0e:2e:65:99:35
wlan0: RX authentication from 00:0e:2e:65:99:35 (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:0e:2e:65:99:35
wlan0: RX ReassocResp from 00:0e:2e:65:99:35 (capab=0x411 status=0 aid=193)
wlan0: invalid aid value 193; bits 15:14 not set
----------------------------

only tested against my wpa-psk encrypted network!


Version-Release number of selected component (if applicable):
2.6.25.9-76.fc9.i686

How reproducible:
Always


Steps to Reproduce:
1.enter network into network-manager
2.be asked what the phrase is
3.watch the nm-applet animation until being asked again what the pass is

Actual Results:
a dialog from nm-applet nm-applet asked for passphrase

Expected Results:
should have been associated with the network

Additional info:
Comment 1 John W. Linville 2008-07-07 16:09:51 EDT

*** This bug has been marked as a duplicate of 453390 ***

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