From owner-freebsd-current@FreeBSD.ORG Wed Jul 20 05:03:15 2005 Return-Path: X-Original-To: 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 1F75416A41F for ; Wed, 20 Jul 2005 05:03:15 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6A5243D45 for ; Wed, 20 Jul 2005 05:03:14 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.94] ([66.127.85.94]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id j6K53Dms027203 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Jul 2005 22:03:14 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <42DDDB32.1080402@errno.com> Date: Tue, 19 Jul 2005 22:03:46 -0700 From: Sam Leffler Organization: Errno Consulting User-Agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Craig Boston References: <20050720044904.GA59111@nowhere> In-Reply-To: <20050720044904.GA59111@nowhere> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: wi(4) IEEE_80211_S_SCAN support? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 20 Jul 2005 05:03:15 -0000 Craig Boston wrote: > Hi everyone, > > Okay, only after banging my head against the wall for a couple hours > trying to figure out why wpa_supplicant doesn't like my old prism2 card > (I'm pretty sure it can't do WPA but I just want to auto-assign WEP > keys...), I think it's because the wi driver just doesn't implement the > IEEE_80211_S_SCAN state. > > It wasn't until discovering that "ifconfig wi0 scan" just sits there > doing nothing that I began to suspect the new wlan infrastructure. > > So, is anybody working on the wi driver currently? I'm game for taking > a stab at implementing those but I don't want to duplicate any effort > that's already underway. > > I also wanted to check because maybe there are some gotchas that > resulted in it not being implemented in the first place :) When I brought in the new net80211 code many months ago a certain person promised he would take care of any/all wi problems. He vapourized and noone else has stepped up. If you can take a crack at fixing wi I will help you as best I can (my time is very short these days). Sam