Return-path: Received: from s3.sipsolutions.net ([5.9.151.49]:46521 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751524AbbGBLit (ORCPT ); Thu, 2 Jul 2015 07:38:49 -0400 Message-ID: <1435837125.2285.7.camel@sipsolutions.net> (sfid-20150702_133852_283618_740392F1) Subject: Re: AP + P2P_GO multichan tests with intel7260 as a P2P_CLIENT - direct probe issue From: Johannes Berg To: Krishna Chaitanya Cc: Janusz Dziedzic , "Peer, Ilan" , "linux-wireless@vger.kernel.org" Date: Thu, 02 Jul 2015 13:38:45 +0200 In-Reply-To: (sfid-20150702_110308_268288_A41D6D36) References: <1435082418.2777.11.camel@ipeer-box> <1435822032.2285.2.camel@sipsolutions.net> (sfid-20150702_110308_268288_A41D6D36) Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: 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