Good job !
Interesting is that the average throughput fluctuates from run to run (iperf3) from 300 to 380-390 without me changing anything. This is huge variation. See the screenshots bellow.
Your RF spectrum around might be fluctuating. (The other radio's around). That 300-390 Mbps is not a bad number. The higher the PHY the higher impact the overhead has. On stable high PHY some steps must be taken to reduce the impact of the overhead. One is rising the basic rate on all radio's. (from 6Mbps to 18 Mbps or even 24 Mbps).
The wireless snooper at one point showed 250 lines on the 5500 frequency, 80% of them bellow 80db, this sounds crazy. I'm not sure how I could be picking up this. The only explanation is that I live on top floor in densely populated central area...but still...unless there's office building very close by (how close should that be?) that I'm not aware of I can't see how this could be happening.
Unfortunately that is your reality. If you allow "Receive errors" in Snooper, you will even see more! You use everything on 5500-5520-5540-5580 with your setting. Co-channel interference happens with every sender that is 6 dB above the noise floor. So you might even wait for someone sending at -96 dBm. Fortunately 802.11ac does a better job than 802.11n for wide channels, by using only some of the 4 channels if needed. (With speed variation ...)
Check your antenna pattern (sending=receiving). Even a 3 dBi low gain antenna has already some donut shape. (there is lower signal in the length axis of the antenna). This is an expliciete donut shape for higher gain antenna. If you have external antenna, set them all upright, not under an angle like in the commercial pictures.
5600 seems to have radar as the AP refuses to listen on it unless in superchannel mode. I guess in EU we don't have other free channels in the 5500+ range?
If you have radar signal detected this will be clearly noted in your log. (Only the AP does radar detect handling). For wifi visibility extend the log with (/system logging add topics=wireless action=memory). All channels above 5500 in EU (Etsi regulatory region) are still DFS channels. The weather channels (5600-5620-5640) take 10 full minutes before they activate after every change of the interface or wireless setting. 10 minutes is extremely long ... if you have to wait for it. The LOG again is your guidance. It will tell you "searching for radar" and "starting network" (not the exact wording ).
There is no need to assume you have radar, you can see it in the log. Actually there are also many "false radar detects".
interesting is also the iperf3 reports some retries — 100-700 for two-minute test. I was thinking that frame-keepalive can interfere with tcp's flow control but it does not look like this is the case right now.
Normally wifi does not drop any packet. It retries until disconnect. TCP congestion avoidance can play a big role in here. Depending on your client you can experiment with the algorithms. https://en.wikipedia.org/wiki/TCP_congestion_control
. MKT does not allow us to specify the algorithm, as Linux client does, and Windows 10 has changed to CUBIC I believe. MKT is not sending TCP data itself, tests should be with sending/receiving clients.
The state at the moment is much better than the starting one and to big degree thanks to the posts I read from you in different other threads. Still, I would've expected higher and more reliable throughput.
tested NV2 for a moment. Ping was tad slower but no jitter. Throughput was lower (yes, I know it's time division, etc). Right now AC is much better.
That's why I start with 802.11ac and only go to nv2 with poor CCQ.
cts to self does not seem to make notable difference. I guess I can leave it on.
I have to reread the 802.11ac survival guide. 802.11ac may be using RTS/CTS to handle separate channels in wide channels. https://www.oreilly.com/library/view/80 ... index.html
(free). See https://www.oreilly.com/library/view/80 ... /ch03.html
for RTS/CTS. The other chapters are interesting too.
here is my AP config. Station is identical, it seems important that the two match, esp. re the advanced tab values
Well I don't like the 6.48 as RouterOS version. Too many reported problems !!! Use the LT (Long Term).
You can add screenshots and photo's here in "Attachments" of a post , they can even be placed "in line".