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?
-Eric
Sam _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
-- Regards, Eric _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
