Description of problem: Connection to Belkin F5D7230-4 wireless router using WPA/WEP security fails as soon as "short barker preamble" activated. Failure does not occur using kernel 2.6.24.4-65. Failure occurs using NetworkManager to start interface or using older locally written startup script. Network functions normally using older kernel. T40 Laptop exhibiting failure has Atheros a/b internal card Version-Release number of selected component (if applicable): wireless-tools-29-0.2.pre22.fc8 How reproducible: Problem occurs with every connection attempt. Steps to Reproduce: 1. Unplug ethernet cable 2. Let NetworkManager attempt to connect to the network 3. Actual results: (dmesg output - WPA) e1000: eth0: e1000_watchdog: NIC Link is Down wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:11:50:0f:3c:3f wlan0: RX authentication from 00:11:50:0f:3c:3f (alg=0 transaction=2 status=0) wlan0: authenticated wlan0: associate with AP 00:11:50:0f:3c:3f wlan0: RX AssocResp from 00:11:50:0f:3c:3f (capab=0x411 status=0 aid=3) wlan0: associated wlan0: switched to short barker preamble (BSSID=00:11:50:0f:3c:3f) ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready wlan0: RX deauthentication from 00:11:50:0f:3c:3f (reason=16) wlan0: deauthenticated wlan0: authenticate with AP 00:11:50:0f:3c:3f wlan0: RX authentication from 00:11:50:0f:3c:3f (alg=0 transaction=2 status=0) wlan0: authenticated wlan0: associate with AP 00:11:50:0f:3c:3f wlan0: RX ReassocResp from 00:11:50:0f:3c:3f (capab=0x411 status=0 aid=3) wlan0: associated wlan0: switched to short barker preamble (BSSID=00:11:50:0f:3c:3f) wlan0: RX deauthentication from 00:11:50:0f:3c:3f (reason=7) wlan0: deauthenticated wlan0: no IPv6 routers present wlan0: authenticate with AP 00:11:50:0f:3c:3f wlan0: RX authentication from 00:11:50:0f:3c:3f (alg=0 transaction=2 status=0) wlan0: authenticated wlan0: associate with AP 00:11:50:0f:3c:3f wlan0: RX ReassocResp from 00:11:50:0f:3c:3f (capab=0x411 status=0 aid=3) wlan0: associated wlan0: switched to short barker preamble (BSSID=00:11:50:0f:3c:3f) wlan0: RX deauthentication from 00:11:50:0f:3c:3f (reason=7) wlan0: deauthenticated Expected results: (dmesg from successful connection) e1000: eth0: e1000_watchdog: NIC Link is Down wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:11:50:0f:3c:3f wlan0: RX authentication from 00:11:50:0f:3c:3f (alg=0 transaction=2 status=0) wlan0: authenticated wlan0: associate with AP 00:11:50:0f:3c:3f wlan0: RX AssocResp from 00:11:50:0f:3c:3f (capab=0x411 status=0 aid=3) wlan0: associated ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Additional info: Appears the "switch to short barker preamble" is the only difference between the successful and non-successful connections. My guess is that the Belkin F5D7230-4 wireless router doesn't accept the short barker preamble. "http://madwifi.org/changeset/1856" adds code to the 80211 driver to support user control of the short/long barker preamble. Unknown if problem is caused by router signalling "will accept short barker" when it doesn't or if the interface code is ignoring the response and using short all the time.
This message is a reminder that Fedora 8 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 8. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '8'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 8's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 8 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This problem started with Fedora 8, continued with Fedora 9 and still exists in Fedora 10. Fedora 9 did not have this problem at initial install from DVD. First F9 kernel update brought problem back. Fedora 10 fails from initial install, with no updates. Fedora 10 dmesg output follows. Note that the short barker preamble message no longer appears but the connection is still dropped. Examination of WPA (private key) password shows that the entered phrase was changed to a numeric string. I believe that the string matches the same one that is generated by my Ubuntu linux which works on this network. ADDRCONF(NETDEV_UP): wlan0: link is not ready eth0: no IPv6 routers present fuse init (API version 7.9) SELinux: initialized (dev fuse, type fuse), uses genfs_contexts wlan0: authenticate with AP 00:11:50:0f:3c:3f wlan0: authenticated wlan0: associate with AP 00:11:50:0f:3c:3f wlan0: RX AssocResp from 00:11:50:0f:3c:3f (capab=0x411 status=0 aid=4) wlan0: associated ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready wlan0: deauthenticated wlan0: authenticate with AP 00:11:50:0f:3c:3f wlan0: authenticated wlan0: associate with AP 00:11:50:0f:3c:3f wlan0: RX ReassocResp from 00:11:50:0f:3c:3f (capab=0x411 status=0 aid=4) wlan0: associated wlan0: deauthenticated wlan0: no IPv6 routers present wlan0: authenticate with AP 00:11:50:0f:3c:3f wlan0: authenticated wlan0: associate with AP 00:11:50:0f:3c:3f wlan0: RX ReassocResp from 00:11:50:0f:3c:3f (capab=0x411 status=0 aid=4) wlan0: associated wlan0: deauthenticated wlan0: authenticate with AP 00:11:50:0f:3c:3f wlan0: authenticated wlan0: associate with AP 00:11:50:0f:3c:3f wlan0: RX ReassocResp from 00:11:50:0f:3c:3f (capab=0x411 status=0 aid=4) wlan0: associated wlan0: disassociating by local choice (reason=3)
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.