On 2017/03/16 19:03, Johannes Berg wrote:
I'm not really sure this is the right solution?
It seems to me that it should be a function of the path selection to
take this into account, not prohibiting the longer path entirely?
Right. To calculate metric with RSSI level is better solution than
this solution.
It seems that this is really what the meshcfg.rssi_threshold was
intended for, and the plink code *does* take it into account. Can you
explain where that's breaking down?
Indeed meshcfg.rssi_threshold is already referred by some codes. But
when booting mesh node with user_mpm=1, the codes is not called.
So we need to add another code.
I will update commit log because this patch just enables
meshcfg.rssi_threshold with user_mpm=1.
Masashi Honma.
