From owner-freebsd-net@FreeBSD.ORG Fri Mar 11 05:56:54 2005 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B0A2116A4CE for ; Fri, 11 Mar 2005 05:56:54 +0000 (GMT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E5FB43D39 for ; Fri, 11 Mar 2005 05:56:54 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.89] ([66.127.85.89]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id j2B5ujms069720 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Mar 2005 21:56:49 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <4231334F.6040109@errno.com> Date: Thu, 10 Mar 2005 21:57:35 -0800 From: Sam Leffler Organization: Errno Consulting User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Schuele References: <1d3ed48c050309115139a9648c@mail.gmail.com> <422FC8C5.8000407@errno.com> <42311883.8090102@computer.org> In-Reply-To: <42311883.8090102@computer.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re: ath0 and reason 25 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Mar 2005 05:56:54 -0000 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