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.
