From owner-freebsd-wireless@FreeBSD.ORG  Thu Apr  3 07:36:36 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 AB05865C;
 Thu,  3 Apr 2014 07:36:36 +0000 (UTC)
Received: from mx.weboutsourcing.cz (mx.weboutsourcing.cz [109.205.73.92])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 27F6F611;
 Thu,  3 Apr 2014 07:36:35 +0000 (UTC)
Received: from [192.168.46.157] ([193.86.201.140]) (authenticated bits=0)
 by mx.weboutsourcing.cz (8.14.4/8.14.4) with ESMTP id s337aXVl098448;
 Thu, 3 Apr 2014 09:36:33 +0200 (CEST)
 (envelope-from knezour@weboutsourcing.cz)
Message-ID: <533D0F7B.1000602@weboutsourcing.cz>
Date: Thu, 03 Apr 2014 09:36:27 +0200
From: Ondra Knezour <knezour@weboutsourcing.cz>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: David Chisnall <theraven@theravensnest.org>
Subject: Re: WDS with a FreeBSD access point
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>
 <DDD043B9-1002-4E80-B687-11B8718A875C@theravensnest.org>
 <533D0C02.9010303@weboutsourcing.cz>
 <B76A5FF7-EB35-4A8E-96C9-8F6903C420B0@theravensnest.org>
In-Reply-To: <B76A5FF7-EB35-4A8E-96C9-8F6903C420B0@theravensnest.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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:36:36 -0000

Dne 3.4.2014 9:23, David Chisnall napsal(a):
> On 3 Apr 2014, at 08:21, Ondra Knezour <knezour@weboutsourcing.cz>
> wrote:
> 
>> Dne 3.4.2014 9:05, David Chisnall napsal(a):
>>> 'STA and AP VAPs'?  Can we go back to assuming that I don't know
>>> anything please?
>> 
>> STA - station, basically a client connecting to the access point AP
>> - access point VAP - virtual AP, on one hardware device can be
>> multiple virtual APs/networks running
> 
> My confusion is from the fact that I'm not sure why I have a VAP - I
> was assuming my configuration would have a single wlan device that
> would talk to stations and WDS remotes.  Is this not the case?

As I can recall (it is long time ago I was experimenting with the WiFi
on little larger scale), you always create at least one VAP, the
ifconfig xxx create wlandev yyy does just that - creates one virtual
device xxx on the top of the hw device yyy.

So if you want for example several diferent SSIDs, you will create
multiple VAPs for them and bridge them together. I am unable to try it
in near future to explain it better but hopefully you got the point.
-- 
Ondra Knezour