On Fri, 2017-03-17 at 14:56 +0900, Masashi Honma wrote: > > 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. 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? 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*. johannes
