Paul, is this what you are referring to? http://www.spinics.net/lists/linux-wireless/msg19695.html
I had been getting the same errors with umd-secure-fast and am glad to hear that they should be fixed in kernel 2.6.27-rc5. Thanks for the information! Matt On Fri, 2008-09-26 at 10:40 -0400, Paul Donohue wrote: > So it turns out that the new mac80211 subsystem in the linux kernel was > generating 802.11a association request packets that our Cisco access points > didn't like. > > This has been fixed in the 2.6.27-rc5 kernel. It is NOT fixed in the > compat-wireless-old package from linuxwireless.org, so you cannot get the fix > simply by installing compat-wireless-old. > > Note that this affects all wireless drivers using the mac80211 subsystem, so > if you're using a kernel >= 2.6.22 and < 2.6.27-rc5, 802.11a will probably > not work for you on campus. > > -Paul > > On Wed, Sep 10, 2008 at 11:59:15AM -0400, Paul Donohue wrote: > > The umd-secure-fast issue is an interesting one that I hadn't noticed ... > > but now that you mention it, 802.11 isn't working for me either. > > > > umd-secure-fast and umd-fast are 802.11a only, umd-secure and umd are > > 802.11a/b/g. For me, if I switch back to the old ipw3945 drivers, 802.11a > > works fine. However, with the latest iwl3945 drivers, 802.11b/g work fine, > > but 802.11a does not work when using any of the SSIDs. After attempting to > > associate, I see messages like the following in the 'dmesg' output: > > eth1: associate with AP ... > > eth1: RX AssocResp from ... (capab=0x11 status=18 aid=1) > > eth1: AP denied association (code=18) > > > > I'm curious if you get similar messages with the ath5k driver when trying > > to associate using 802.11a, or if you're seeing a different kind of error... > > > > If anyone else on this list is having similar problems with 802.11a, I'd be > > interested in hearing about them too...
