Hi, Chaoxing Yes. You are correct. As pointed out, the following patch is intended to solve this:
http://lists.open80211s.org/pipermail/devel/2013-February/004149.html http://www.spinics.net/lists/linux-wireless/msg103642.html --- Chun-Yeow On Mon, Mar 11, 2013 at 9:46 PM, Chaoxing Lin <[email protected]> wrote: > I guess your mp is added to bridge since you mentioned "Ethernet" MAC. > I saw the same problem and solved it long ago(meaning, I can't remember exact > scenario to reproduce it). > > Below is the note when I fixed it. I hope it will help. > I believe the mesh_hwmp.c maintainer would know what's going on after reading > it. > > > "The problem is that code always looks up DA from mpath table. > Only when there is no entry in mpath table, it looks up DA from mpp table. > If neither table has an entry for DA, code adds an empty entry with DA in > mpath > table and starts path request with the hope that this entry will be filled > when > path reply packet comes back. In this case(DA is not a MP, it's Ethernet > MAC), there won't be path reply, which > results in a dead entry in mpath table. > > This dead entry prevent future communication because code won't look up DA > from > mpp table any more (there is an entry in mpath table, although it's dead). > > The fix for the bug part is to delete dead entry in mpath table when DA is > learned in mpp table. Now, valid entry can be found in mpp table and there is > no > need to do path request(meaning, no further dead entry later on)" > > _______________________________________________ Devel mailing list [email protected] http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
