On Wed, Dec 16, 2015 at 04:46:19PM +0100, Gregor Best wrote: > I have done some speed testing, but with inconclusive results. I used a > Macbook Pro with OS X as the other side, testing was done with iperf, > both machines connected to the same WiFi: > > $ iperf -i 2 -c 192.168.178.54 > ------------------------------------------------------------ > Client connecting to 192.168.178.54, TCP port 5001 > TCP window size: 17.0 KByte (default) > ------------------------------------------------------------ > [ 3] local 192.168.178.49 port 30131 connected with 192.168.178.54 port 5001 > [ ID] Interval Transfer Bandwidth > [ 3] 0.0- 2.0 sec 768 KBytes 3.15 Mbits/sec > [ 3] 2.0- 4.0 sec 640 KBytes 2.62 Mbits/sec > [ 3] 4.0- 6.0 sec 640 KBytes 2.62 Mbits/sec > [ 3] 6.0- 8.0 sec 512 KBytes 2.10 Mbits/sec > [ 3] 8.0-10.0 sec 640 KBytes 2.62 Mbits/sec > [ 3] 0.0-10.3 sec 3.25 MBytes 2.64 Mbits/sec > > I assume the low bandwidth is due to the two thick walls separating my > laptops and the access point. Everything else seems to be fine though. > I'll retry the speed measurement in a few days when I'm home for > christmas.
Traffic bursts lasting less than 10s are probably too short to trigger AMRR into raising the data rate all the way up. The initial rate is the lowest one. The bandwidth values look about right to me, though, at least for 2Ghz (assuming your AP is not alone somewhere on a remote island). On 5Ghz you might see more, depending on whether the AP sends aggregated frames for not. Run 'ifconfig iwn0 debug' and look for lines in dmesg saying 'received action...' -- these frames are ADDBA and DELBA requests used to negotiate use of A-MPDUs.
