Im having trouble using NV2 on some (most) of my P2MTP. I use RB912 with RF Element horn at my towers, and RB911 with RF Element Stationbox XL as CPE. (Some are RB711 and Stationbox Micro) 20MHz and both HT enabled
There is about 20+ clients.
My problem is that with NV2 it seems to peak at 20-23 Mbps total, but with 802.11 it has no problems with 50-60Mbps ++ total.
I have also seen this issue with P2P links (QRT) it performs much better with 802.11 than with NV2.
I would check to make sure all the subscribers have good connections. I’ve recently noticed with NV2 that one poor connection causes the whole AP to suffer dramatically.
What makes this interesting, is that CCQ drops when the link is idle and there’s no traffic. Yet, when there’s traffic all CCQs are well over the 80% and we still only get about 30Mbps / 35Mbps.
Given that CCQ drops when links are idle, just how are you supposed to know what a “bad link” is?
In which version did this start (if anyone knows). Would love to downgrade to a version where this isn’t an issue.
What makes this interesting, is that CCQ drops when the link is idle and there’s no traffic. Yet, when there’s traffic all CCQs are well over the 80% and we still only get about 30Mbps / 35Mbps.
CCQ can only be measured with active traffic.
This is why NV2 needs airtime fairness or at least a function to enable priority over each connection in PTMP.
NV2 is all about airtime, all clients are giving a “time slot” , only wifi radio basics are still the same.
Strange I have never seen one or more low signal,low ccq (or both) clients registered to a AP causing this, have you any examples to share to prove this point?
I suspect that for TDMA performance to be effected it would take the overall (average) signal + CCQ + SNR for the group of clients (?) to be low.
So then why we only seeing 20-30Mbps throughput on the APs? > > Back to square one…
running a loop here…
one more time ;
a client with Rx-rate connection rate of 52Mbps will have throughput of more or less 30Mbps when doing bandwidth test. at that moment the total bandwidth available to all clients will be 30Mbps.
next client ( Rx-rate 135Mbps ) doing bandwidth test will get more or less 15Mbps )
this because Ap has sfq interface queue active. which will divide available resources.
client with lowest “active” Rx-rate is total available bandwidth on AP
Are you sure about sfq, default now unless changed is “only-hardware-queue” https://wiki.mikrotik.com/wiki/Manual:Queue#SFQ
“Note: Starting from v5.8 there is new kind none and new default queue only-hardware-queue. All RouterBOARDS will have this new queue type set as default interface queue”
"only-hardware-queue leaves interface with only hw transmit descriptor ring buffer which acts as a queue in itself. Usually at least 100 packets can be queued for transmit in transmit descriptor ring buffer. Transmit descriptor ring buffer size and the amount of packets that can be queued in it varies for different types of ethernet MACs.
Having no software queue is especially beneficial on SMP systems because it removes the requirement to synchronize access to it from different cpus/cores which is expensive."
And a client whom is IDLE will have their ACTIVE rates, drop to as low as 6Mbps, with a CCQ of like 4%, or 6%… So even IF I have clients at 6Mbps, I still only get 30mbps throughput on the AP. WAY HIGHER than “client with lowest “active” Rx-rate is total available bandwidth on AP”
Back to square one…
So even IF I have clients at 6Mbps, I still only get 30mbps throughput on the AP. WAY HIGHER than “client with lowest “active” Rx-rate is total available bandwidth on AP”