From owner-freebsd-current@FreeBSD.ORG Wed Apr 23 16:18:01 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C54021065677; Wed, 23 Apr 2008 16:18:01 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 8601A8FC26; Wed, 23 Apr 2008 16:18:01 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m3NGI0r5095691 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Apr 2008 09:18:01 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <480F6138.7000803@freebsd.org> Date: Wed, 23 Apr 2008 09:18:00 -0700 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.9 (X11/20071125) MIME-Version: 1.0 To: lev@freebsd.org 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> In-Reply-To: <11410077632.20080423195800@serebryakov.spb.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-Rhyolite-Metrics: ebb.errno.com; whitelist Cc: Randy Bush , Brooks Davis , freebsd-current@freebsd.org Subject: Re: HEADSUP: 802.11 vap support merged 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, 23 Apr 2008 16:18:01 -0000 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