Hi Yeoh, Could you check if the duplicates you observe, in addition of having the same SA and sequence number, also have the same RA? If not, the RA check would be a better way to kill dupes rather than the cache.
Thanks! Javier On Thu, Mar 14, 2013 at 7:33 PM, Yeoh Chun-Yeow <[email protected]> wrote: >> I would only recommend introducing the recently uncast cache Yeoh is >> proposing if we understand the root cause why duplicate unicast frames >> occur. > After applying the unicast duplicate patch (plus adding a counter on > it for duplicate unicast frame) for all the 11 nodes and also the > patch from Thomas, I try to ping between two farthest nodes (perhaps > 2-hops or 3-hops away) for 1 hours with interval 0.01s. In my case, > node 1 to node 11. > > Since the checking of Thomas's patch is done first, so there should > also be duplicate unicast frame with the same sequence number if in > case any. > > I have observed the following number of duplicate unicast frame (with > same sequence number and source address) in my setup: > Node 1: 0 > Node 2: 0 > Node 3: 597 > Node 4: 0 > Node 5: 1416 > Node 6: 411 > Node 7: 1055 > Node 8: 205 > Node 9: 444 > Node 10: 2 > Node 11: 0 > > ---- > Chun-Yeow > _______________________________________________ > Devel mailing list > [email protected] > http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel -- Javier Cardona cozybit Inc. http://www.cozybit.com _______________________________________________ Devel mailing list [email protected] http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
