From owner-freebsd-wireless@FreeBSD.ORG  Thu Apr  3 07:05:58 2014
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id CBAA5207;
 Thu,  3 Apr 2014 07:05:58 +0000 (UTC)
Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "theravensnest.org", Issuer "theravensnest.org" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 928F81C5;
 Thu,  3 Apr 2014 07:05:58 +0000 (UTC)
Received: from [192.168.0.100] (cpc14-cmbg15-2-0-cust307.5-4.cable.virginm.net
 [82.26.1.52]) (authenticated bits=0)
 by theravensnest.org (8.14.7/8.14.7) with ESMTP id s3375rN3062400
 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
 Thu, 3 Apr 2014 07:05:56 GMT
 (envelope-from theraven@theravensnest.org)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: WDS with a FreeBSD access point
From: David Chisnall <theraven@theravensnest.org>
In-Reply-To: <CAJ-Vmo=P50h6q1b0+TgFD+h+hPfG7UiNd0vpPmO+5k374YOPSA@mail.gmail.com>
Date: Thu, 3 Apr 2014 08:05:48 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <DDD043B9-1002-4E80-B687-11B8718A875C@theravensnest.org>
References: <E8950480-2829-4F4E-A48C-B080AE75BC97@FreeBSD.org>
 <533BD60D.9050701@weboutsourcing.cz>
 <CAJ-Vmokx1Ce7yQ=VGeqT4FnSgtG3JZMJs2bvs4vdbaYYDyZ0kw@mail.gmail.com>
 <533CD386.80906@weboutsourcing.cz>
 <E7DD4EF0-1A2F-4237-8995-F1D0AC1ABA87@theravensnest.org>
 <CAJ-Vmo=P50h6q1b0+TgFD+h+hPfG7UiNd0vpPmO+5k374YOPSA@mail.gmail.com>
To: Adrian Chadd <adrian@freebsd.org>
X-Mailer: Apple Mail (2.1874)
Cc: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org>
X-BeenThere: freebsd-wireless@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discussions of 802.11 stack,
 tools device driver development." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless/>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 07:05:58 -0000

On 3 Apr 2014, at 07:57, Adrian Chadd <adrian@freebsd.org> wrote:

> Are both freebsd APs?

Nope, the main station is a FreeBSD box, the remote is a cheap commodity =
AP (there are a lot that claim to do WDS for under =A310 - I have two =
different models for testing).

> It looks reasonably straightfoward. I really should just give this a
> go at home on an extender AP and test the hell out of it.

Let me know how it goes...

> So, for wifi traffic, you absolutely want the wifi VAPs in a bridge
> group as the traffic between stations and APs is all layer-2.

I think I'm missing something here.  The script created a bridge between =
the wireless and wired interfaces.  I don't think I want that, so what =
do I want the bridge between?

> There's
> no routing involved. If you want to route between the bridge0
> interface and the rest of the system then please do so but do put the
> STA and AP VAPs into the same bridge group.

'STA and AP VAPs'?  Can we go back to assuming that I don't know =
anything please?

David