On Mon, May 19, 2014 at 11:00:53AM +0200, Henning Rogge wrote: > Is there an easy way to stop HWMP in the 802.11s implementation? If I understand your use case, you want to basically remove the resolving part of mesh_nexthop_resolve()? I don't believe the current implementation has a way to turn that off. In principle, you can specify a vendor-specific path selection protocol when joining, but glancing at the existing code, we don't really do anything with that field except use it for peering fitness checks. If all you want to do is force the paths, you can do so with the NL80211_CMD_SET_MESH_PATH API; such paths would override any selected by HWMP. But you'd still generate PREQ/PREPs and get multihop communication in that case, it just wouldn't be subject to the airtime link metric. Perhaps we should skip resolve in case ifmsh->mesh_pp_id != 1 and assume paths are somehow set up out of band or something? -- Bob Copeland %% www.bobcopeland.com -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
