Bugzilla – Bug 151284
madwifi-ng won't associate with certain networks
Last modified: 2007-06-05 10:05:15 UTC
Recent madwifi drivers (definitely r1451, r1440) are having problems associating with certain wireless networks. I am trying to narrow down exactly what "certain" means -- some networks associate fine, some do not. This is not a NetworkManager problem. I can reproduce it with the ifcfg scripts and even with iwconfig(8) directly. Doing /usr/sbin/iwconfig ath0 essid Foo for some networks results in the driver cycling through the various frequencies and never associating with a specific AP, even through the network is visible in a scan. Conversely, with some other networks, it works fine. I don't have hard evidence on what networks do not work. Novell's onenet here in Boston no longer works. Oddly, my test WPA networks work fine. So far, all of the networks that do not work are 802.11b. While all of the networks that do work are not 802.11b. So that _might_ be it. One of the non-functioning networks is unencrypted and broadcasting and 802.11b, so it is as simple as it gets. It worked a few weeks ago fine. Now the driver won't even find the AP. I wish I could narrow down what networks work better, but this is as much as I can find.
Even if I force the correct frequency with `iwconfig ath0 essid foo freq nnn`, the AP is never associated with. It also writes "IEEE 802.11g" even though the AP is 802.11b. Do not know if that is related. Something in recent drivers just refuses to associate with recent AP's ...
Setting the frequency is not possible in managed mode. Could you try whether the card associates when you force 802.11b mode (iwpriv ath0 mode 11b)?
No, unfortunately it does not associate if I force 802.11b mode.
r1453 seems to work a lot better. Can we package that version? Our whole office is wireless-less!
Hrm, no, just packaged up r1457 and not seeing any improvement.
Created attachment 71071 [details] NM and wpa_supplicant log
Attached above is the NM and wpa_supplicant log while trying and failing to connect to a normal, broadcast, unencrypted network. Any ideas?
Fails using the "wext" wpa_supplicant driver, too. And of course iwconfig never associates (never even sees the AP).
I had also no success associating to the 11b-only AP in my office. The driver keeps dropping the association response frames. I hacked it to accept them, although I don't fully understand the frame handling code. However, it fixes this problem for me. Could you test whether it does the same for you? If so, I'll contact the upstream maintainer, maybe he can convert my hack into a sane fix. ;) Package is at /work/built/mbuild/gaspode-jg-10.
*** Bug 154991 has been marked as a duplicate of this bug. ***
jg, Sie sind ein Hero! It works. Danke! Can we please get this in autobuild as soon as possible?
Package submitted.
This is working for me now as well
Package in the next beta. I'll close this. Thanks, jg!
What version should we look for? I am hoping to get this off of hazard before we see beta7, is that a possibility?
It is mentioned in the changelog. 1451_2.6.15_rc5_git2_2-5
Err, 1451_2.6.15_rc5_git2_3-6
I've just submitted a new package to stable (also available as mbuild gaspode-jg-13), which has a cleaner fix it. Could somebody double-check whether it fixes association for you as well?