Time out and Lantency

RouterOS Wireless Networking
1

hi friends.
I’m having the problem with my AP’s . About 200 meter the RB 230 Ap node is away from Ap GW, and I’m having latency, time out. Ok I use one MT AP to connect 30 client on it all going out via ether1 from ether1 via 5.8 to GW and then going to Wifi server. Each single client is limited to 256kbps. I have 22 Ap’s node connect to GW .
Ping result.


[selim@BLD2140-B] > ping 10.84.0.1
10.84.0.1 64 byte ping: ttl=62 time=120 ms
10.84.0.1 64 byte ping: ttl=62 time=5 ms
10.84.0.1 64 byte ping: ttl=62 time=13 ms
10.84.0.1 64 byte ping: ttl=62 time=9 ms
10.84.0.1 64 byte ping: ttl=62 time=113 ms
10.84.0.1 64 byte ping: ttl=62 time=500 ms
10.84.0.1 64 byte ping: ttl=62 time=112 ms
10.84.0.1 64 byte ping: ttl=62 time=277 ms
10.84.0.1 ping timeout
10.84.0.1 ping timeout
10.84.0.1 64 byte ping: ttl=62 time=114 ms
10.84.0.1 64 byte ping: ttl=62 time=413 ms
10.84.0.1 64 byte ping: ttl=62 time=65 ms
10.84.0.1 64 byte ping: ttl=62 time=120 ms
10.84.0.1 64 byte ping: ttl=62 time=330 ms
10.84.0.1 64 byte ping: ttl=62 time=351 ms
16 packets transmitted, 14 packets received, 12% packet loss
round-trip min/avg/max = 5/181.5/500 ms



15 Clients are on line with 256kbps speed limited.

received-packets-per-second: 62
received-bits-per-second: 231.5kbps
sent-packets-per-second: 56
sent-bits-per-second: 365.0kbps

They are complain about the internet is slow.

Here is the static of 5.8 configuration. And I don’t use the 2.4 wireless all the clients using cable via ether1 or ether2 depend.

Flags: X - disabled, R - running
0 R name=“5.8Ghz” mtu=1500 mac-address=00:0B:6B:34:07:8A arp=enabled disable-running-check=no interface-type=Atheros AR5212
radio-name=“bld2140b” mode=station ssid=“votra” area=“” frequency-mode=superchannel country=no_country_set antenna-gain=0
frequency=5825 band=5ghz scan-list=default rate-set=default supported-rates-b=1Mbps,2Mbps,5.5Mbps,11Mbps
supported-rates-a/g=6Mbps,9Mbps,12Mbps,18Mbps,24Mbps,36Mbps,48Mbps,54Mbps basic-rates-b=1Mbps basic-rates-a/g=6Mbps
max-station-count=2007 ack-timeout=dynamic tx-power-mode=default noise-floor-threshold=default periodic-calibration=default
periodic-calibration-interval=60 burst-time=disabled dfs-mode=none antenna-mode=ant-a wds-mode=disabled wds-default-bridge=none
wds-default-cost=100 wds-cost-range=50-150 wds-ignore-ssid=no update-stats-interval=disabled default-authentication=yes
default-forwarding=yes default-ap-tx-limit=0 default-client-tx-limit=0 proprietary-extensions=pre-2.9.25 hide-ssid=no
security-profile=default disconnect-timeout=3s on-fail-retry-time=100ms preamble-mode=both compression=no allow-sharedkey=no
i saw to many things here like netsream periodic calibration . i have no idea what those two are . Most of the time I have time out in 5.8 links from node to AP, even sometimes giving me hard time to connect via ssh from GW to node or vice-versa.



Thx Selim. If some one can help me will be great.
:frowning:

2

what is your signal?

200 meters? you would need to set tx-power to as low as possible and perhaps even miss align the antenna.

3

Hi Equis
Here it is the signal

5.8Ghz Miles 00:15:6D:10:18:E8 yes -63dBm… 36Mbps 56m42s
I’m using RB230 in this point with Pannel 23 dBi. But I have RIC antenna also. GW is PC and I’m using Omni antenna 23 dBi and during the night I have so much latency, time out

thx Selim.

4

I am sorry I dont have an answer

Looks like interference tho, I guess you would have tried each channel?

do you have ccq like in 2.9?

5

Only during the night? What’s the environment like? Does it occur during summer/winter etc?

6

hi equis, bjohns

