From owner-freebsd-current@FreeBSD.ORG Sun Jan 23 01:32:53 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ADFAC16A4CE for ; Sun, 23 Jan 2005 01:32:53 +0000 (GMT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D09C43D1D for ; Sun, 23 Jan 2005 01:32:53 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.92] ([66.127.85.92]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id j0N1WpWi096117 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 22 Jan 2005 17:32:53 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <41F2FED8.606@errno.com> Date: Sat, 22 Jan 2005 17:33:12 -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: Bryan Bunch References: <41F1E26E.8030200@errno.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: WPA with ath X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jan 2005 01:32:53 -0000 Bryan Bunch wrote: > I'm trying to connect to a Linksys WRT54G. I have tested the card on > the computer when booting up in XP and it connects fine via WPA. I > also tested the card in CURRENT with WPA disabled and the card > connected fine. There's nothing useful in the log you included. You can get the reason code sent by the ap by enabling association debugging in the 802.11 layer. I usually do this with the 80211debug program found in /usr/src/tools/tools/ath. Something like 80211debug +assoc+auth should suffice. Messages go to the console. I've seen postings in various forums that this AP has issues with certain firmware revs; you might check if your firmware is up to date. Past the above a packet trace is needed. Sam