From owner-freebsd-current@FreeBSD.ORG  Thu Jun 26 16:38:22 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 D59BF37B401
	for <freebsd-current@freebsd.org>;
	Thu, 26 Jun 2003 16:38:22 -0700 (PDT)
Received: from ebb.errno.com (ebb.errno.com [66.127.85.87])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4552843FB1
	for <freebsd-current@freebsd.org>;
	Thu, 26 Jun 2003 16:38:22 -0700 (PDT)	(envelope-from sam@errno.com)
Received: from melange.errno.com (melange.errno.com [66.127.85.82])
	(authenticated bits=0)
	by ebb.errno.com (8.12.9/8.12.9) with ESMTP id h5QNcK7N007064
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <freebsd-current@freebsd.org>;
	Thu, 26 Jun 2003 16:38:21 -0700 (PDT)	(envelope-from sam@errno.com)
Date: Thu, 26 Jun 2003 16:38:19 -0700
From: Sam Leffler <sam@errno.com>
To: freebsd-current@freebsd.org
Message-ID: <267229455.1056645499@melange.errno.com>
X-Mailer: Mulberry/3.1.0b1 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: hostap+wi 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Jun 2003 23:38:23 -0000

I'm trying to pin down a problem where prism-based AP's constructed from 
"wlan" code and the wi driver don't work right.  I'm seeing the following 
when a client/station trys to associate with an AP of this sort:

client		AP
AUTH	->
	<-	AUTH response
ASSOC	->
	<-	PROBE response
	<-	ASSOC response

and then the client retries again ad infinitum.

If you've got an AP running with recent source and a wi card please contact 
me.

	Sam