Equis I don’t know what is ccq honest :frowning: . If you can give me more explain how to look or what is it ccq.
I tired all channel. Nothing has been changed , all AP has 2.9.38 OS running.

Bjohns. Is accour during the winter like now I’m having the problem. Now in Kosovo is winter and tem is -5 and will go down more . But I don’t thing the winter make me this problem, . The time out the most of the time happen during the night. Also during the time has like 5 min laterncy and comes back and start working. In those 22 AP almost 300 till 400 people will connected and all using 256 kbps traffic limited.
The Gw is PC and I I see the traffic going throught is 5Mbits . This is not enought bandwith for those clients. But my pipe form ISP is more 40Mbits available .

thx selim .

7

Equis.
How can I do to set tx-power lower. Antennas are align good . No problem cuz I HAVE OPEN VIEW
thx selim

8

Hi, speaks on its bad perfomance of atheros cards with chipset as AP : http://forum.mikrotik.com/t/time-out-and-lantency/10887/1

9

Sorry correct poist is :
http://forum.mikrotik.com//viewtopic.php?p=60412

10

thanks kleber.

I’m using the CM9 and SR 5, what king of card should I use to make the network run better .
And all the time I have the problem about ping and time out with one word latency . As i write in this post I’m using only 5.8 to carry traffic to the GW and don’t use 2.4 wireless. And I wan to take out the latency on the 5.8. 22 Access Point almost all doing the same thing this is bad for me :frowning: . I really want to know what king of card should I use.
22 AP’s are align good, I use RB230, RIC 112, RB532, and all has CM9 card and SR5 . What should I do to take off the high ping.

thx Selim . sorry for my bad English.

11

