Sat Jul 20, 2019 4:22 pm
I also want to share my experience with mikrotiks ac hardware in p2p links and maybe someone has an explanation for my strange observations.
I can only reach 190Mbit/s with nstream on ac hardware.
I have a PtP link with a DISC Lite5 ac (AP) and a LHG XL 5 ac (client). The link is about 600m long. The conditions are far from optimal because at least two roofs occlude the first fresnel zone and there is, as always no clean 80Mhz Chanel. However with 802.11 I can reach 300Mbit/s of TCP throughput in both directions. With nv2 I can reach nearly 300Mbit/s from the AP to the client but only 160Mbit/s from the client to the AP, which is the direction where most of the traffic will flow. Furthermore the throughput with nv2 is very unstable. Therefore, nv2 is not an option.
While 802.11 has the best TCP throughput and the throughput is much more stable then with nv2, I have another KO problem with it. Every 10 to 100 second the links stops forwarding traffic for 3 to 8 seconds. During this 0 throughput events the client does not disconnect (I can see it in the wireless registration table of the AP), nor the Tx/Rx does change, at least not more then when the link is fully operational (between 520 and 650Mbit/s).
I'm relative sure it is not a problem of the hardware because, I can reproduce this speed limitations of nstream and also the 0 traffic flow events when using 802.11 with two SXT-HG5ac in a comparable setup. Not the exact same location, but nearly the same distance and also an roof that hits first fresnel zone.
Can somebody explain why the links stops forwarding traffic every 10 to 100 seconds for some seconds if 802.11 is used?
It would be really great if mikrotik could improve the maximal throughput of nstream on ac hardware, because it is the only protocol that works reliable for me.
p.s.: All stated throughputs are measured with iperf3.