From owner-freebsd-wireless@FreeBSD.ORG  Sun Jun 30 20:34:19 2013
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])
 by hub.freebsd.org (Postfix) with ESMTP id 3A34FE5;
 Sun, 30 Jun 2013 20:34:19 +0000 (UTC) (envelope-from lev@FreeBSD.org)
Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru
 [IPv6:2a01:4f8:131:60a2::2])
 by mx1.freebsd.org (Postfix) with ESMTP id F3E211B19;
 Sun, 30 Jun 2013 20:34:18 +0000 (UTC)
Received: from lion.home.serebryakov.spb.ru (unknown
 [IPv6:2001:470:923f:1:4576:f46b:6d13:91c5])
 (Authenticated sender: lev@serebryakov.spb.ru)
 by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id C12594AC1C;
 Mon,  1 Jul 2013 00:34:17 +0400 (MSK)
Date: Mon, 1 Jul 2013 00:34:05 +0400
From: Lev Serebryakov <lev@FreeBSD.org>
X-Priority: 3 (Normal)
Message-ID: <657034146.20130701003405@serebryakov.spb.ru>
To: Adrian Chadd <adrian@freebsd.org>
Subject: Re: CFT: wpa_supplicant/hostapd import patch
In-Reply-To: <CAJ-Vmonwyc_YTOudFTFGutPEWwk+4BqA_e-NxAJ6QnMKeQefUw@mail.gmail.com>
References: <7671255B-5582-428A-8ADC-3DF7AA32C772@FreeBSD.org>
 <8819701.20130630194938@serebryakov.spb.ru>
 <A3A05313-D783-4633-BD60-9E5CA1B7F95B@FreeBSD.org>
 <EF43F13C-9803-47F2-8A2A-FCBCC9BBED4F@FreeBSD.org>
 <1415556931.20130701000811@serebryakov.spb.ru>
 <DCDC6F3A-03AF-4DCB-A66C-BD9DC832B12D@FreeBSD.org>
 <638557210.20130701001136@serebryakov.spb.ru>
 <FD107753-1E4D-43AC-B8E0-06D33A10D196@FreeBSD.org>
 <1342388755.20130701001505@serebryakov.spb.ru>
 <B1B0EA44-1D91-4DE8-AC40-A22176496DD8@FreeBSD.org>
 <CAJ-Vmonwyc_YTOudFTFGutPEWwk+4BqA_e-NxAJ6QnMKeQefUw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org>
X-BeenThere: freebsd-wireless@freebsd.org
X-Mailman-Version: 2.1.14
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: Sun, 30 Jun 2013 20:34:19 -0000

Hello, Adrian.
You wrote 1 =D0=B8=D1=8E=D0=BB=D1=8F 2013 =D0=B3., 0:25:23:

AC> Basic p2p isn't that hard - we'd just create another vap (call it a
AC> p2p mode vap) and have it implement the relevant semantics for p2p
AC> (discovery, announcement, session master/slave handling, etc.) After
AC> that I believe it looks like a normal station mode connection.
  Do I understand right, here you describe P in P2P?

AC> I _think_ that the net80211 / driver side of things is pretty simple.
AC> But I could be very wrong.

AC> However, the p2p off-channel stuff requires significant stack and
AC> driver work. I'm still sketching out what that's going to look like.
  And off-channel mode is mode, when here is (true) AP, which coordinates 2
clients to send traffic directly, without AP routing?

--=20
// Black Lion AKA Lev Serebryakov <lev@FreeBSD.org>