Kleber watch this result.
[selim@BLD2090-C] > ping 10.84.32.1
10.84.32.1 64 byte ping: ttl=64 time=10 ms
10.84.32.1 64 byte ping: ttl=64 time=136 ms
10.84.32.1 64 byte ping: ttl=64 time=40 ms
10.84.32.1 64 byte ping: ttl=64 time=54 ms
10.84.32.1 64 byte ping: ttl=64 time=349 ms
10.84.32.1 ping timeout
10.84.32.1 64 byte ping: ttl=64 time=150 ms
10.84.32.1 64 byte ping: ttl=64 time=7 ms
10.84.32.1 64 byte ping: ttl=64 time=59 ms
10.84.32.1 64 byte ping: ttl=64 time=16 ms
10.84.32.1 64 byte ping: ttl=64 time=18 ms
10.84.32.1 64 byte ping: ttl=64 time=65 ms
10.84.32.1 64 byte ping: ttl=64 time=311 ms
10.84.32.1 64 byte ping: ttl=64 time=812 ms
10.84.32.1 64 byte ping: ttl=64 time=78 ms
10.84.32.1 64 byte ping: ttl=64 time=30 ms
10.84.32.1 64 byte ping: ttl=64 time=248 ms
10.84.32.1 64 byte ping: ttl=64 time=152 ms
10.84.32.1 ping timeout
10.84.32.1 ping timeout
10.84.32.1 64 byte ping: ttl=64 time=181 ms
10.84.32.1 64 byte ping: ttl=64 time=164 ms
10.84.32.1 ping timeout
10.84.32.1 64 byte ping: ttl=64 time=37 ms
10.84.32.1 ping timeout
10.84.32.1 64 byte ping: ttl=64 time=241 ms
10.84.32.1 ping timeout
10.84.32.1 ping timeout
10.84.32.1 ping timeout
10.84.32.1 ping timeout
10.84.32.1 ping timeout
10.84.32.1 ping timeout
10.84.32.1 ping timeout
10.84.32.1 64 byte ping: ttl=64 time=1 ms
10.84.32.1 64 byte ping: ttl=64 time=40 ms
10.84.32.1 64 byte ping: ttl=64 time=10 ms
10.84.32.1 64 byte ping: ttl=64 time=191 ms
10.84.32.1 64 byte ping: ttl=64 time=852 ms
10.84.32.1 64 byte ping: ttl=64 time=10 ms
10.84.32.1 64 byte ping: ttl=64 time=417 ms
10.84.32.1 ping timeout
10.84.32.1 64 byte ping: ttl=64 time=309 ms
10.84.32.1 ping timeout
10.84.32.1 ping timeout
10.84.32.1 64 byte ping: ttl=64 time=330 ms
10.84.32.1 64 byte ping: ttl=64 time=147 ms
10.84.32.1 ping timeout
10.84.32.1 ping timeout
10.84.32.1 ping timeout
10.84.32.1 ping timeout
10.84.32.1 64 byte ping: ttl=64 time=167 ms
10.84.32.1 64 byte ping: ttl=64 time=22 ms
10.84.32.1 64 byte ping: ttl=64 time=235 ms
10.84.32.1 64 byte ping: ttl=64 time=95 ms
10.84.32.1 64 byte ping: ttl=64 time=16 ms
10.84.32.1 64 byte ping: ttl=64 time=1 ms
10.84.32.1 64 byte ping: ttl=64 time=23 ms
10.84.32.1 64 byte ping: ttl=64 time=951 ms
10.84.32.1 ping timeout
10.84.32.1 ping timeout
10.84.32.1 64 byte ping: ttl=64 time=315 ms
10.84.32.1 64 byte ping: ttl=64 time=1 ms
10.84.32.1 64 byte ping: ttl=64 time=20 ms
10.84.32.1 64 byte ping: ttl=64 time=24 ms
10.84.32.1 64 byte ping: ttl=64 time=571 ms
10.84.32.1 64 byte ping: ttl=64 time=427 ms
10.84.32.1 64 byte ping: ttl=64 time=871 ms
10.84.32.1 64 byte ping: ttl=64 time=206 ms
10.84.32.1 64 byte ping: ttl=64 time=170 ms
10.84.32.1 64 byte ping: ttl=64 time=41 ms
10.84.32.1 64 byte ping: ttl=64 time=4 ms
10.84.32.1 ping timeout
10.84.32.1 64 byte ping: ttl=64 time=85 ms
10.84.32.1 64 byte ping: ttl=64 time=218 ms
10.84.32.1 64 byte ping: ttl=64 time=3 ms
10.84.32.1 64 byte ping: ttl=64 time=83 ms
10.84.32.1 64 byte ping: ttl=64 time=95 ms
10.84.32.1 64 byte ping: ttl=64 time=5 ms
10.84.32.1 64 byte ping: ttl=64 time=85 ms
10.84.32.1 64 byte ping: ttl=64 time=2 ms
10.84.32.1 64 byte ping: ttl=64 time=18 ms
10.84.32.1 64 byte ping: ttl=64 time=4 ms
10.84.32.1 ping timeout
10.84.32.1 64 byte ping: ttl=64 time=413 ms
10.84.32.1 64 byte ping: ttl=64 time=74 ms
10.84.32.1 64 byte ping: ttl=64 time=72 ms
10.84.32.1 64 byte ping: ttl=64 time=287 ms
10.84.32.1 ping timeout
10.84.32.1 ping timeout
10.84.32.1 ping timeout
10.84.32.1 64 byte ping: ttl=64 time=533 ms
10.84.32.1 64 byte ping: ttl=64 time=69 ms
10.84.32.1 64 byte ping: ttl=64 time=15 ms
10.84.32.1 64 byte ping: ttl=64 time=83 ms
10.84.32.1 64 byte ping: ttl=64 time=1 ms
10.84.32.1 64 byte ping: ttl=64 time=146 ms
10.84.32.1 64 byte ping: ttl=64 time=45 ms
10.84.32.1 64 byte ping: ttl=64 time=187 ms
10.84.32.1 ping timeout
10.84.32.1 64 byte ping: ttl=64 time=755 ms
10.84.32.1 ping timeout
10.84.32.1 64 byte ping: ttl=64 time=76 ms
10.84.32.1 64 byte ping: ttl=64 time=144 ms
10.84.32.1 64 byte ping: ttl=64 time=55 ms
10.84.32.1 64 byte ping: ttl=64 time=59 ms
10.84.32.1 64 byte ping: ttl=64 time=2 ms
10.84.32.1 64 byte ping: ttl=64 time=105 ms
10.84.32.1 64 byte ping: ttl=64 time=101 ms
10.84.32.1 64 byte ping: ttl=64 time=63 ms
10.84.32.1 64 byte ping: ttl=64 time=98 ms
10.84.32.1 64 byte ping: ttl=64 time=1 ms
10.84.32.1 64 byte ping: ttl=64 time=5 ms
10.84.32.1 64 byte ping: ttl=64 time=151 ms
10.84.32.1 64 byte ping: ttl=64 time=3 ms
10.84.32.1 64 byte ping: ttl=64 time=1 ms
10.84.32.1 64 byte ping: ttl=64 time=3 ms
10.84.32.1 64 byte ping: ttl=64 time=5 ms
10.84.32.1 64 byte ping: ttl=64 time=5 ms
10.84.32.1 64 byte ping: ttl=64 time=4 ms
10.84.32.1 64 byte ping: ttl=64 time=1 ms
10.84.32.1 ping timeout
10.84.32.1 ping timeout
10.84.32.1 64 byte ping: ttl=64 time=92 ms
10.84.32.1 64 byte ping: ttl=64 time=3 ms
10.84.32.1 64 byte ping: ttl=64 time=4 ms
10.84.32.1 64 byte ping: ttl=64 time=91 ms
10.84.32.1 64 byte ping: ttl=64 time=298 ms
10.84.32.1 64 byte ping: ttl=64 time=522 ms
10.84.32.1 ping timeout
10.84.32.1 ping timeout
10.84.32.1 64 byte ping: ttl=64 time=102 ms
10.84.32.1 64 byte ping: ttl=64 time=14 ms
10.84.32.1 64 byte ping: ttl=64 time=319 ms
10.84.32.1 64 byte ping: ttl=64 time=628 ms
10.84.32.1 64 byte ping: ttl=64 time=244 ms
10.84.32.1 64 byte ping: ttl=64 time=234 ms
10.84.32.1 ping timeout
10.84.32.1 64 byte ping: ttl=64 time=236 ms
10.84.32.1 64 byte ping: ttl=64 time=161 ms
10.84.32.1 64 byte ping: ttl=64 time=1 ms
10.84.32.1 64 byte ping: ttl=64 time=530 ms
10.84.32.1 64 byte ping: ttl=64 time=18 ms
10.84.32.1 64 byte ping: ttl=64 time=248 ms
10.84.32.1 ping timeout
10.84.32.1 64 byte ping: ttl=64 time=314 ms
10.84.32.1 64 byte ping: ttl=64 time=221 ms
10.84.32.1 64 byte ping: ttl=64 time=981 ms
10.84.32.1 64 byte ping: ttl=64 time=497 ms
10.84.32.1 ping timeout
10.84.32.1 ping timeout
10.84.32.1 ping timeout
10.84.32.1 64 byte ping: ttl=64 time=224 ms
10.84.32.1 ping timeout
10.84.32.1 ping timeout
10.84.32.1 ping timeout
10.84.32.1 64 byte ping: ttl=64 time=350 ms
156 packets transmitted, 116 packets received, 25% packet loss
round-trip min/avg/max = 1/173.4/981 ms

