From owner-freebsd-net@FreeBSD.ORG Thu Mar 10 04:09:57 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 13B8016A4CE for ; Thu, 10 Mar 2005 04:09:57 +0000 (GMT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDF5E43D41 for ; Thu, 10 Mar 2005 04:09:56 +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 j2A49ums062890 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 9 Mar 2005 20:09:56 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <422FC8C5.8000407@errno.com> Date: Wed, 09 Mar 2005 20:10:45 -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: Kevin Downey References: <1d3ed48c050309115139a9648c@mail.gmail.com> In-Reply-To: <1d3ed48c050309115139a9648c@mail.gmail.com> 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: Thu, 10 Mar 2005 04:09:57 -0000 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. Sam