Community discussions

MikroTik App
 
mariusmotea
just joined
Topic Author
Posts: 11
Joined: Mon Feb 01, 2016 7:18 pm

2.4ghz issues with hAP ac and hAP ac^2

Tue Jul 10, 2018 8:22 pm

Hi,

A have a very wired issue with Mikrotik routers from title on 2.4ghz frequency were all my home lights and sensors are connected. First i was using the Routerboard 962UiGS-5HacT2HnT, but because there were lot of moments when my lights start to not respond to commands or to respond with a few seconds delay i decide to return it. At that moment i was sure the router is faulty because i have also two cheap Tenda and TP-link routers that work with same network devices for months with absolutely no delays. This week i decide to buy an hAP ac^2 and i was very surprised to see that this one have identical issues with the previews model that is totally different hardware. In order to isolate the issue i made following things:
- remove one wifi device at a time until i can isolate if there is one wifi light/sensor that can cause issues
- run just with default webfig config to avoid any bad parameters
- avoid router PoE (normally is PoE powered)
- disconnect devices one by one when transmission latency start to be big in order to see if one device cause interferences
- power off all zigbee devices.
- tried RC firmware releases
- change wifi channel to avoid interference from neighbors (just 2)

None on these give me a clue what else can be wrong except one very wired behavior when i disconnect one device from the network (random) the ping replies between devices start to be very big and this can be saw in the middle of the following output when i disconnect two wifi lights:
64 bytes from 192.168.88.1: icmp_seq=263 ttl=64 time=839 ms
64 bytes from 192.168.88.1: icmp_seq=264 ttl=64 time=581 ms
64 bytes from 192.168.88.1: icmp_seq=265 ttl=64 time=3.66 ms
64 bytes from 192.168.88.1: icmp_seq=266 ttl=64 time=2.51 ms
64 bytes from 192.168.88.1: icmp_seq=267 ttl=64 time=2.66 ms
64 bytes from 192.168.88.1: icmp_seq=268 ttl=64 time=1.10 ms
64 bytes from 192.168.88.1: icmp_seq=269 ttl=64 time=0.963 ms
64 bytes from 192.168.88.1: icmp_seq=270 ttl=64 time=199 ms
64 bytes from 192.168.88.1: icmp_seq=271 ttl=64 time=1005 ms #### first light disconnected here, second one about 10 replies later
64 bytes from 192.168.88.1: icmp_seq=272 ttl=64 time=3.23 ms
64 bytes from 192.168.88.1: icmp_seq=273 ttl=64 time=1926 ms
64 bytes from 192.168.88.1: icmp_seq=274 ttl=64 time=986 ms
64 bytes from 192.168.88.1: icmp_seq=275 ttl=64 time=615 ms
64 bytes from 192.168.88.1: icmp_seq=276 ttl=64 time=3699 ms
64 bytes from 192.168.88.1: icmp_seq=277 ttl=64 time=2692 ms
64 bytes from 192.168.88.1: icmp_seq=278 ttl=64 time=1668 ms
64 bytes from 192.168.88.1: icmp_seq=279 ttl=64 time=644 ms
64 bytes from 192.168.88.1: icmp_seq=280 ttl=64 time=434 ms
64 bytes from 192.168.88.1: icmp_seq=281 ttl=64 time=977 ms
64 bytes from 192.168.88.1: icmp_seq=282 ttl=64 time=597 ms
64 bytes from 192.168.88.1: icmp_seq=283 ttl=64 time=1435 ms
64 bytes from 192.168.88.1: icmp_seq=284 ttl=64 time=1700 ms
64 bytes from 192.168.88.1: icmp_seq=285 ttl=64 time=1779 ms
64 bytes from 192.168.88.1: icmp_seq=286 ttl=64 time=920 ms
64 bytes from 192.168.88.1: icmp_seq=287 ttl=64 time=176 ms
64 bytes from 192.168.88.1: icmp_seq=288 ttl=64 time=556 ms
64 bytes from 192.168.88.1: icmp_seq=289 ttl=64 time=379 ms
64 bytes from 192.168.88.1: icmp_seq=290 ttl=64 time=1741 ms
64 bytes from 192.168.88.1: icmp_seq=291 ttl=64 time=940 ms
64 bytes from 192.168.88.1: icmp_seq=292 ttl=64 time=269 ms
64 bytes from 192.168.88.1: icmp_seq=293 ttl=64 time=237 ms
64 bytes from 192.168.88.1: icmp_seq=294 ttl=64 time=613 ms
64 bytes from 192.168.88.1: icmp_seq=295 ttl=64 time=1769 ms
64 bytes from 192.168.88.1: icmp_seq=296 ttl=64 time=1211 ms
64 bytes from 192.168.88.1: icmp_seq=298 ttl=64 time=12188 ms
64 bytes from 192.168.88.1: icmp_seq=299 ttl=64 time=11182 ms
64 bytes from 192.168.88.1: icmp_seq=300 ttl=64 time=10158 ms
64 bytes from 192.168.88.1: icmp_seq=301 ttl=64 time=9134 ms
64 bytes from 192.168.88.1: icmp_seq=302 ttl=64 time=8110 ms
64 bytes from 192.168.88.1: icmp_seq=303 ttl=64 time=7086 ms
64 bytes from 192.168.88.1: icmp_seq=304 ttl=64 time=6062 ms
64 bytes from 192.168.88.1: icmp_seq=305 ttl=64 time=5038 ms
64 bytes from 192.168.88.1: icmp_seq=306 ttl=64 time=4014 ms
64 bytes from 192.168.88.1: icmp_seq=307 ttl=64 time=2990 ms
64 bytes from 192.168.88.1: icmp_seq=308 ttl=64 time=3116 ms
64 bytes from 192.168.88.1: icmp_seq=309 ttl=64 time=2091 ms
64 bytes from 192.168.88.1: icmp_seq=310 ttl=64 time=1092 ms
64 bytes from 192.168.88.1: icmp_seq=311 ttl=64 time=665 ms
64 bytes from 192.168.88.1: icmp_seq=312 ttl=64 time=656 ms
64 bytes from 192.168.88.1: icmp_seq=313 ttl=64 time=1649 ms
64 bytes from 192.168.88.1: icmp_seq=314 ttl=64 time=1709 ms
64 bytes from 192.168.88.1: icmp_seq=315 ttl=64 time=1393 ms
64 bytes from 192.168.88.1: icmp_seq=316 ttl=64 time=2733 ms
64 bytes from 192.168.88.1: icmp_seq=317 ttl=64 time=3214 ms
64 bytes from 192.168.88.1: icmp_seq=318 ttl=64 time=2183 ms
64 bytes from 192.168.88.1: icmp_seq=319 ttl=64 time=1866 ms
64 bytes from 192.168.88.1: icmp_seq=320 ttl=64 time=849 ms
64 bytes from 192.168.88.1: icmp_seq=321 ttl=64 time=1402 ms
64 bytes from 192.168.88.1: icmp_seq=322 ttl=64 time=1109 ms
64 bytes from 192.168.88.1: icmp_seq=323 ttl=64 time=662 ms
64 bytes from 192.168.88.1: icmp_seq=324 ttl=64 time=2814 ms
64 bytes from 192.168.88.1: icmp_seq=325 ttl=64 time=2752 ms
64 bytes from 192.168.88.1: icmp_seq=326 ttl=64 time=1729 ms
64 bytes from 192.168.88.1: icmp_seq=327 ttl=64 time=729 ms
64 bytes from 192.168.88.1: icmp_seq=328 ttl=64 time=3656 ms
64 bytes from 192.168.88.1: icmp_seq=329 ttl=64 time=5473 ms
64 bytes from 192.168.88.1: icmp_seq=330 ttl=64 time=4450 ms
64 bytes from 192.168.88.1: icmp_seq=331 ttl=64 time=3425 ms
64 bytes from 192.168.88.1: icmp_seq=332 ttl=64 time=5189 ms
64 bytes from 192.168.88.1: icmp_seq=333 ttl=64 time=4173 ms
64 bytes from 192.168.88.1: icmp_seq=334 ttl=64 time=3149 ms
64 bytes from 192.168.88.1: icmp_seq=335 ttl=64 time=2149 ms
64 bytes from 192.168.88.1: icmp_seq=336 ttl=64 time=5433 ms
64 bytes from 192.168.88.1: icmp_seq=337 ttl=64 time=4409 ms
64 bytes from 192.168.88.1: icmp_seq=341 ttl=64 time=4688 ms
64 bytes from 192.168.88.1: icmp_seq=342 ttl=64 time=3687 ms
64 bytes from 192.168.88.1: icmp_seq=343 ttl=64 time=7856 ms
64 bytes from 192.168.88.1: icmp_seq=344 ttl=64 time=6832 ms
64 bytes from 192.168.88.1: icmp_seq=345 ttl=64 time=5808 ms
64 bytes from 192.168.88.1: icmp_seq=346 ttl=64 time=4808 ms
64 bytes from 192.168.88.1: icmp_seq=347 ttl=64 time=3792 ms
64 bytes from 192.168.88.1: icmp_seq=348 ttl=64 time=2768 ms
64 bytes from 192.168.88.1: icmp_seq=349 ttl=64 time=1744 ms
64 bytes from 192.168.88.1: icmp_seq=350 ttl=64 time=3579 ms
64 bytes from 192.168.88.1: icmp_seq=351 ttl=64 time=2579 ms
64 bytes from 192.168.88.1: icmp_seq=352 ttl=64 time=2383 ms
64 bytes from 192.168.88.1: icmp_seq=353 ttl=64 time=1359 ms
64 bytes from 192.168.88.1: icmp_seq=354 ttl=64 time=359 ms
64 bytes from 192.168.88.1: icmp_seq=355 ttl=64 time=5636 ms
64 bytes from 192.168.88.1: icmp_seq=356 ttl=64 time=4629 ms
64 bytes from 192.168.88.1: icmp_seq=357 ttl=64 time=3606 ms
64 bytes from 192.168.88.1: icmp_seq=358 ttl=64 time=4009 ms
64 bytes from 192.168.88.1: icmp_seq=359 ttl=64 time=2986 ms
64 bytes from 192.168.88.1: icmp_seq=360 ttl=64 time=1962 ms
64 bytes from 192.168.88.1: icmp_seq=361 ttl=64 time=4715 ms
64 bytes from 192.168.88.1: icmp_seq=362 ttl=64 time=3715 ms
64 bytes from 192.168.88.1: icmp_seq=363 ttl=64 time=4130 ms
64 bytes from 192.168.88.1: icmp_seq=364 ttl=64 time=3106 ms
64 bytes from 192.168.88.1: icmp_seq=365 ttl=64 time=2082 ms
64 bytes from 192.168.88.1: icmp_seq=366 ttl=64 time=2045 ms
64 bytes from 192.168.88.1: icmp_seq=367 ttl=64 time=1030 ms
64 bytes from 192.168.88.1: icmp_seq=368 ttl=64 time=1466 ms
64 bytes from 192.168.88.1: icmp_seq=369 ttl=64 time=1295 ms
64 bytes from 192.168.88.1: icmp_seq=370 ttl=64 time=294 ms
64 bytes from 192.168.88.1: icmp_seq=371 ttl=64 time=1827 ms
64 bytes from 192.168.88.1: icmp_seq=372 ttl=64 time=809 ms
64 bytes from 192.168.88.1: icmp_seq=373 ttl=64 time=4092 ms
64 bytes from 192.168.88.1: icmp_seq=374 ttl=64 time=3076 ms
64 bytes from 192.168.88.1: icmp_seq=375 ttl=64 time=2052 ms
64 bytes from 192.168.88.1: icmp_seq=376 ttl=64 time=2282 ms
64 bytes from 192.168.88.1: icmp_seq=377 ttl=64 time=1258 ms
64 bytes from 192.168.88.1: icmp_seq=378 ttl=64 time=3160 ms
64 bytes from 192.168.88.1: icmp_seq=379 ttl=64 time=4455 ms
64 bytes from 192.168.88.1: icmp_seq=380 ttl=64 time=3450 ms
64 bytes from 192.168.88.1: icmp_seq=381 ttl=64 time=2427 ms
64 bytes from 192.168.88.1: icmp_seq=382 ttl=64 time=4291 ms
64 bytes from 192.168.88.1: icmp_seq=383 ttl=64 time=3276 ms
64 bytes from 192.168.88.1: icmp_seq=384 ttl=64 time=2275 ms
64 bytes from 192.168.88.1: icmp_seq=385 ttl=64 time=2935 ms
64 bytes from 192.168.88.1: icmp_seq=386 ttl=64 time=1911 ms
64 bytes from 192.168.88.1: icmp_seq=387 ttl=64 time=1540 ms
64 bytes from 192.168.88.1: icmp_seq=388 ttl=64 time=1145 ms
64 bytes from 192.168.88.1: icmp_seq=389 ttl=64 time=481 ms
64 bytes from 192.168.88.1: icmp_seq=390 ttl=64 time=374 ms
64 bytes from 192.168.88.1: icmp_seq=391 ttl=64 time=1299 ms
64 bytes from 192.168.88.1: icmp_seq=392 ttl=64 time=288 ms
64 bytes from 192.168.88.1: icmp_seq=393 ttl=64 time=66.9 ms
64 bytes from 192.168.88.1: icmp_seq=394 ttl=64 time=88.8 ms
64 bytes from 192.168.88.1: icmp_seq=395 ttl=64 time=2.09 ms
64 bytes from 192.168.88.1: icmp_seq=396 ttl=64 time=2.19 ms
64 bytes from 192.168.88.1: icmp_seq=397 ttl=64 time=2.04 ms
64 bytes from 192.168.88.1: icmp_seq=398 ttl=64 time=11.8 ms
64 bytes from 192.168.88.1: icmp_seq=399 ttl=64 time=483 ms
64 bytes from 192.168.88.1: icmp_seq=400 ttl=64 time=2.05 ms
64 bytes from 192.168.88.1: icmp_seq=401 ttl=64 time=2.03 ms
64 bytes from 192.168.88.1: icmp_seq=402 ttl=64 time=0.940 ms
64 bytes from 192.168.88.1: icmp_seq=403 ttl=64 time=2.60 ms
64 bytes from 192.168.88.1: icmp_seq=404 ttl=64 time=2.39 ms
64 bytes from 192.168.88.1: icmp_seq=405 ttl=64 time=978 ms
64 bytes from 192.168.88.1: icmp_seq=406 ttl=64 time=0.825 ms
64 bytes from 192.168.88.1: icmp_seq=407 ttl=64 time=1.41 ms
64 bytes from 192.168.88.1: icmp_seq=408 ttl=64 time=4.01 ms
64 bytes from 192.168.88.1: icmp_seq=409 ttl=64 time=384 ms
64 bytes from 192.168.88.1: icmp_seq=410 ttl=64 time=130 ms
64 bytes from 192.168.88.1: icmp_seq=411 ttl=64 time=449 ms
64 bytes from 192.168.88.1: icmp_seq=412 ttl=64 time=0.822 ms
64 bytes from 192.168.88.1: icmp_seq=413 ttl=64 time=1.96 ms
64 bytes from 192.168.88.1: icmp_seq=414 ttl=64 time=2.28 ms
64 bytes from 192.168.88.1: icmp_seq=415 ttl=64 time=1.12 ms
64 bytes from 192.168.88.1: icmp_seq=416 ttl=64 time=0.944 ms
64 bytes from 192.168.88.1: icmp_seq=417 ttl=64 time=1.10 ms
64 bytes from 192.168.88.1: icmp_seq=418 ttl=64 time=2.30 ms
64 bytes from 192.168.88.1: icmp_seq=419 ttl=64 time=1.04 ms
With Tenda and TP-link routers i have stable ping with all devices (~2ms) and when i disconnect one device i did not saw any increase of latency. Any help will be appreciated as i lose lot of time trying to fix this problem.

