From owner-freebsd-current@FreeBSD.ORG Wed Apr 23 17:15:05 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 7B6CC106564A; Wed, 23 Apr 2008 17:15:05 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from ftp.translate.ru (ftp.translate.ru [195.131.4.140]) by mx1.freebsd.org (Postfix) with ESMTP id 1D9808FC15; Wed, 23 Apr 2008 17:15:05 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from desktop.home.serebryakov.spb.ru (unknown [89.163.10.141]) (Authenticated sender: lev@serebryakov.spb.ru) by ftp.translate.ru (Postfix) with ESMTPA id 534BE13DF62; Wed, 23 Apr 2008 21:15:04 +0400 (MSD) Date: Wed, 23 Apr 2008 21:15:21 +0400 From: Lev Serebryakov X-Mailer: The Bat! (v3.99.3) Professional Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <29742224.20080423211521@serebryakov.spb.ru> To: Sam Leffler In-Reply-To: <480F6138.7000803@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> <480F6138.7000803@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Randy Bush , freebsd-current@FreeBSD.org, lev@FreeBSD.org, Brooks Davis Subject: Re[2]: HEADSUP: 802.11 vap support merged X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org 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 17:15:05 -0000 Hello, Sam. You wrote 23 ?????? 2008 ?., 20:18:00: >>> 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 I understand this. And, IMHO, it is exact reason to not use "vap" as part of RC variables :) > (mesh support eventually). The terminology is unfortunately tied to the > original motivation. Maybe, terminology in scripts can be more generic and neutral? `wlan'? -- // Black Lion AKA Lev Serebryakov