From owner-freebsd-current@FreeBSD.ORG Sun May 30 01:46:37 2004 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 8933416A4CE; Sun, 30 May 2004 01:46:37 -0700 (PDT) Received: from herring.rabson.org (mailgate.nlsystems.com [80.177.232.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B2FB43D2F; Sun, 30 May 2004 01:46:36 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.rabson.org (herring.rabson.org [10.0.0.2]) by herring.rabson.org (8.12.11/8.12.11) with ESMTP id i4U8kO1m013605; Sun, 30 May 2004 09:46:25 +0100 (BST) (envelope-from dfr@nlsystems.com) From: Doug Rabson To: wpaul@FreeBSD.ORG (Bill Paul) Date: Sun, 30 May 2004 09:46:23 +0100 User-Agent: KMail/1.6.1 References: <20040530053703.0169216A4CF@hub.freebsd.org> In-Reply-To: <20040530053703.0169216A4CF@hub.freebsd.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200405300946.23882.dfr@nlsystems.com> X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on herring.rabson.org X-Virus-Scanned: ClamAV version 'clamd / ClamAV version 0.65', clamav-milter version '0.60p' cc: freebsd-current@FreeBSD.ORG Subject: Re: Project Evil APs 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, 30 May 2004 08:46:37 -0000 On Sunday 30 May 2004 06:37, Bill Paul wrote: > > Is 'mediaopt hostap' supposed to with the Project Evil ndis driver? > > ... > > No, not even a little. I can't even believe you asked. HostAP mode > requires the ability to send and receive non-data frames in most > cases (beacon frames, management frames, etc...). Some NICs have > firmware that let you use hostAP features without having to implement > all the logic in software. But all Windows 802.11 drivers all pretend > to be 802.3 link layer drivers, because Windows doesn't have any > 802.11 protocol support. NDIS has no API for doing monitor mode or > any hostAP tricks. So no, it's not supported, and it never will be. > > > I > > just acquired a Linksys WMP54G card which appears to use the > > Broadcom 43xx chipset. I was originally intending to build a > > home-made access point out of the thing but I can't set the hostap > > mode. > > > > Project Evil likes this thing just fine with the drivers that came > > in the box and happily sends and receives packets in adhoc mode. > > When I try something like 'ifconfig ndis0 mediaopt hostap' I just > > get a 'Device not configured' error: > > > You want to use ad-hoc mode. You don't want to bother me with silly > questions about hostap mode because it doesn't really let you do > anything you can't do with ad-hoc mode anyway. Use IPSec with > ad-hoc mode and you'll probably get better security than any > access point can give you in the first place. > Probably. Only if I can get this silly little WinME laptop to do ad-hoc as well though. The main reason for doing this is that my AP died and my gf wants to use the laptop in the garden :-). Interestingly, the inf file lists a registry key named "EnableSoftAP" which appears to suggest that support might be possible in windows with the right software. Probably involves custom drivers using private interfaces with the driver though :-(. Any chance of a native driver for the Broadcom 43xx stuff?