Thanks,
Marius.
Last edited by mariusmotea on Wed Jul 11, 2018 4:53 pm, edited 1 time in total.
 
Faceless
just joined
Posts: 18
Joined: Sat Mar 03, 2018 4:03 pm
Location: Ukraine
Contact:

Re: 2.4ghz issues with hAP ac and hAP ac^2

Wed Jul 11, 2018 4:04 pm

Try to update to 6.42.5 RouterOS and play with Wireless>advanced>Hw retries choose 5-7 or 15.
 
mariusmotea
just joined
Topic Author
Posts: 11
Joined: Mon Feb 01, 2016 7:18 pm

Re: 2.4ghz issues with hAP ac and hAP ac^2

Wed Jul 11, 2018 7:34 pm

Thanks, it was 7 i put 15. Will run a few days with this option to see what will happend.
 
mariusmotea
just joined
Topic Author
Posts: 11
Joined: Mon Feb 01, 2016 7:18 pm

Re: 2.4ghz issues with hAP ac and hAP ac^2

Wed Jul 11, 2018 8:41 pm

No luck, i will put 5 now and test. It seams that if i use Hue Entertainment stream protocol that send 25 frames per second to hue bridge will trigger the issue faster.
64 bytes from 192.168.10.30: icmp_seq=109 ttl=128 time=2477 ms
64 bytes from 192.168.10.30: icmp_seq=112 ttl=128 time=2131 ms
64 bytes from 192.168.10.30: icmp_seq=114 ttl=128 time=1308 ms
64 bytes from 192.168.10.30: icmp_seq=136 ttl=128 time=1224 ms
64 bytes from 192.168.10.30: icmp_seq=166 ttl=128 time=1275 ms
64 bytes from 192.168.10.30: icmp_seq=170 ttl=128 time=1204 ms
64 bytes from 192.168.10.30: icmp_seq=175 ttl=128 time=1236 ms
64 bytes from 192.168.10.30: icmp_seq=176 ttl=128 time=1338 ms
 
