From owner-freebsd-net@FreeBSD.ORG Tue Apr 18 11:14:32 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9121716A401; Tue, 18 Apr 2006 11:14:32 +0000 (UTC) (envelope-from lists@wm-access.no) Received: from lakepoint.domeneshop.no (lakepoint.domeneshop.no [194.63.248.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0BF443D69; Tue, 18 Apr 2006 11:14:31 +0000 (GMT) (envelope-from lists@wm-access.no) Received: from [192.168.9.8] (gw1.arcticwireless.no [80.203.184.14]) (authenticated bits=0) by lakepoint.domeneshop.no (8.13.6/8.13.6) with ESMTP id k3IBERRu026098 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 18 Apr 2006 13:14:28 +0200 Message-ID: <4444CA13.8000405@wm-access.no> Date: Tue, 18 Apr 2006 13:14:27 +0200 From: =?ISO-8859-1?Q?Sten_Daniel_S=F8rsdal?= User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Fabian Keil References: <200604142048.20189.doconnor@gsoft.com.au> <20060414140709.20c51ebc@localhost> <200604151053.25089.doconnor@gsoft.com.au> <20060415115352.1ef82bb1@localhost> <20060415195147.GA54638@heff.fud.org.nz> <20060415232801.0dbbc8f4@localhost> In-Reply-To: <20060415232801.0dbbc8f4@localhost> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-net@freebsd.org, Andrew Thompson Subject: Re: How to use if_bridge X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2006 11:14:32 -0000 Fabian Keil wrote: > The example section has the following sentence "Such a con- > figuration could be used to implement a simple 802.11-to-Ethernet bridg= e > (assuming the 802.11 interface is in ad-hoc mode)." >=20 > I don't get the meaning of the ad-hoc mode part. In my tests if_bridge > worked in hostap mode as well, but failed in infrastructure mode. Could= > you clarify if (or why not) bridging in infrastructure mode should work= ? hostap should work, ad-hoc should work. by infrastructure you mean that the card operates as a 'station'? then it shouldn't work (correctly) as defined by the standard. commercial products tend to implement "mac-nat" or just simple dumb passthrough (which requires support on the ap side and is very much like ad-hoc mode). you would want to look into WDS for a standard way of dealing with bridging on 802.11 --=20 Sten Daniel S=F8rsdal