From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from s3.sipsolutions.net ([5.9.151.49]:32937 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966206AbaLLLle (ORCPT ); Fri, 12 Dec 2014 06:41:34 -0500 Message-ID: <1418384490.2470.23.camel@sipsolutions.net> (sfid-20141212_124140_829997_ACC1777F) Subject: Re: [PATCH v4] mac80211: keep sending peer candidate events while in listen state From: Johannes Berg To: "Nishikawa, Kenzoh" Cc: "linux-wireless@vger.kernel.org" , "devel@lists.open80211s.org" , "Bob Copeland (me@bobcopeland.com)" , "Thomas Pedersen (thomas@noack.us)" Date: Fri, 12 Dec 2014 12:41:30 +0100 In-Reply-To: <2EB4F5C65A3B8E4E92660930F4EF6B5B06C981@JPYOKXMS113.jp.sony.com> References: <2EB4F5C65A3B8E4E92660930F4EF6B5B06C981@JPYOKXMS113.jp.sony.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Fri, 2014-11-21 at 11:24 +0000, Nishikawa, Kenzoh wrote: > Instead of sending peer candidate events just once, send them > as long as the peer remains in the LISTEN state in the peering > state machine, when userspace is implementing the peering manager. > Userspace may silence the events from a peer by progressing > the state machine or by setting the link state to BLOCKED. > > Fixes the problem that a mesh peering process won't be fired > again after the previous first peering trial fails due to > like air propagation error if the peering is managed by > user space such as wpa_supplicant. > > This patch works with another patch for wpa_supplicant described > here which fires a peering process again triggered by the notice > from kernel. > http://lists.shmoo.com/pipermail/hostap/2014-November/031235.html Can any of the mesh folks comment on this? johannes