mariusmotea
just joined
Topic Author
Posts: 11
Joined: Mon Feb 01, 2016 7:18 pm

Re: 2.4ghz issues with hAP ac and hAP ac^2

Fri Jul 13, 2018 11:44 am

Is possible that the issue to be generated by my RaspberryPi3 with built in wifi. I disconnect this from power and in last 2 days i did not have any issues. Hope this to be the problem. Question remain why only Mikrotik routers are affected by this and cheep ones not.
 
antonsb
MikroTik Support
MikroTik Support
Posts: 212
Joined: Sun Jul 24, 2016 3:12 pm
Location: Riga, Latvia

Re: 2.4ghz issues with hAP ac and hAP ac^2

Wed Jul 18, 2018 11:00 am

known issue on RPI3 and RPIzeroW:
https://github.com/raspberrypi/firmware/issues/839
 
mariusmotea
just joined
Topic Author
Posts: 11
Joined: Mon Feb 01, 2016 7:18 pm

Re: 2.4ghz issues with hAP ac and hAP ac^2

Tue Jul 24, 2018 12:06 pm

No issues in last two weeks so very likely this was the issue. I made upgrade to raspberry firmware and i will give a new try now.

Marius.
 
badziew
just joined
Posts: 3
Joined: Wed Jul 25, 2018 10:24 pm

