SXT AC ,p2p link on 2km and latency is unstabile ,

hi dear mikrotik team ,
i have link with sxt ac on 2 km , signal is ~55 - air rate ~ 585MBps 80mhz , real tcp throughput is ~120-180mbps and latency is very unstable ( start’s from 0 ms and big is 80 ) .
first i set on wireless protocol : nv2 but not working well , next set nstreme and same situation , on this time i use 802.11 and more stabile but with unstability latency

i upgrade from 6.16to 6.18 and 6.19 os and same result.
c1.PNG

when tcp usage more than 100mbps
c2.PNG

yes 802.11ac is unusable under mikrotik.
try to switch to 802.11a/n only mode.

Wrong
ping.jpg

what the wrong ?
c5.PNG

I was answering to the post above mine, like is normal. If I was answering you, I had to quote you, in a perfect world.

You posted results of a bandwidth U can achieve with better ping with nstreme in a/n mode.
A/c is unstable as for now and I’ve put easy solution for Misha :slight_smile:
in a ideal world mikrotik should work no worse than other maker gears.
but it’s not.
:neutral_face:

My picture proved you are wrong, radios are connected with 802.11ac and nv2.
I had reply only at your post.
So what are you talking about?
Are you misleading people or what?

No you are reading it incorrectly.

He said AC is UNSTABLE currently still in routeros, so its best to use your SXT AC in AN mode, instead of AC mode, so you get more stable results.

Since when UNSTABLE is writen unusable? When did you learn to read? My picture shows is not unstable or unusable anyway.
BTW is good to stay ontopic. Any frustration can be resolved by hiting a wall with your head.

now i set a/n mode with nstreme and max throughput is ~120mbps in tcp mode and ping better than previos situation , also on a/n , only-n and only-a/c i attempts custom channel with 30 mhz bandwidth and its say that not supported :confused: ,

hi all ,

now , i change sxt’s on netbox 5 with dish 30dbi anten, results is very well for this moment , tcp traffic archive ~ 300-340mbps and udp traffic ~ 400-470 mbps

config set : ap-bridge → station-bridge , distance set manually ( 2km ) , hardware retries 10 , wireles protocol nv2 with auto timing ,and band only-A/C


well be good if implement custom channel widths on C standart and MCS if be checkable manually
Captureudp.PNG
Capturetcp.PNG