Hi all,
Well i have a cell in a rural area with clean channels so i put an omnitik and i have clients connected from 1 to 12km (.6mi to 7mi)
The clients are all Mikrotik of course (otherway we cant enable nv2) they are mostly Sextant 5HnD but i have a few 411AH with XR5 with a 23dBi panels (the farest ones)
So the AP its running on both 802.11 a / n with both chains enabled.
The signals of the clients are:
And the TxCCQ on AP side is:
The problem comes (i think) With my nv2 setup. At full use i get a 52% of CPU in the Omnitik but the troughput can’t pass 12mbps, i tough maybe my internet connection had a problem, but no, i tried from the ethernet side make a btest from my laptop to a client and when the AP its running 12mbps i get around 54kbps on both directions.
If the traffic goes down to 7 mbps and i make the btest i get the 5mbps . so the AP cant reach more than 12mbps.
I am running NV2 defaults except for the Cell radius, i put 15km (3 more just in case).
But i dont know the following?
TDMA Period size: im running 4 that increase a little the bandwith (from 11.2 to 12mbps), but increased too the latency (around 12ms).
Cell Radius: 15km ( farest client its between 12-13km.)
Queue Count: 2 (No idea what for it is this)
QoS: Default (either)
On HT Tab i’m using defaults with both chains enabled.
How can i improve the troughput on the AP side.. Im about to test with nstreme But i dont want to because as far as i know nstream cant handle very well the dual chain setting. (am i right?)
Many of your signal levels are far too low.
This results in low air rates for the affected clients,
which will lower your total throughput for all clients in return.
Aim for -65dB RX-level (CPE and Omni).
Use mikrotik linkcalc to estimate needed TX-Power and Antenna-type.
Try to never go below -70dB RX-level. Everything less is instable and unreliable,
Also you’re mixing A and N, that’s bad. Kick all A-Clients. Only use N-Clients.
Have you already enabled both HT-Chains (H and V polarization) and 40MHz (extension channel)?
Have you disabled default forwarding on your omnitik? (to ensure CPEs cannot communicated to each other)
I agree with you about the signal level, i think im going to sectorize this zone. I cant kick all A clients because their radios are A, i will consider changing to N tough.
I have both chains enabled and i will stay on 20Mhz, in the other hand i didnt have disabled the default forwarding, and didnt notice until you wrote it.. thanks.. i will see how the behavor is with this setting off.
I had a 20dbi Sector from Ubnt, but the equipment that was doing the job died with a lightning storm. Someone stole our ground cable… The omnitik survived and i connected all the clients on it and was doing an amaizing job, but i will put the sectors again
The omnitik survived and i connected all the clients on it and was doing an amaizing job, but i will put the sectors again 