But during the day was working fine now time here 20:17 PM and look with what king of problem I’m having. And don’t know what to do .
Ap is RB532 GW is PC . GW has card Atheros AR5213, but AP RB 532 has Atheros AR5212
AP is away from GW let say max 300 meter is not long air line, I’m say 300 meter but could me less then 300 mm .


thx Selim.

12

I use winbox to set tx-power under wireless tab
300m is very very close.

have a look at teh status tab also, you will see tx/rx ccq this is quality of the link

13

Equis thx
I found but I see some options, all rates fixed, card rates, manual. What should I do now. how to lower tx-power, if you can send me the picture will be nice, to show me how to changed tx-power . I see in all rates fixed I see 17 dBm

seli_gl@yahoo.com
I have no problem with signal I thing meaby with signal to. Only with time out and ping is high. During the night is horrible slow.
her is all my result of my AP’s

INTERFACE MAC-ADDRESS AP SIGNAL… TX-RATE

0 5.8Ghz 00:0B:6B:4D:47:7F no -58dBm… 48Mbps
1 5.8Ghz
2 5.8Ghz 00:0C:42:05:03:57 no -75dBm… 36Mbps
3 5.8Ghz 00:02:6F:22:85:0E no -54dBm… 54Mbps
4 5.8Ghz 00:0B:6B:4D:03:34 no -63dBm… 54Mbps
5 5.8Ghz 00:0B:6B:4F:AD:4A no -66dBm… 54Mbps
6 5.8Ghz 00:0B:6B:4D:04:57 no -50dBm… 54Mbps
7 5.8Ghz 00:0B:6B:34:08:12 no -56dBm… 54Mbps
8 5.8Ghz 00:0B:6B:4D:04:1E no -67dBm… 48Mbps
9 5.8Ghz 00:02:6F:22:85:2C no -61dBm… 54Mbps
10 5.8Ghz 00:0B:6B:56:00:EF no -46dBm… 54Mbps
11 5.8Ghz 00:0B:6B:4D:03:90 no -55dBm… 48Mbps
12 5.8Ghz 00:0B:6B:34:07:8A no -70dBm… 48Mbps
13 5.8Ghz 00:0B:6B:4F:3A:56 no -78dBm… 54Mbps
14 5.8Ghz 00:0C:42:05:32:84 no -59dBm… 54Mbps
15 5.8Ghz 00:0B:6B:4F:3A:5E no -68dBm… 54Mbps
16 5.8Ghz 00:0C:42:05:03:3E no -60dBm… 54Mbps
17 5.8Ghz 00:0B:6B:34:06:6B no -56dBm… 54Mbps
18 5.8Ghz 00:02:6F:43:31:2E no -58dBm… 54Mbps
19 5.8Ghz 00:0B:6B:4D:04:54 no -60dBm… 54Mbps
20 5.8Ghz 00:0B:6B:34:0A:E1 no -64dBm… 54Mbps
21 5.8Ghz 00:0B:6B:34:06:69 no -77dBm… 36Mbps
22 5.8Ghz 00:02:6F:43:31:2F no -52dBm… 54Mbps
23 5.8Ghz 00:0B:6B:4D:05:6C no -52dBm… 54Mbps


