Dear Thomas, I am able to find the embedded boards with Gigabit Ethernet, so the throughput measurements are as followed:
Non Secured Mesh (HT40+) # iperf -s -i 1 ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 85.3 KByte (default) ------------------------------------------------------------ [ ID] Interval Transfer Bandwidth [SUM] 0.0-10.5 sec 189 MBytes 151 Mbits/sec Secured Mesh (HT40+) # iperf -s -i 1 ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 85.3 KByte (default) ------------------------------------------------------------ [ ID] Interval Transfer Bandwidth [SUM] 0.0-10.9 sec 23.7 MBytes 18.2 Mbits/sec So more or less the throughput for HT20 and HT40+ for secured mesh is the same, not much improvement. Perhaps, due to processing overhead for using the software crypto in the setup (nohwcrypt=1). What's the throughput that you able to get in your site? Any network cards that is able to support hardware crypto acceleration in Mesh setup? Please advice. Thanks Regards, Chun-Yeow On Mon, Nov 14, 2011 at 10:05 AM, Yeoh Chun-Yeow <[email protected]>wrote: > Hi, Thomas > > Managed to get the secured mesh up after applying the linked patch. I have > managed to test the HT20 mode for secured mesh and non-secured mesh due to > my embedded platform only supports Fast Ethernet. Here are the results: > > Non Secured Mesh (HT20) > # iperf -s -i 1 > ------------------------------------------------------------ > Server listening on TCP port 5001 > TCP window size: 85.3 KByte (default) > ------------------------------------------------------------ > [ ID] Interval Transfer Bandwidth > [SUM] 0.0-10.0 sec 72.0 MBytes 60.1 Mbits/sec > > Secured Mesh (HT20) > # iperf -s -i 1 > ------------------------------------------------------------ > Server listening on TCP port 5001 > TCP window size: 85.3 KByte (default) > ------------------------------------------------------------ > [ ID] Interval Transfer Bandwidth > [SUM] 0.0-10.1 sec 15.6 MBytes 13.0 Mbits/sec > > A bit disappointed that the throughput is drop quite significantly. > Confirm that the aggregation is working: > > > Rx A-MPDU request on tid 0 result 0 > Open BA session requested for 0a:0b:6b:7d:e3:b9 tid 0 > > activated addBA response timer on tid 0 > switched off addBA timer for tid 0 > Aggregation is on for tid 0 > > Regards, > Chun-Yeow > > >
_______________________________________________ Devel mailing list [email protected] http://open80211s.com/mailman/listinfo/devel