Re: 2.4ghz issues with hAP ac and hAP ac^2

Wed Jul 25, 2018 10:27 pm

I have different problem with 2,4Ghz WiFi on hAP ac^2: it's completely unusable when any specific frequency is selected. Access point visibility is intermittent (maybe several seconds over two minutes). It's all fine when the frequency is set to auto.
 
Niffchen
newbie
Posts: 35
Joined: Thu Mar 22, 2018 1:36 pm

Re: 2.4ghz issues with hAP ac and hAP ac^2

Thu Aug 02, 2018 12:27 pm

I have different problem with 2,4Ghz WiFi on hAP ac^2: it's completely unusable when any specific frequency is selected. Access point visibility is intermittent (maybe several seconds over two minutes). It's all fine when the frequency is set to auto.
I have the same issues with CAPsMAN and the connected hAP ac2 APs. I not really solved this issue but I recognized the I have problems with connections/packet loss/loops and the CAP is reconnecting after seconds, minutes, hours and the performance is the same as you mentioned. For weeks I was adjusting frequencies until I recognized that this was not the reason. I could see in the log of the hAP that the CAP gets a disconnect after "sent max keealive without response". Do you have some strange messages at your logfile?

Could you try to disable RSTP on the bridge of the hAP and choose "none". This solved the performance issues with my wireless environment. Maybe you have a similar problem like me ;-)
I hope I will find the reason for this very soon.
Last edited by Niffchen on Thu Aug 02, 2018 12:31 pm, edited 1 time in total.
 
badziew
just joined
Posts: 3
Joined: Wed Jul 25, 2018 10:24 pm

Re: 2.4ghz issues with hAP ac and hAP ac^2

Thu Aug 02, 2018 9:14 pm

Actually, I think it was 40MHz channel width that was causing 2,4GHz WiFi to barely work. It's 100% fine on 20MHz, because only devices that use it are 2DSXL, PSVita and HP printer...

Who is online

Users browsing this forum: ASP71 and 15 guests