Date: Wed, 23 Apr 2008 09:18:00 -0700 From: Sam Leffler <sam@freebsd.org> To: lev@freebsd.org Cc: Randy Bush <randy@psg.com>, Brooks Davis <brooks@freebsd.org>, freebsd-current@freebsd.org Subject: Re: HEADSUP: 802.11 vap support merged Message-ID: <480F6138.7000803@freebsd.org> In-Reply-To: <11410077632.20080423195800@serebryakov.spb.ru> References: <480D6667.4020509@errno.com> <20080422200616.GA44541@tirith.brixandersen.dk> <480E79F9.40303@freebsd.org> <480F358A.2000009@psg.com> <20080423142628.GA44288@lor.one-eyed-alien.net> <480F4C56.7070009@psg.com> <11410077632.20080423195800@serebryakov.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Lev Serebryakov wrote:
> Hello, Randy.
> You wrote 23 ?????? 2008 ?., 18:48:54:
>
>
>> the difference between a wlan and a vap is subtle.
>>
> I don't thinks, that difference between client and server is subtile
> :) wlan is AP OR client, and VAP is AP only. And many comuters will be
> configured as clients, with wpa_supplicant, not hostapd :)
>
>
A "vap" is just an ifnet cloned from an 802.11 device. These have a
fixed operatin mode that can be ap, ibss, sta, monitor, ahdemo, whatever
(mesh support eventually). The terminology is unfortunately tied to the
original motivation.
Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?480F6138.7000803>