From owner-freebsd-current@FreeBSD.ORG Fri Jan 14 00:57:43 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 AB07216A4CE for ; Fri, 14 Jan 2005 00:57:43 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23F6F43D49 for ; Fri, 14 Jan 2005 00:57:43 +0000 (GMT) (envelope-from benjamin.becker@gmail.com) Received: by rproxy.gmail.com with SMTP id r35so280824rna for ; Thu, 13 Jan 2005 16:57:42 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=aMfTqHDe0JomBbn/Sq/xaxehhoNJ5D86oFnxNO4ETWXVNaOFoeIbFzSq2MWxo9JqMCEXrjYkvZB5ouxKELRBPhWHSo5P6PhECj/oMuM9xMRUjfn2VSjtVyLPeHQdgsVEu23lGG/Kh9v46mkOUL6VlbjSKwken5jMdboWvc/pKbY= Received: by 10.38.90.35 with SMTP id n35mr139248rnb; Thu, 13 Jan 2005 16:57:42 -0800 (PST) Received: by 10.38.73.18 with HTTP; Thu, 13 Jan 2005 16:57:42 -0800 (PST) Message-ID: <38d37be7050113165733434463@mail.gmail.com> Date: Thu, 13 Jan 2005 16:57:42 -0800 From: Ben Becker To: freebsd-current@freebsd.org In-Reply-To: <41E6FA7F.2070406@errno.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <38d37be7050111092379f2a898@mail.gmail.com> <20050113065003.GA2336@tongi.org> <38d37be7050113143868516018@mail.gmail.com> <41E6FA7F.2070406@errno.com> Subject: Re: Atheros and SIS bridging problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Ben Becker List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 00:57:43 -0000 On Thu, 13 Jan 2005 14:47:27 -0800, Sam Leffler wrote: > Those devices tunnel using a 4-address 802.11 format specifically > designed for this. Like I said, what you need is not currently > supported. The encapsulation work is actually very simple; the hard bit > is how everything ties into the system. I happen to be working on this > but results will not be available for a while. > > Sam Would this be as simple as using the struct ieee80211_frame_add4 instead of ieee80211_frame and setting the proper ToDS and FromDS values in the control settings? It looks like you've done most of the work already. Is there anything else that needs to be done aside from updating all of the net80211 and device driver functions that reference ieee80211_frame? I'm going to start working on a hack for this since I need the feature for a project I'm working on. I don't want to keep pestering you with this since you're already working on it, but I'm more than happy to help incorporate this feature in any way I can. Obviously, any tips and pointers would be greatly appreciated. -Ben