From: Johannes Berg <johannes@sipsolutions.net>
To: "Nishikawa, Kenzoh" <Kenzoh.Nishikawa@jp.sony.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"devel@lists.open80211s.org" <devel@lists.open80211s.org>,
"Bob Copeland (me@bobcopeland.com)" <me@bobcopeland.com>,
"Thomas Pedersen (thomas@noack.us)" <thomas@noack.us>
Subject: Re: [PATCH v4] mac80211: keep sending peer candidate events while in listen state
Date: Fri, 12 Dec 2014 12:41:30 +0100 [thread overview]
Message-ID: <1418384490.2470.23.camel@sipsolutions.net> (raw)
In-Reply-To: <2EB4F5C65A3B8E4E92660930F4EF6B5B06C981@JPYOKXMS113.jp.sony.com>
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
next prev parent reply other threads:[~2014-12-12 11:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 11:24 [PATCH v4] mac80211: keep sending peer candidate events while in listen state Nishikawa, Kenzoh
2014-12-12 11:41 ` Johannes Berg [this message]
2014-12-12 16:47 ` Bob Copeland (me@bobcopeland.com)
2014-12-15 12:39 ` Johannes Berg
2014-12-14 2:18 ` Nishikawa, Kenzoh
2014-12-15 12:40 ` 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=1418384490.2470.23.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Kenzoh.Nishikawa@jp.sony.com \
--cc=devel@lists.open80211s.org \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.com \
--cc=thomas@noack.us \
/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;
as well as URLs for NNTP newsgroup(s).