thx Selim.

14

I dont think its signal, looks fine.

do you have heavy p2p user?

when is slow go to tools, torch and look for many connections, see who the offender is.

15

Equis.

Ok here is result of /inte wire reg pr stats.

0 interface=5.8Ghz radio-name=“milesGW” mac-address=00:15:6D:10:18:E8
ap=yes wds=no rx-rate=48Mbps tx-rate=54Mbps packets=4993,8207
bytes=345933,10174737 frames=4993,8315 frame-bytes=316623,10127115
hw-frames=4993,8325 hw-frame-bytes=436455,10326935 uptime=3m28s
last-activity=10ms signal-strength=-48dBm@6Mbps signal-to-noise=53dB
strength-at-rates=-48dBm@6Mbps 850ms,-48dBm@9Mbps 3m26s620ms,-48dBm@12Mbps
3m20s190ms,-49dBm@18Mbps 3m20s170ms,-48dBm@24Mbps
3m19s320ms,-52dBm@36Mbps 3m10s680ms,-53dBm@48Mbps 10ms,-
54dBm@54Mbps 80ms
tx-signal-strength=-56dBm tx-ccq=99% rx-ccq=98% p-throughput=5857
ack-timeout=28 distance=28 nstreme=no framing-mode=none
routeros-version=“2.9.38” last-ip=63.209.144.195 802.1x-port-enabled=yes
authentication-type=none encryption=none compression=no
the tx-ccq=99% rx-ccq=98% is good or bad, what higher % and what lower, which one is good..

I did changed in 15 dBm tx-power looks good for now I will do test in night and to see what king of result i will have, I think we are closer to result problem. Thanks very very much .
All AP’s are closer to GW let say the some AP can be longer 1000 meter.

Selim.

16

tx-ccq=99% rx-ccq=98%

This is very good…

17

Equis
I don’t know how to how much I’m thankful for you help. I will try tonight and push down all AP tx-power in 15 dBm and I will see what is gonna happen.

Sorry I didn’t answer in your question above. I have all clients using cable I don’t have heavy 2p2 connection . All clients are cable<>switch<> RB230, RB532, RIC whatever RB is , via 5.8Ghz <>PC GW<> and main link out in public.

thx selim .

18

Have tried changing channel also?

Change channel at the time when it is slow

Hopefully your problem will be no more

19

Hi Equis.

I push the GW to 13 dBm and working much much better than it was. The signal was increased. But some AP has tx-ccq= rx-ccq= under 50% what should I do to improved it this one . Should I change wireless card, or what should I do. And what kind of wireless card you are using. What do you thing the sector antenna is gonna make work better , cuz all AP’s faced to the GW I don’t need to use omni if the sector make better I have good position to use sector. If you have any idea
By the way
“I learning what is tx-ccq and rx-ccq”
:smiley: :wink:

Thanks Selim.

20

Hello

You should change channel till ccq is as high as possible.

I use cm9 mostly

You should use the tightest antenna you can to do the job.

So a sector better than omni
a panel better then sector

How many clients connect to the omni you have?
Omni’s suck real bad in high rf noise environment.

Thanks :wink: