Date: Wed, 23 Apr 2008 21:15:21 +0400 From: Lev Serebryakov <lev@FreeBSD.org> To: Sam Leffler <sam@FreeBSD.org> Cc: Randy Bush <randy@psg.com>, freebsd-current@FreeBSD.org, lev@FreeBSD.org, Brooks Davis <brooks@FreeBSD.org> Subject: Re[2]: HEADSUP: 802.11 vap support merged Message-ID: <29742224.20080423211521@serebryakov.spb.ru> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <lev@FreeBSD.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?29742224.20080423211521>