Bug 453882 - WPA Supplicant fails on kernel 2.6.25.9-76 with b43 driver
WPA Supplicant fails on kernel 2.6.25.9-76 with b43 driver
Status: CLOSED DUPLICATE of bug 453390
Product: Fedora
Classification: Fedora
Component: wpa_supplicant (Show other bugs)
9
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Dan Williams
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-02 21:06 EDT by Ryan Farmer
Modified: 2008-07-07 12:17 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-07-07 12:17:48 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)
Clip of network related log entries from /var/log/messages (34.07 KB, text/plain)
2008-07-02 21:06 EDT, Ryan Farmer
no flags Details
/var/log/messages (20.06 KB, text/plain)
2008-07-03 15:28 EDT, Phil Barnes
no flags Details
Dmesg output after turning on Wireless until fail of association (5.52 KB, text/plain)
2008-07-03 20:21 EDT, Philipp Fehre
no flags Details
Messages output from connection until fail (6.46 KB, text/plain)
2008-07-03 20:21 EDT, Philipp Fehre
no flags Details

  None (edit)
Description Ryan Farmer 2008-07-02 21:06:04 EDT
Description of problem:

After updating to kernel 2.6.25.9-76, my Broadcom 4318 wireless chipset will no
longer authenticate with WPA protected networks.

How reproducible: Upgrade to kernel 2.6.25.9-76, use WPA Suppicant 0.6.3-6, use
b43 driver and firmware.

Steps to Reproduce:

1. Try to connect to any WPA protected network.
  
Actual results:

Connection fails at point of authentication.

Expected results:

Working connection.

Additional info:

Using 128-bit WEP, I am able to authenticate with the router, although this is a
nasty workaround it beats nothing, if you use this work around I suggest
creating a MAC Address whitelist on your router to bolster your network
security, and disabling wireless administration of the router.

I've created an attachment that I've clipped from /var/log/messages with related
information to this problem.
Comment 1 Ryan Farmer 2008-07-02 21:06:04 EDT
Created attachment 310871 [details]
Clip of network related log entries from /var/log/messages
Comment 2 Phil Barnes 2008-07-03 15:28:50 EDT
Created attachment 310955 [details]
/var/log/messages

Messages file filtered on NetworkManager, involves a few attempts to connect
before shutdown.
Comment 3 Phil Barnes 2008-07-03 15:32:57 EDT
It also breaks iwl3945. See my previous submission. 

Sorry I didn't realise creating an attachment would submit.
Comment 4 Philipp Fehre 2008-07-03 20:21:11 EDT
Created attachment 310968 [details]
Dmesg output after turning on Wireless until fail of association
Comment 5 Philipp Fehre 2008-07-03 20:21:48 EDT
Created attachment 310969 [details]
Messages output from connection until fail
Comment 6 Philipp Fehre 2008-07-03 20:23:42 EDT
Comment on attachment 310968 [details]
Dmesg output after turning on Wireless until fail of association

Same problem here on iwl3945 and b43 as well (own both cards) using Network
Manager as well as wpa_supplicant directly, first occurence after Kernel update
Comment 7 Philipp Fehre 2008-07-04 05:47:28 EDT
Seems to be a Kernel Problem, using the Kernel 2.6.25.6-55.fc9.i686 everything
works fine. 
Comment 8 Mark P. 2008-07-05 15:58:20 EDT
Here the same. I have a ASUS 167G. With Kernel 2.6.25.6-55.fc9.i686 it works fine.
Comment 9 Yanko Kaneti 2008-07-06 11:36:46 EDT
duplicate of bug 453390
Comment 10 Dan Williams 2008-07-07 12:17:48 EDT
yeah, it's kernel issues not the supplicant or NM.  Thanks for the dupe research!

*** 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.