From: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
To: "Malinen, Jouni" <jouni@qca.qualcomm.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
"Peer, Ilan" <ilan.peer@intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Rodriguez, Luis" <rodrigue@qca.qualcomm.com>,
"John W . Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH v8] cfg80211: P2P find phase offload
Date: Tue, 4 Jun 2013 19:47:20 +0300 [thread overview]
Message-ID: <2442077.aHiBPHBLmq@lx-vladimir> (raw)
In-Reply-To: <8887AA04B7EC49479420AE48C5F94A930EF6C0AA@NASANEXD02D.na.qualcomm.com>
On Tuesday, June 04, 2013 05:35:30 PM Malinen, Jouni wrote:
>
> On 6/4/13 5:29 PM, "Johannes Berg" <johannes@sipsolutions.net> wrote:
>
> >On Tue, 2013-06-04 at 17:03 +0300, Vladimir Kondratiev wrote:
> >
> >> And, probes must be reported to the host in all cases, for wpa_s to
> >>have peer list.
> >> Need to add comment describing this.
> >
> >I don't think that's necessarily true. wpa_s will pre-build a list, but
> >note that it doesn't make those peers as discovered and you can't really
> >do anything with them. As such, I would argue that reporting probe
> >requests ("probes") would be harmful and counter to one potential goal
> >of this patch (powersaving.)
>
> In general, I'd agree. However, I would like to get information of any
> peer device being in active PBC mode. This would require either getting
> those Probe Request frames or alternatively that being tracked in
> kernel/driver/firmware with some access for wpa_supplicant to fetch
> information of all STAs (list of MAC Address + UUID) that have indicated
> active PBC mode within last 120 seconds.
>
> - Jouni
I am a bit confused. I supposed that if devices A and B (not in a group yet)
try to discover each other, it works like the following
A ---- probe-req ---> B (now B knows A)
A <--- probe-resp ---- B (now A knows B)
But if device is discovered by probe-resp only, it mean this should be
A ---- probe-req ---> B
A <--- probe-resp ---- B (now A knows B)
A <--- probe-req ---- B
A ---- probe-resp ---> B (now B knows A)
What is the case?
Thanks, Vladimir
next prev parent reply other threads:[~2013-06-04 16:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 6:44 [PATCH v8] P2P find phase offload Vladimir Kondratiev
2013-06-04 6:44 ` [PATCH v8] cfg80211: " Vladimir Kondratiev
2013-06-04 10:07 ` Peer, Ilan
2013-06-04 11:24 ` Vladimir Kondratiev
2013-06-04 12:07 ` Johannes Berg
2013-06-04 14:03 ` Vladimir Kondratiev
2013-06-04 14:29 ` Johannes Berg
2013-06-04 14:35 ` Malinen, Jouni
2013-06-04 16:47 ` Vladimir Kondratiev [this message]
2013-06-04 18:30 ` Jouni Malinen
2013-06-05 7:10 ` Vladimir Kondratiev
2013-06-05 7:53 ` Johannes Berg
2013-06-05 13:30 ` Vladimir Kondratiev
2013-06-11 12:12 ` Johannes Berg
2013-06-05 7:46 ` Johannes Berg
2013-06-05 8:10 ` Arend van Spriel
2013-06-05 8:18 ` Johannes Berg
2013-06-05 8:38 ` Arend van Spriel
2013-06-05 16:26 ` Vladimir Kondratiev
2013-06-05 8:12 ` Jouni Malinen
2013-06-04 12:10 ` Peer, Ilan
2013-06-04 10:43 ` Johannes Berg
2013-06-04 6:51 ` [PATCH v8] " Johannes Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2442077.aHiBPHBLmq@lx-vladimir \
--to=qca_vkondrat@qca.qualcomm.com \
--cc=ilan.peer@intel.com \
--cc=johannes@sipsolutions.net \
--cc=jouni@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rodrigue@qca.qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox