From owner-freebsd-current@FreeBSD.ORG Wed Oct 19 14:26:43 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 5761816A41F; Wed, 19 Oct 2005 14:26:43 +0000 (GMT) (envelope-from atrens@nortel.com) Received: from zrtps0kn.nortelnetworks.com (zrtps0kn.nortelnetworks.com [47.140.192.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAAB143D46; Wed, 19 Oct 2005 14:26:42 +0000 (GMT) (envelope-from atrens@nortel.com) Received: from zcarhxm2.corp.nortel.com (zcarhxm2.corp.nortel.com [47.129.230.99]) by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id j9JEQZA01308; Wed, 19 Oct 2005 10:26:36 -0400 (EDT) Received: from [10.0.5.2] ([47.128.22.25] RDNS failed) by zcarhxm2.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 19 Oct 2005 10:26:34 -0400 Message-ID: <43565782.8080706@nortel.com> Date: Wed, 19 Oct 2005 10:26:10 -0400 From: "Andrew Atrens" User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050926) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrew Thompson References: <43560B6A.4070505@mikulas.com> <20051019091559.GA45009@heff.fud.org.nz> In-Reply-To: <20051019091559.GA45009@heff.fud.org.nz> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 19 Oct 2005 14:26:34.0134 (UTC) FILETIME=[1B42FB60:01C5D4B9] X-Mailman-Approved-At: Thu, 20 Oct 2005 12:27:19 +0000 Cc: freebsd-current@freebsd.org, Jiri Mikulas Subject: Re: ath client bridge 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, 19 Oct 2005 14:26:43 -0000 Andrew Thompson wrote: > On Wed, Oct 19, 2005 at 11:01:30AM +0200, Jiri Mikulas wrote: > >>Hello >>I have problem to setup bridging box with ath in client mode and if_bridge >>When card is in AP mode, everything is ok, but if I want to run card in >>client mode, bridging is not working. >>Here are my testing steps: (it's quite long, so I prefer put URL there :) ) > > > Bridging on the client side of a wireless connection is not supported > and has to do with the 801.11 frame format. The problem is that the > client only registers its own MAC address with the AP, so the bridged > clients do not get a reply (as far as I understand). Yah, the 802.11 header only has room for three addresses. The AP uses them as - ssid src dest (in this case src is the *real* src of the packet hence the AP itself can bridge) The client uses - ssid src dest (in this case src *must* be the client mac, hence the client can't bridge packets from other macs) There is a four address version of the packet header, but as I recall the fourth address is used by TKIP. So it's a problem with 802.11 standard. I think that's why they came up with WDS. I think there's some support for WDS in MadWiFi, but not yet in the BSD stack(s). Another thing that you *could* do - that I'm actually working on for DragonFly, is to add support for bridging GIF interfaces. Or, if it was possible add support for directly bridging across IPsec - I think even transport mode support would suffice, as long as in either case the AP and client were endpoints for the IPsec connection. Andrew