I have noticed that when individual unit ack time gets high everyone on the link suffers. And if I bump that client off they return with a better ack. And a very short time later the system is running a lot smoother.
The people with the high ack time are not the same each time, even my own link wish connects at -65 had a ack the other day of 300 but i reset myself and returned to the normal ack of 56.
I was wondering if there is a script out there or you know a way to write one that would scan thought he list and bump people off at a set ack that I set.
I’m not sure this is the best way to handle the issue but it seems like what would work for me.
Set your ACK timeout on your AP to be that of your furthest Client (Highest ACK timeout).
When the ACK go above this number the client will disconnect automatically.
Just a few questions,
(1) setting ACK timeout to furthest Client, for example is this furthest client has a 105us timeout is there a extra margin to allow with this figure say 105+10%,
(2) I have one AP ACK timeout set at 110us but i note one cpe had a dynamic timeout of 406us but after a reboot it is 88us, (ccq 90+%)
(3) Should the each cpe ACK be manually set to match the AP ACK which is set for the furthest away CPE + % margin ( example - AP 110us all CPE’s =110us)
(4) By having different ACK timeout figures for each cpe effect performance,
(4) Is there a script to reboot a router with a high ACK,
Every transmition requires a receive of an acknowledgement (does not matter which radio Client or AP).
The ack timeout is the amount of time from transmition before an ack can be expected to be received.
If this does not happen withing the acktimeout setting, the the transmitted packet is assume to be lost and the packet is then retransmitted.
The ack timeout is only relevent to the transmitter, this is why the AP is set to the furthest client.
It is always good to add a little margin on the ack timeout setting. Typically this is a prefference thing (no hard and cold rule of thumb) typically 5%-20%.
If there is a problem with transmition the client disconnects then reconnects.
A more precise acktimeout value will optimize the performance of your AP.
I have no problem with disconnects this is to optimize the network,
You say timeout is revelant to the transmitter, is that the AP and assuming it is the AP is there any need to manually set CPE’s,
Next question is after manually setting the ACK for the network, is RTS/CTS setting, i was going to post another topic on this,
I believe rts/cts should only set on the cpe’s and not the AP, but what setting and what is the best way to test?
As i have 100% Mikrotik network would ntstreme would be a easier option for this (OS v3.30) or does this also have more variables,
The client is also a transmitter, however the ack timeout on the client should be set for the client distance.
Only the AP should be set for the furthest.
As for rts/cts Just set the AP for cts to self.
As far as nstreme; it has come a long way, and performs rather well.
With that said, nstreme does break down in some environments, and rts/cts may work better in these instances.
I do prefer nstreme where I can use it.