Date: Thu, 10 Mar 2005 21:57:35 -0800 From: Sam Leffler <sam@errno.com> To: Eric Schuele <e.schuele@computer.org> Cc: freebsd-net@freebsd.org Subject: Re: ath0 and reason 25 Message-ID: <4231334F.6040109@errno.com> In-Reply-To: <42311883.8090102@computer.org> References: <1d3ed48c050309115139a9648c@mail.gmail.com> <422FC8C5.8000407@errno.com> <42311883.8090102@computer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Eric Schuele wrote: > Sam Leffler wrote: > >> Kevin Downey wrote: >> >>> I have a dlink card that uses the ath0 driver. a DLW520. And when a >>> try to connect to an AP I get an error in dmesg "ath: association >>> failed (reason 25)" followed by the BSSID of the AP. Is there a list >>> of "reasons" somewhere? I have tried on an open AP a closed AP with >>> WEP w/o WEP and I always get the same error. The card sees the AP >>> fine. kismet finds it no problem. Sometimes wicontrol -i ath0 -L will >>> show the AP and sometimes not. >>> I have tried looking around in /src/sys/dev/ath and /src/sys/net80211 >>> for " >>> reasons" but my understanding of C / BSD internals is not very deep. >> >> >> >> You don't mention what OS version you're running. >> >> trouble% grep STATUS /usr/include/net80211/ieee80211.h|grep 25 >> IEEE80211_STATUS_SHORTSLOT_REQUIRED = 25, >> >> So the AP and station are not agreeing on how to configure the slot >> time. This may have something to do with the 11g configuration of >> your AP--e.g. did you fix long or short slot time in the AP? OTOH if >> you're running 5.x then there are some bugs in the 11g support that >> have been fixed in current and might cause this. > > > Will these fixes find their way to 5.x? Probably not. The 802.11 code in 5.x is very out of date and backmerging even the simplest changes is problematic. I'm spending all my FreeBSD time on current. Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4231334F.6040109>