From: Johannes Berg <johannes@sipsolutions.net>
To: Krishna Chaitanya <chaitanya.mgit@gmail.com>
Cc: Janusz Dziedzic <janusz.dziedzic@tieto.com>,
"Peer, Ilan" <ilan.peer@intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: AP + P2P_GO multichan tests with intel7260 as a P2P_CLIENT - direct probe issue
Date: Thu, 02 Jul 2015 13:38:45 +0200 [thread overview]
Message-ID: <1435837125.2285.7.camel@sipsolutions.net> (raw)
In-Reply-To: <CABPxzYLVDUsFu3WwCFzYjE-sZtARiDSM6iGRu6RSFxeJ7k=rOw@mail.gmail.com> (sfid-20150702_110308_268288_A41D6D36)
On Thu, 2015-07-02 at 14:32 +0530, Krishna Chaitanya wrote:
>
> We have also found another issue with direct probe.
> Some of the AP's are not setting sequence number in the probe
> responses
> so in case of a retry they are dropped as duplicate by rx_h_check
> causing direct probe to fail.
I don't quite see how that can be an issue, since the RETRY bit
shouldn't be set??
johannes
next prev parent reply other threads:[~2015-07-02 11:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 8:50 AP + P2P_GO multichan tests with intel7260 as a P2P_CLIENT - direct probe issue Janusz Dziedzic
2015-06-23 11:11 ` Peer, Ilan
2015-06-23 11:29 ` Krishna Chaitanya
2015-06-23 11:55 ` Peer, Ilan
2015-06-23 12:04 ` Krishna Chaitanya
2015-06-23 18:00 ` Peer, Ilan
2015-06-24 12:20 ` Peer, Ilan
2015-06-27 21:49 ` Janusz Dziedzic
2015-06-27 22:03 ` Janusz Dziedzic
2015-06-28 8:36 ` Peer, Ilan
2015-07-02 7:27 ` Johannes Berg
2015-07-02 9:02 ` Krishna Chaitanya
2015-07-02 11:38 ` Johannes Berg [this message]
2015-07-02 11:49 ` Krishna Chaitanya
2015-07-02 9:44 ` Janusz Dziedzic
2015-07-02 11:39 ` Johannes Berg
2015-07-02 11:50 ` Krishna Chaitanya
2015-07-02 12:01 ` Johannes Berg
2015-07-02 12:13 ` Krishna Chaitanya
2015-07-02 12:37 ` 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=1435837125.2285.7.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=chaitanya.mgit@gmail.com \
--cc=ilan.peer@intel.com \
--cc=janusz.dziedzic@tieto.com \
--cc=linux-wireless@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.