Yes, mpath set is only valid after peering. So you will have the MAC address then. ---- Chun-Yeow On Mon, May 26, 2014 at 5:37 PM, Henning Rogge <hrogge@xxxxxxxxx> wrote: > Hi, > > I think this would require to know the mac addresses of the remote > nodes... but maybe I will look into changing the timeout value. > > Henning Rogge > > On Mon, May 26, 2014 at 8:47 AM, Yeoh Chun-Yeow <yeohchunyeow@xxxxxxxxx> wrote: >> For disable HWMP, in additional to disable frame forwarding and set >> mesh TTL to 1, you can force specific mpath using "iw mesh0 mpath set >> <MACx> next_hop <MACx>". In this case, you will disable the path >> refresh. >> >> ---- >> Chun-Yeow >> >> On Sat, May 24, 2014 at 4:57 AM, Bob Copeland <me@xxxxxxxxxxxxxxx> wrote: >>> On Fri, May 23, 2014 at 12:52:57PM +0200, Henning Rogge wrote: >>>> Hi, >>>> >>>> I will have another look at the codebase next week, there was a lot of >>>> similar code for both tables that could be simplified without throwing >>>> them together. >>>> >>>> The feeling I get here is that four new nl80211 commands >>>> (set/get/del/dump mpp_paths) are the right way to export these values? >>> >>> That approach would be fine by me. Thanks for working on this! >>> >>> -- >>> 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
