From owner-freebsd-current@FreeBSD.ORG Sun Jul 6 21:39:34 2003 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 8004637B401; Sun, 6 Jul 2003 21:39:34 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3466843F85; Sun, 6 Jul 2003 21:39:32 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.8/8.12.3) with ESMTP id h674dQdP021509; Sun, 6 Jul 2003 22:39:26 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 07 Jul 2003 04:32:59 +0900 (JST) Message-Id: <20030707.043259.85411876.imp@bsdimp.com> To: ru@freebsd.org From: "M. Warner Losh" In-Reply-To: <20030706063342.GA7846@sunbay.com> References: <20030705221335.GC66426@sunbay.com> <20030706.094038.96603831.imp@bsdimp.com> <20030706063342.GA7846@sunbay.com> X-Mailer: Mew version 2.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: sam@errno.com cc: dgilbert@velocet.ca cc: freebsd-current@freebsd.org Subject: Re: [current] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2003 04:39:34 -0000 In message: <20030706063342.GA7846@sunbay.com> Ruslan Ermilov writes: : Uh sorry, it was very late in the night here; of course I meant Lucent : chipsets when asking if they also support host-ap mode. What are : these add-ins you're talking about? The add-ins that I'm talking about are what is known as a tertiary firmware. This firmware is downloaded by the 'host' into the card so that it can do the ap functionality. There's an authentication api to the host, but I only know about it in general terms.... : I'm mostly interested in the bridge(4) functionality. OK. Keep in mind that 802.11 isn't the same as 802.3 ethernet. There are a number of different things that need to happen for devices to work as well as special tags that bridging woul dneed to work. This is basically the hostap functionality. : As I understand, to do briding, the card should be able to send : frames with arbitrary MAC addresses, and when not in host-ap mode, : Lucent based chipsets do not allow this (i.e., you see with : tcpdump(1) that packets is written to wi0 interface, but the other : end doesn't receive the frame). Some versions of lucent firmware support these sorts of things, in addition to receiving all packets off the air, but most versions do not. I think that the receive all packets was the only one available in public firmware, and then only a few select versions. : What surprises me here, is that : these same cards appear to work (by forwarding arbitrary Ethernet : frames) when inserted into Lucent-based APs. Does anyone have a : valid explanation to this? Is this an artificial limitation on : these cards to limit their commercial use, or am I missing an : obvious? The reason they work when inserted into AP is due to the tertiary firmware that I alluded to above... Warner