Hi, Thomas This check is redundant. It sounds like dot11MeshForwarding only >> prevents forwarding of PREQ frames (which you caught above), thereby >> preventing the creation of multihop mpaths with this node as the >> destination. >> >> > To be safe, this is a possibility that a user alters his mpath table to > reach a destination via a specific node, such as "iw mesh0 mpath set <MAC1> > next_hop <MAC2>". So if MAC2 is set to not forwarding and this checking is > there, it will ensure that the data is not forwarded even force by a > particular mesh node. I have tested this scenario thus putting this > checking here. Please comment. > > I made the mistake. After redoing the testing, it seems redundant. So I will resubmit the patch by eliminating this line.
Thanks Regards, Chun-Yeow
_______________________________________________ Devel mailing list [email protected] http://open80211s.com/mailman/listinfo/devel
