From: Masashi Honma <masashi.honma@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/2] mac80211: Drop new node with weak power
Date: Mon, 20 Mar 2017 15:39:02 +0900 [thread overview]
Message-ID: <c95cce88-d02f-8ef3-a848-0a8a3de6296b@gmail.com> (raw)
In-Reply-To: <1489753692.2544.9.camel@sipsolutions.net>
On 2017/03/17 21:28, Johannes Berg wrote:
> Hmm. If path selection isn't done by mac80211 in this case, wouldn't it
> be more appropriate to put this logic into the (userspace) component
> that does path selection?
Currently, userspace application(wpa_supplicant) does not have mesh
path selection functionality.
> IOW, I'm not convinced that outright not adding the *peer* is a good
> idea either way - it seems much better to me to not use the *path*.
We have already had the code to calculate mesh path metric with RSSI.
But we still needs this patch for a special case on SAE. Some hardware
can use hardware encryption for mesh SAE. Then the hardware has a
limitation of key registration. For example, some hardware could only
save keys for 8 stations. So we need to drop stations itself with weak
signal instead of the pathes to its.
Masashi Honma.
next prev parent reply other threads:[~2017-03-20 6:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 1:57 [PATCH 1/2] nl80211: Use signed function for a signed variable Masashi Honma
2017-03-16 1:57 ` [PATCH 2/2] mac80211: Drop new node with weak power Masashi Honma
2017-03-16 10:03 ` Johannes Berg
2017-03-17 5:56 ` Masashi Honma
2017-03-17 12:28 ` Johannes Berg
2017-03-20 6:39 ` Masashi Honma [this message]
2017-03-29 8:26 ` Johannes Berg
2017-03-16 9:55 ` [PATCH 1/2] nl80211: Use signed function for a signed variable Johannes Berg
2017-03-17 5:59 ` [PATCH v2] mac80211: Use rssi_threshold even though user_mpm=1 Masashi Honma
2017-03-26 20:53 ` Masashi Honma
2017-03-29 8:29 ` 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=c95cce88-d02f-8ef3-a848-0a8a3de6296b@gmail.com \
--to=masashi.honma@gmail.com \
--cc=johannes@sipsolutions.net \
--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 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).