Return-path: Received: from mail-ig0-f175.google.com ([209.85.213.175]:36070 "EHLO mail-ig0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752918AbbGBLuF (ORCPT ); Thu, 2 Jul 2015 07:50:05 -0400 Received: by igrv9 with SMTP id v9so94480347igr.1 for ; Thu, 02 Jul 2015 04:50:05 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <1435837125.2285.7.camel@sipsolutions.net> References: <1435082418.2777.11.camel@ipeer-box> <1435822032.2285.2.camel@sipsolutions.net> <1435837125.2285.7.camel@sipsolutions.net> From: Krishna Chaitanya Date: Thu, 2 Jul 2015 17:19:45 +0530 Message-ID: (sfid-20150702_135010_652884_CA7183BB) Subject: Re: AP + P2P_GO multichan tests with intel7260 as a P2P_CLIENT - direct probe issue To: Johannes Berg Cc: Janusz Dziedzic , "Peer, Ilan" , "linux-wireless@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Thu, Jul 2, 2015 at 5:08 PM, Johannes Berg wrote: > 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?? If retry bit is not set, then it works, but in a noisy channel 2.4GHz we are seeing high retries causing direct probes to fail 90% of the time. The AP in case is Marvel AP RD88W8787 (WFA Testbed).