ste so why don’t You use nstreme ?
i’ve got many main links on x86 with nstreme and it’s much more capable than titanium with the same antennas.
high jitter on mikrotik nv2 is kind of neverending story…
Normis: I’ve got 25% worse results with nstreme as with 80211.ac but with better ping. so
802.11 ac - up to 240 mbps (air data rate 520mbps)
nstreme - up to 180mbps air 520…
there is plenty to do so…
and once again Could You consider making it possible to force MCS lower than 7 on AC ?
What about disconnections in nstreme and ac. Is it stable ?
Because I have links with 100/100 ccq on “n” and they disconnect quite frequently with nstreme.
This problem is seen by a lot of people and nobody has a real solution until now. To reproduce it just put nv2 links in row and you will see that tcp speed decreases while udp speed stays up at the speed of the slowest link involved. This was not the case with nstreme (But with nstreme we’ve stability problems since 6.x releases).
I guess it has to do with how nv2 queues/aggregates packets. But this is just guesswork.
So while tuning nv2 for .ac please dont look only into a single link. Just put 3 links in a row (SXT AC are cheap you know )
and run a single tcp stream test end to end and see how much it differs from UDP speeds.
nstreme does not work well for us since 6.x. May be your x86s higher cpu power is the difference. We use 411AH, 433AH.
With SXT AC nstreme was way slower than 802.11 and nv2. May be nstreme needs more cpu cycles to operate and run into problem when the cpu cant keep up with the traffic.
router os 6.7 x86, dbii-fn50pro ar9220 ----nstreme ---- rb493G ros 6.7 link around 11km both places significantly crowded with 5ghz gears.
43days of link uptime thruput up to 150mbps real traffic and suppose 43days ago we had some serious power shortage and thats why it’s only 43days short.
ping avg 2ms no loss, no tcp problems. wish reproduce this with wider channels from AC.
maybe uptime of link is related to very good antennas from Jirous and quite ideal fresnel zone.
I reset PTP client unit to facory default but without cofnig
I set it up as PTP AP because could not see my other unit which suppoust to be PTP AP, I could not set 20/40/80 channel wide in quickset, have to made it manually.
When I came to other location I’ve noticed that the PTP AP got reset by itself Oo, so I made factory reset again to be sure all is fine
I set it up as PTP APC but could not see any other network on scan than 20Mhz channel wide.
Right now I am going to check the previous one PTP AP to see whats going on.
Dont worry @plisken you tested the settings from first posts and you got good result
Please see my test after all resets and reconfig https://www.youtube.com/watch?v=yijQaSYx2hc
Looks much better, a bit more stable and better latency, but ccq is totaly not relevant to quality in MT as I can see.
Also I changed PTP AP to second unit maybe that was the reason also ?
Great result, CCQ is not so bad on this speed.
This settings use a very great bandtwidth.
How bigger the bandwidth how more unstable.
I find this a very successful test.
Maby use another frequency and try out.