Page 1 of 2

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 5:41 am
by yhfung
Based on the presented results, it is confirmed the new rc5 works for my Macbook Pro Retina 2015 for 5GHz connection. However when I compared the 2.4GHz results, it seems that the results look very similar. There is no significant improvement if we compared the speed and Retr count number. If MikroTik Engineering Team can resolve this 2.4GHz issue as well, then the whole product hAP ac^2 is a very good and priced competitive product in the world!!!

By the way, many thanks is given to jarda, who was expediting this matter with MirkoTik Team many times otherwise we are still waiting for the resolution.

YH

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 7:20 am
by yhfung
In this morning, I carried out the 5GHz and 2.4GHz test. I found that the 5GHz now is very stable using the rc5. There are still problems with 2.4GHz, please take a look at the following listing. Please note there are some disconnection found in the middle of the listing. Also the ping time is extremely large, which is unacceptable. I do believe MikroTik has the ability to resolve this issue.

Listing 1: 2.4G ping time using MacBook Pro Retina 2015
ping 192.168.10.1
PING 192.168.10.1 (192.168.10.1): 56 data bytes
64 bytes from 192.168.10.1: icmp_seq=0 ttl=64 time=0.774 ms
64 bytes from 192.168.10.1: icmp_seq=1 ttl=64 time=1.182 ms
64 bytes from 192.168.10.1: icmp_seq=2 ttl=64 time=2.112 ms
64 bytes from 192.168.10.1: icmp_seq=3 ttl=64 time=1.018 ms
64 bytes from 192.168.10.1: icmp_seq=4 ttl=64 time=1.785 ms
64 bytes from 192.168.10.1: icmp_seq=5 ttl=64 time=127.967 ms
64 bytes from 192.168.10.1: icmp_seq=6 ttl=64 time=1.258 ms
64 bytes from 192.168.10.1: icmp_seq=7 ttl=64 time=142.877 ms
64 bytes from 192.168.10.1: icmp_seq=8 ttl=64 time=0.877 ms
64 bytes from 192.168.10.1: icmp_seq=9 ttl=64 time=0.942 ms
64 bytes from 192.168.10.1: icmp_seq=10 ttl=64 time=25.295 ms
64 bytes from 192.168.10.1: icmp_seq=11 ttl=64 time=0.914 ms
64 bytes from 192.168.10.1: icmp_seq=12 ttl=64 time=3.511 ms
64 bytes from 192.168.10.1: icmp_seq=13 ttl=64 time=16.145 ms
64 bytes from 192.168.10.1: icmp_seq=14 ttl=64 time=515.981 ms
64 bytes from 192.168.10.1: icmp_seq=15 ttl=64 time=967.542 ms
Request timeout for icmp_seq 16
64 bytes from 192.168.10.1: icmp_seq=16 ttl=64 time=1216.925 ms
64 bytes from 192.168.10.1: icmp_seq=17 ttl=64 time=212.107 ms
64 bytes from 192.168.10.1: icmp_seq=18 ttl=64 time=0.884 ms
64 bytes from 192.168.10.1: icmp_seq=19 ttl=64 time=3.156 ms
64 bytes from 192.168.10.1: icmp_seq=20 ttl=64 time=0.990 ms
64 bytes from 192.168.10.1: icmp_seq=21 ttl=64 time=0.742 ms
64 bytes from 192.168.10.1: icmp_seq=22 ttl=64 time=0.966 ms
64 bytes from 192.168.10.1: icmp_seq=23 ttl=64 time=741.282 ms
64 bytes from 192.168.10.1: icmp_seq=24 ttl=64 time=507.794 ms
64 bytes from 192.168.10.1: icmp_seq=25 ttl=64 time=285.503 ms
64 bytes from 192.168.10.1: icmp_seq=26 ttl=64 time=0.831 ms
64 bytes from 192.168.10.1: icmp_seq=27 ttl=64 time=3.398 ms
64 bytes from 192.168.10.1: icmp_seq=28 ttl=64 time=0.843 ms
64 bytes from 192.168.10.1: icmp_seq=29 ttl=64 time=21.699 ms
64 bytes from 192.168.10.1: icmp_seq=30 ttl=64 time=1026.251 ms
64 bytes from 192.168.10.1: icmp_seq=31 ttl=64 time=1341.191 ms
64 bytes from 192.168.10.1: icmp_seq=32 ttl=64 time=517.096 ms
64 bytes from 192.168.10.1: icmp_seq=33 ttl=64 time=11.753 ms
64 bytes from 192.168.10.1: icmp_seq=34 ttl=64 time=3.619 ms
64 bytes from 192.168.10.1: icmp_seq=35 ttl=64 time=79.708 ms
64 bytes from 192.168.10.1: icmp_seq=36 ttl=64 time=44.383 ms
64 bytes from 192.168.10.1: icmp_seq=37 ttl=64 time=113.755 ms
64 bytes from 192.168.10.1: icmp_seq=38 ttl=64 time=762.776 ms
64 bytes from 192.168.10.1: icmp_seq=39 ttl=64 time=766.703 ms
64 bytes from 192.168.10.1: icmp_seq=40 ttl=64 time=173.980 ms
64 bytes from 192.168.10.1: icmp_seq=41 ttl=64 time=0.991 ms

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 7:51 am
by pepek
Great news!

Thank everyone involved in fixing this bug.

However, the job is not done yet:
5GHz upload is great
5GHz download may need some tuning (maybe it's caused by specific client? Can be OK for others...)
2GHz work has to be done - I hope, it has the same cause as 5GHz and applying 5GHz fix to 2GHz module will move us significantly forward - to stability and speeds usable in daily use. 6.43rc6? Then it could be finally deployed to operation.

Mikrotik may also work on their internal communication and communication with customers. This module needs to fix few issues. I hope I will see it in changelog of next RC:)

I'm interested what's source of this problem - how can Mikrotik release and start selling device with totally crappy wireless part (at least for users in this thread:) ) that needs more than month to identify problem. But I can imagine, I will not receive answer for this question.

----------------
Even with these initial pains, hAP ac^2 can be great device for home use.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 9:13 am
by jarda
At least we can have a real hope that mikrotik goes the right way. But the trip will be much longer and we have to wait a bit more before we get current / bugfix version that could be reliably used in production.

Stay tuned for all and go, go, go for mikrotik.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 9:20 am
by vecernik87
yhfung - can you make sure that there is no interference/noise on 2.4GHz band while you do your tests? 2.4GHz is pretty busy and there might be some non-wifi signal in the air.
(I used GrooveA52 for this but many other mikrotik devices with AR92xx / AR93xx should do the job)

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 9:40 am
by yhfung
vecernik87,

For the sake of other interference, I switched off the Siemens DECT phone and hAP ac lite tower, then I carried out ping test for both 2.4GHz and 5GHz with the following results.

Based on the last message from the ping, that is "round-trip min/avg/max/stddev = 0.816/317.053/1611.294/375.575 ms", the average ping time is 317ms, which is not acceptable. We need help from MikroTik to resolve this issue.

For 2.4GHz WiFi, ping time summary
round-trip min/avg/max/stddev = 0.816/317.053/1611.294/375.575 ms

For 5GHz WiFi, ping time summary
round-trip min/avg/max/stddev = 0.859/2.735/30.155/2.013 ms


Listing 1: Ping time for 2.4GHz v6.43r5 firmware
ping -c 300 192.168.55.203
PING 192.168.55.203 (192.168.55.203): 56 data bytes
64 bytes from 192.168.55.203: icmp_seq=0 ttl=63 time=96.247 ms
64 bytes from 192.168.55.203: icmp_seq=1 ttl=63 time=1.067 ms
64 bytes from 192.168.55.203: icmp_seq=2 ttl=63 time=3.650 ms
64 bytes from 192.168.55.203: icmp_seq=3 ttl=63 time=3.075 ms
64 bytes from 192.168.55.203: icmp_seq=4 ttl=63 time=3.652 ms
64 bytes from 192.168.55.203: icmp_seq=5 ttl=63 time=151.065 ms
64 bytes from 192.168.55.203: icmp_seq=6 ttl=63 time=445.050 ms
64 bytes from 192.168.55.203: icmp_seq=7 ttl=63 time=4.143 ms
64 bytes from 192.168.55.203: icmp_seq=8 ttl=63 time=174.244 ms
64 bytes from 192.168.55.203: icmp_seq=9 ttl=63 time=104.137 ms
64 bytes from 192.168.55.203: icmp_seq=10 ttl=63 time=19.646 ms
64 bytes from 192.168.55.203: icmp_seq=11 ttl=63 time=1.331 ms
64 bytes from 192.168.55.203: icmp_seq=12 ttl=63 time=151.537 ms
64 bytes from 192.168.55.203: icmp_seq=13 ttl=63 time=212.131 ms
64 bytes from 192.168.55.203: icmp_seq=14 ttl=63 time=3.586 ms
64 bytes from 192.168.55.203: icmp_seq=15 ttl=63 time=1.174 ms
64 bytes from 192.168.55.203: icmp_seq=16 ttl=63 time=326.089 ms
64 bytes from 192.168.55.203: icmp_seq=17 ttl=63 time=3.544 ms
64 bytes from 192.168.55.203: icmp_seq=18 ttl=63 time=3.643 ms
64 bytes from 192.168.55.203: icmp_seq=19 ttl=63 time=3.633 ms
64 bytes from 192.168.55.203: icmp_seq=20 ttl=63 time=1.303 ms
64 bytes from 192.168.55.203: icmp_seq=21 ttl=63 time=3.969 ms
64 bytes from 192.168.55.203: icmp_seq=22 ttl=63 time=2.658 ms
64 bytes from 192.168.55.203: icmp_seq=23 ttl=63 time=48.002 ms
64 bytes from 192.168.55.203: icmp_seq=24 ttl=63 time=294.170 ms
64 bytes from 192.168.55.203: icmp_seq=25 ttl=63 time=338.832 ms
64 bytes from 192.168.55.203: icmp_seq=26 ttl=63 time=1.075 ms
64 bytes from 192.168.55.203: icmp_seq=27 ttl=63 time=430.825 ms
64 bytes from 192.168.55.203: icmp_seq=28 ttl=63 time=472.157 ms
64 bytes from 192.168.55.203: icmp_seq=29 ttl=63 time=993.887 ms
64 bytes from 192.168.55.203: icmp_seq=30 ttl=63 time=1.032 ms
64 bytes from 192.168.55.203: icmp_seq=31 ttl=63 time=1.176 ms
64 bytes from 192.168.55.203: icmp_seq=32 ttl=63 time=422.510 ms
64 bytes from 192.168.55.203: icmp_seq=33 ttl=63 time=625.386 ms
64 bytes from 192.168.55.203: icmp_seq=34 ttl=63 time=1.063 ms
64 bytes from 192.168.55.203: icmp_seq=35 ttl=63 time=137.421 ms
64 bytes from 192.168.55.203: icmp_seq=36 ttl=63 time=384.461 ms
Request timeout for icmp_seq 37
64 bytes from 192.168.55.203: icmp_seq=37 ttl=63 time=1190.534 ms
64 bytes from 192.168.55.203: icmp_seq=38 ttl=63 time=286.548 ms
64 bytes from 192.168.55.203: icmp_seq=39 ttl=63 time=1.381 ms
64 bytes from 192.168.55.203: icmp_seq=40 ttl=63 time=384.615 ms
64 bytes from 192.168.55.203: icmp_seq=41 ttl=63 time=1.094 ms
64 bytes from 192.168.55.203: icmp_seq=42 ttl=63 time=1.209 ms
64 bytes from 192.168.55.203: icmp_seq=43 ttl=63 time=2.872 ms
64 bytes from 192.168.55.203: icmp_seq=44 ttl=63 time=1.049 ms
64 bytes from 192.168.55.203: icmp_seq=45 ttl=63 time=1.513 ms
64 bytes from 192.168.55.203: icmp_seq=46 ttl=63 time=1.074 ms
64 bytes from 192.168.55.203: icmp_seq=47 ttl=63 time=1.073 ms
64 bytes from 192.168.55.203: icmp_seq=48 ttl=63 time=266.088 ms
64 bytes from 192.168.55.203: icmp_seq=49 ttl=63 time=291.524 ms
64 bytes from 192.168.55.203: icmp_seq=50 ttl=63 time=1.121 ms
64 bytes from 192.168.55.203: icmp_seq=51 ttl=63 time=356.473 ms
64 bytes from 192.168.55.203: icmp_seq=52 ttl=63 time=258.897 ms
64 bytes from 192.168.55.203: icmp_seq=53 ttl=63 time=194.165 ms
64 bytes from 192.168.55.203: icmp_seq=54 ttl=63 time=238.451 ms
64 bytes from 192.168.55.203: icmp_seq=55 ttl=63 time=1151.244 ms
64 bytes from 192.168.55.203: icmp_seq=56 ttl=63 time=256.618 ms
64 bytes from 192.168.55.203: icmp_seq=57 ttl=63 time=142.546 ms
64 bytes from 192.168.55.203: icmp_seq=58 ttl=63 time=1.079 ms
64 bytes from 192.168.55.203: icmp_seq=59 ttl=63 time=3.528 ms
64 bytes from 192.168.55.203: icmp_seq=60 ttl=63 time=1.078 ms
64 bytes from 192.168.55.203: icmp_seq=61 ttl=63 time=117.198 ms
64 bytes from 192.168.55.203: icmp_seq=62 ttl=63 time=53.675 ms
64 bytes from 192.168.55.203: icmp_seq=63 ttl=63 time=7.302 ms
64 bytes from 192.168.55.203: icmp_seq=64 ttl=63 time=3.884 ms
64 bytes from 192.168.55.203: icmp_seq=65 ttl=63 time=3.644 ms
64 bytes from 192.168.55.203: icmp_seq=66 ttl=63 time=4.099 ms
64 bytes from 192.168.55.203: icmp_seq=67 ttl=63 time=414.772 ms
64 bytes from 192.168.55.203: icmp_seq=68 ttl=63 time=1478.748 ms
64 bytes from 192.168.55.203: icmp_seq=69 ttl=63 time=591.285 ms
64 bytes from 192.168.55.203: icmp_seq=70 ttl=63 time=307.697 ms
64 bytes from 192.168.55.203: icmp_seq=71 ttl=63 time=380.752 ms
64 bytes from 192.168.55.203: icmp_seq=72 ttl=63 time=213.814 ms
64 bytes from 192.168.55.203: icmp_seq=73 ttl=63 time=25.544 ms
64 bytes from 192.168.55.203: icmp_seq=74 ttl=63 time=1.097 ms
64 bytes from 192.168.55.203: icmp_seq=75 ttl=63 time=474.385 ms
64 bytes from 192.168.55.203: icmp_seq=76 ttl=63 time=153.936 ms
64 bytes from 192.168.55.203: icmp_seq=77 ttl=63 time=40.726 ms
64 bytes from 192.168.55.203: icmp_seq=78 ttl=63 time=3.693 ms
64 bytes from 192.168.55.203: icmp_seq=79 ttl=63 time=131.466 ms
64 bytes from 192.168.55.203: icmp_seq=80 ttl=63 time=3.674 ms
64 bytes from 192.168.55.203: icmp_seq=81 ttl=63 time=962.174 ms
64 bytes from 192.168.55.203: icmp_seq=82 ttl=63 time=156.894 ms
64 bytes from 192.168.55.203: icmp_seq=83 ttl=63 time=192.328 ms
64 bytes from 192.168.55.203: icmp_seq=84 ttl=63 time=3.748 ms
64 bytes from 192.168.55.203: icmp_seq=85 ttl=63 time=4.247 ms
64 bytes from 192.168.55.203: icmp_seq=86 ttl=63 time=258.409 ms
64 bytes from 192.168.55.203: icmp_seq=87 ttl=63 time=475.438 ms
64 bytes from 192.168.55.203: icmp_seq=88 ttl=63 time=360.733 ms
64 bytes from 192.168.55.203: icmp_seq=89 ttl=63 time=664.606 ms
64 bytes from 192.168.55.203: icmp_seq=90 ttl=63 time=1432.887 ms
64 bytes from 192.168.55.203: icmp_seq=91 ttl=63 time=515.457 ms
64 bytes from 192.168.55.203: icmp_seq=92 ttl=63 time=1014.269 ms
64 bytes from 192.168.55.203: icmp_seq=93 ttl=63 time=965.836 ms
64 bytes from 192.168.55.203: icmp_seq=94 ttl=63 time=182.358 ms
64 bytes from 192.168.55.203: icmp_seq=95 ttl=63 time=3.790 ms
64 bytes from 192.168.55.203: icmp_seq=96 ttl=63 time=461.143 ms
64 bytes from 192.168.55.203: icmp_seq=97 ttl=63 time=339.800 ms
64 bytes from 192.168.55.203: icmp_seq=98 ttl=63 time=1255.572 ms
64 bytes from 192.168.55.203: icmp_seq=99 ttl=63 time=946.232 ms
64 bytes from 192.168.55.203: icmp_seq=100 ttl=63 time=15.853 ms
64 bytes from 192.168.55.203: icmp_seq=101 ttl=63 time=1.034 ms
64 bytes from 192.168.55.203: icmp_seq=102 ttl=63 time=233.805 ms
64 bytes from 192.168.55.203: icmp_seq=103 ttl=63 time=1.076 ms
64 bytes from 192.168.55.203: icmp_seq=104 ttl=63 time=136.322 ms
64 bytes from 192.168.55.203: icmp_seq=105 ttl=63 time=1.778 ms
64 bytes from 192.168.55.203: icmp_seq=106 ttl=63 time=1.065 ms
64 bytes from 192.168.55.203: icmp_seq=107 ttl=63 time=1.070 ms
64 bytes from 192.168.55.203: icmp_seq=108 ttl=63 time=184.751 ms
64 bytes from 192.168.55.203: icmp_seq=109 ttl=63 time=1.504 ms
64 bytes from 192.168.55.203: icmp_seq=110 ttl=63 time=419.626 ms
64 bytes from 192.168.55.203: icmp_seq=111 ttl=63 time=161.871 ms
64 bytes from 192.168.55.203: icmp_seq=112 ttl=63 time=355.883 ms
64 bytes from 192.168.55.203: icmp_seq=113 ttl=63 time=35.677 ms
64 bytes from 192.168.55.203: icmp_seq=114 ttl=63 time=208.910 ms
64 bytes from 192.168.55.203: icmp_seq=115 ttl=63 time=3.655 ms
64 bytes from 192.168.55.203: icmp_seq=116 ttl=63 time=1.067 ms
64 bytes from 192.168.55.203: icmp_seq=117 ttl=63 time=1.077 ms
64 bytes from 192.168.55.203: icmp_seq=118 ttl=63 time=1.184 ms
64 bytes from 192.168.55.203: icmp_seq=119 ttl=63 time=3.571 ms
64 bytes from 192.168.55.203: icmp_seq=120 ttl=63 time=195.255 ms
64 bytes from 192.168.55.203: icmp_seq=121 ttl=63 time=3.572 ms
64 bytes from 192.168.55.203: icmp_seq=122 ttl=63 time=3.738 ms
64 bytes from 192.168.55.203: icmp_seq=123 ttl=63 time=104.366 ms
64 bytes from 192.168.55.203: icmp_seq=124 ttl=63 time=1.038 ms
64 bytes from 192.168.55.203: icmp_seq=125 ttl=63 time=1.040 ms
64 bytes from 192.168.55.203: icmp_seq=126 ttl=63 time=6.040 ms
64 bytes from 192.168.55.203: icmp_seq=127 ttl=63 time=3.654 ms
64 bytes from 192.168.55.203: icmp_seq=128 ttl=63 time=160.323 ms
64 bytes from 192.168.55.203: icmp_seq=129 ttl=63 time=232.272 ms
64 bytes from 192.168.55.203: icmp_seq=130 ttl=63 time=3.690 ms
64 bytes from 192.168.55.203: icmp_seq=131 ttl=63 time=3.549 ms
64 bytes from 192.168.55.203: icmp_seq=132 ttl=63 time=1.060 ms
64 bytes from 192.168.55.203: icmp_seq=133 ttl=63 time=356.000 ms
64 bytes from 192.168.55.203: icmp_seq=134 ttl=63 time=200.476 ms
64 bytes from 192.168.55.203: icmp_seq=135 ttl=63 time=3.580 ms
64 bytes from 192.168.55.203: icmp_seq=136 ttl=63 time=78.580 ms
64 bytes from 192.168.55.203: icmp_seq=137 ttl=63 time=1179.404 ms
64 bytes from 192.168.55.203: icmp_seq=138 ttl=63 time=247.567 ms
64 bytes from 192.168.55.203: icmp_seq=139 ttl=63 time=136.379 ms
64 bytes from 192.168.55.203: icmp_seq=140 ttl=63 time=610.184 ms
64 bytes from 192.168.55.203: icmp_seq=141 ttl=63 time=111.924 ms
64 bytes from 192.168.55.203: icmp_seq=142 ttl=63 time=4.351 ms
64 bytes from 192.168.55.203: icmp_seq=143 ttl=63 time=4.099 ms
64 bytes from 192.168.55.203: icmp_seq=144 ttl=63 time=3.637 ms
64 bytes from 192.168.55.203: icmp_seq=145 ttl=63 time=3.683 ms
64 bytes from 192.168.55.203: icmp_seq=146 ttl=63 time=584.105 ms
64 bytes from 192.168.55.203: icmp_seq=147 ttl=63 time=482.505 ms
64 bytes from 192.168.55.203: icmp_seq=148 ttl=63 time=1158.798 ms
64 bytes from 192.168.55.203: icmp_seq=149 ttl=63 time=237.410 ms
64 bytes from 192.168.55.203: icmp_seq=150 ttl=63 time=146.037 ms
64 bytes from 192.168.55.203: icmp_seq=151 ttl=63 time=301.588 ms
64 bytes from 192.168.55.203: icmp_seq=152 ttl=63 time=1.306 ms
64 bytes from 192.168.55.203: icmp_seq=153 ttl=63 time=153.659 ms
64 bytes from 192.168.55.203: icmp_seq=154 ttl=63 time=1.466 ms
64 bytes from 192.168.55.203: icmp_seq=155 ttl=63 time=3.621 ms
64 bytes from 192.168.55.203: icmp_seq=156 ttl=63 time=1.239 ms
64 bytes from 192.168.55.203: icmp_seq=157 ttl=63 time=171.609 ms
64 bytes from 192.168.55.203: icmp_seq=158 ttl=63 time=390.688 ms
64 bytes from 192.168.55.203: icmp_seq=159 ttl=63 time=4.856 ms
64 bytes from 192.168.55.203: icmp_seq=160 ttl=63 time=422.667 ms
64 bytes from 192.168.55.203: icmp_seq=161 ttl=63 time=4.200 ms
64 bytes from 192.168.55.203: icmp_seq=162 ttl=63 time=382.492 ms
64 bytes from 192.168.55.203: icmp_seq=163 ttl=63 time=1115.018 ms
64 bytes from 192.168.55.203: icmp_seq=164 ttl=63 time=306.815 ms
64 bytes from 192.168.55.203: icmp_seq=165 ttl=63 time=1611.294 ms
64 bytes from 192.168.55.203: icmp_seq=166 ttl=63 time=721.117 ms
64 bytes from 192.168.55.203: icmp_seq=167 ttl=63 time=1602.184 ms
64 bytes from 192.168.55.203: icmp_seq=168 ttl=63 time=746.899 ms
64 bytes from 192.168.55.203: icmp_seq=169 ttl=63 time=803.824 ms
64 bytes from 192.168.55.203: icmp_seq=170 ttl=63 time=1105.891 ms
64 bytes from 192.168.55.203: icmp_seq=171 ttl=63 time=203.136 ms
64 bytes from 192.168.55.203: icmp_seq=172 ttl=63 time=965.402 ms
64 bytes from 192.168.55.203: icmp_seq=173 ttl=63 time=408.061 ms
64 bytes from 192.168.55.203: icmp_seq=174 ttl=63 time=293.413 ms
64 bytes from 192.168.55.203: icmp_seq=175 ttl=63 time=710.741 ms
64 bytes from 192.168.55.203: icmp_seq=176 ttl=63 time=988.288 ms
64 bytes from 192.168.55.203: icmp_seq=177 ttl=63 time=548.190 ms
64 bytes from 192.168.55.203: icmp_seq=178 ttl=63 time=1145.470 ms
64 bytes from 192.168.55.203: icmp_seq=179 ttl=63 time=285.680 ms
64 bytes from 192.168.55.203: icmp_seq=180 ttl=63 time=621.050 ms
64 bytes from 192.168.55.203: icmp_seq=181 ttl=63 time=450.339 ms
64 bytes from 192.168.55.203: icmp_seq=182 ttl=63 time=600.265 ms
64 bytes from 192.168.55.203: icmp_seq=183 ttl=63 time=154.855 ms
64 bytes from 192.168.55.203: icmp_seq=184 ttl=63 time=1.148 ms
64 bytes from 192.168.55.203: icmp_seq=185 ttl=63 time=1.227 ms
64 bytes from 192.168.55.203: icmp_seq=186 ttl=63 time=0.816 ms
64 bytes from 192.168.55.203: icmp_seq=187 ttl=63 time=1.139 ms
64 bytes from 192.168.55.203: icmp_seq=188 ttl=63 time=525.529 ms
64 bytes from 192.168.55.203: icmp_seq=189 ttl=63 time=415.439 ms
64 bytes from 192.168.55.203: icmp_seq=190 ttl=63 time=1123.966 ms
64 bytes from 192.168.55.203: icmp_seq=191 ttl=63 time=225.665 ms
64 bytes from 192.168.55.203: icmp_seq=192 ttl=63 time=1288.864 ms
64 bytes from 192.168.55.203: icmp_seq=193 ttl=63 time=365.940 ms
64 bytes from 192.168.55.203: icmp_seq=194 ttl=63 time=1309.261 ms
64 bytes from 192.168.55.203: icmp_seq=195 ttl=63 time=403.919 ms
64 bytes from 192.168.55.203: icmp_seq=196 ttl=63 time=1306.664 ms
64 bytes from 192.168.55.203: icmp_seq=197 ttl=63 time=365.513 ms
64 bytes from 192.168.55.203: icmp_seq=198 ttl=63 time=681.875 ms
64 bytes from 192.168.55.203: icmp_seq=199 ttl=63 time=591.075 ms
64 bytes from 192.168.55.203: icmp_seq=200 ttl=63 time=3.722 ms
64 bytes from 192.168.55.203: icmp_seq=201 ttl=63 time=1098.663 ms
64 bytes from 192.168.55.203: icmp_seq=202 ttl=63 time=196.683 ms
64 bytes from 192.168.55.203: icmp_seq=203 ttl=63 time=541.968 ms
64 bytes from 192.168.55.203: icmp_seq=204 ttl=63 time=589.573 ms
64 bytes from 192.168.55.203: icmp_seq=205 ttl=63 time=496.090 ms
64 bytes from 192.168.55.203: icmp_seq=206 ttl=63 time=287.142 ms
64 bytes from 192.168.55.203: icmp_seq=207 ttl=63 time=846.839 ms
64 bytes from 192.168.55.203: icmp_seq=208 ttl=63 time=913.778 ms
64 bytes from 192.168.55.203: icmp_seq=209 ttl=63 time=635.220 ms
64 bytes from 192.168.55.203: icmp_seq=210 ttl=63 time=1060.553 ms
64 bytes from 192.168.55.203: icmp_seq=211 ttl=63 time=146.878 ms
64 bytes from 192.168.55.203: icmp_seq=212 ttl=63 time=796.115 ms
64 bytes from 192.168.55.203: icmp_seq=213 ttl=63 time=250.030 ms
64 bytes from 192.168.55.203: icmp_seq=214 ttl=63 time=652.522 ms
64 bytes from 192.168.55.203: icmp_seq=215 ttl=63 time=130.391 ms
64 bytes from 192.168.55.203: icmp_seq=216 ttl=63 time=3.881 ms
64 bytes from 192.168.55.203: icmp_seq=217 ttl=63 time=179.271 ms
64 bytes from 192.168.55.203: icmp_seq=218 ttl=63 time=674.531 ms
64 bytes from 192.168.55.203: icmp_seq=219 ttl=63 time=3.584 ms
64 bytes from 192.168.55.203: icmp_seq=220 ttl=63 time=3.562 ms
64 bytes from 192.168.55.203: icmp_seq=221 ttl=63 time=174.271 ms
64 bytes from 192.168.55.203: icmp_seq=222 ttl=63 time=3.935 ms
64 bytes from 192.168.55.203: icmp_seq=223 ttl=63 time=1.117 ms
64 bytes from 192.168.55.203: icmp_seq=224 ttl=63 time=74.062 ms
64 bytes from 192.168.55.203: icmp_seq=225 ttl=63 time=762.720 ms
64 bytes from 192.168.55.203: icmp_seq=226 ttl=63 time=653.550 ms
64 bytes from 192.168.55.203: icmp_seq=227 ttl=63 time=913.540 ms
64 bytes from 192.168.55.203: icmp_seq=228 ttl=63 time=1.118 ms
64 bytes from 192.168.55.203: icmp_seq=229 ttl=63 time=712.787 ms
64 bytes from 192.168.55.203: icmp_seq=230 ttl=63 time=3.627 ms
64 bytes from 192.168.55.203: icmp_seq=231 ttl=63 time=3.608 ms
64 bytes from 192.168.55.203: icmp_seq=232 ttl=63 time=196.848 ms
64 bytes from 192.168.55.203: icmp_seq=233 ttl=63 time=22.340 ms
64 bytes from 192.168.55.203: icmp_seq=234 ttl=63 time=3.740 ms
64 bytes from 192.168.55.203: icmp_seq=235 ttl=63 time=537.470 ms
64 bytes from 192.168.55.203: icmp_seq=236 ttl=63 time=3.670 ms
64 bytes from 192.168.55.203: icmp_seq=237 ttl=63 time=1.638 ms
64 bytes from 192.168.55.203: icmp_seq=238 ttl=63 time=1332.584 ms
64 bytes from 192.168.55.203: icmp_seq=239 ttl=63 time=327.713 ms
64 bytes from 192.168.55.203: icmp_seq=240 ttl=63 time=1229.999 ms
64 bytes from 192.168.55.203: icmp_seq=241 ttl=63 time=351.176 ms
64 bytes from 192.168.55.203: icmp_seq=242 ttl=63 time=1038.555 ms
64 bytes from 192.168.55.203: icmp_seq=243 ttl=63 time=125.065 ms
64 bytes from 192.168.55.203: icmp_seq=244 ttl=63 time=876.548 ms
64 bytes from 192.168.55.203: icmp_seq=245 ttl=63 time=393.577 ms
64 bytes from 192.168.55.203: icmp_seq=246 ttl=63 time=3.624 ms
64 bytes from 192.168.55.203: icmp_seq=247 ttl=63 time=42.092 ms
64 bytes from 192.168.55.203: icmp_seq=248 ttl=63 time=4.031 ms
64 bytes from 192.168.55.203: icmp_seq=249 ttl=63 time=476.145 ms
64 bytes from 192.168.55.203: icmp_seq=250 ttl=63 time=3.705 ms
64 bytes from 192.168.55.203: icmp_seq=251 ttl=63 time=541.663 ms
64 bytes from 192.168.55.203: icmp_seq=252 ttl=63 time=909.653 ms
64 bytes from 192.168.55.203: icmp_seq=253 ttl=63 time=564.181 ms
64 bytes from 192.168.55.203: icmp_seq=254 ttl=63 time=3.656 ms
64 bytes from 192.168.55.203: icmp_seq=255 ttl=63 time=474.987 ms
64 bytes from 192.168.55.203: icmp_seq=256 ttl=63 time=39.288 ms
64 bytes from 192.168.55.203: icmp_seq=257 ttl=63 time=824.183 ms
64 bytes from 192.168.55.203: icmp_seq=258 ttl=63 time=976.184 ms
64 bytes from 192.168.55.203: icmp_seq=259 ttl=63 time=521.470 ms
64 bytes from 192.168.55.203: icmp_seq=260 ttl=63 time=1286.070 ms
64 bytes from 192.168.55.203: icmp_seq=261 ttl=63 time=407.095 ms
64 bytes from 192.168.55.203: icmp_seq=262 ttl=63 time=507.786 ms
64 bytes from 192.168.55.203: icmp_seq=263 ttl=63 time=142.566 ms
64 bytes from 192.168.55.203: icmp_seq=264 ttl=63 time=399.458 ms
64 bytes from 192.168.55.203: icmp_seq=265 ttl=63 time=363.096 ms
64 bytes from 192.168.55.203: icmp_seq=266 ttl=63 time=620.044 ms
64 bytes from 192.168.55.203: icmp_seq=267 ttl=63 time=3.572 ms
64 bytes from 192.168.55.203: icmp_seq=268 ttl=63 time=120.653 ms
64 bytes from 192.168.55.203: icmp_seq=269 ttl=63 time=867.108 ms
64 bytes from 192.168.55.203: icmp_seq=270 ttl=63 time=699.333 ms
64 bytes from 192.168.55.203: icmp_seq=271 ttl=63 time=5.343 ms
64 bytes from 192.168.55.203: icmp_seq=272 ttl=63 time=3.620 ms
64 bytes from 192.168.55.203: icmp_seq=273 ttl=63 time=6.269 ms
64 bytes from 192.168.55.203: icmp_seq=274 ttl=63 time=325.170 ms
64 bytes from 192.168.55.203: icmp_seq=275 ttl=63 time=414.943 ms
64 bytes from 192.168.55.203: icmp_seq=276 ttl=63 time=90.855 ms
64 bytes from 192.168.55.203: icmp_seq=277 ttl=63 time=461.520 ms
64 bytes from 192.168.55.203: icmp_seq=278 ttl=63 time=4.061 ms
64 bytes from 192.168.55.203: icmp_seq=279 ttl=63 time=434.481 ms
64 bytes from 192.168.55.203: icmp_seq=281 ttl=63 time=66.685 ms
64 bytes from 192.168.55.203: icmp_seq=282 ttl=63 time=384.979 ms
64 bytes from 192.168.55.203: icmp_seq=283 ttl=63 time=3.619 ms
64 bytes from 192.168.55.203: icmp_seq=284 ttl=63 time=86.190 ms
64 bytes from 192.168.55.203: icmp_seq=285 ttl=63 time=3.686 ms
64 bytes from 192.168.55.203: icmp_seq=286 ttl=63 time=954.569 ms
64 bytes from 192.168.55.203: icmp_seq=287 ttl=63 time=3.615 ms
64 bytes from 192.168.55.203: icmp_seq=288 ttl=63 time=54.245 ms
64 bytes from 192.168.55.203: icmp_seq=289 ttl=63 time=425.645 ms
64 bytes from 192.168.55.203: icmp_seq=290 ttl=63 time=3.660 ms
64 bytes from 192.168.55.203: icmp_seq=291 ttl=63 time=3.564 ms
64 bytes from 192.168.55.203: icmp_seq=292 ttl=63 time=451.816 ms
64 bytes from 192.168.55.203: icmp_seq=293 ttl=63 time=3.775 ms
64 bytes from 192.168.55.203: icmp_seq=294 ttl=63 time=161.888 ms
64 bytes from 192.168.55.203: icmp_seq=295 ttl=63 time=70.334 ms
64 bytes from 192.168.55.203: icmp_seq=296 ttl=63 time=135.991 ms
64 bytes from 192.168.55.203: icmp_seq=297 ttl=63 time=425.154 ms
64 bytes from 192.168.55.203: icmp_seq=298 ttl=63 time=3.696 ms
64 bytes from 192.168.55.203: icmp_seq=299 ttl=63 time=361.330 ms

--- 192.168.55.203 ping statistics ---
300 packets transmitted, 299 packets received, 0.3% packet loss
round-trip min/avg/max/stddev = 0.816/317.053/1611.294/375.575 ms
#

Listing 2: 5GHz ping time with average ping time = 2.74ms
ping -c 300 192.168.55.203
PING 192.168.55.203 (192.168.55.203): 56 data bytes
64 bytes from 192.168.55.203: icmp_seq=0 ttl=63 time=3.756 ms
64 bytes from 192.168.55.203: icmp_seq=1 ttl=63 time=4.140 ms
64 bytes from 192.168.55.203: icmp_seq=2 ttl=63 time=0.926 ms
64 bytes from 192.168.55.203: icmp_seq=3 ttl=63 time=3.352 ms
64 bytes from 192.168.55.203: icmp_seq=4 ttl=63 time=3.481 ms
64 bytes from 192.168.55.203: icmp_seq=5 ttl=63 time=0.861 ms
64 bytes from 192.168.55.203: icmp_seq=6 ttl=63 time=0.983 ms
64 bytes from 192.168.55.203: icmp_seq=7 ttl=63 time=3.527 ms
64 bytes from 192.168.55.203: icmp_seq=8 ttl=63 time=3.190 ms
64 bytes from 192.168.55.203: icmp_seq=9 ttl=63 time=3.581 ms
64 bytes from 192.168.55.203: icmp_seq=10 ttl=63 time=3.563 ms
64 bytes from 192.168.55.203: icmp_seq=11 ttl=63 time=3.985 ms
64 bytes from 192.168.55.203: icmp_seq=12 ttl=63 time=30.155 ms
64 bytes from 192.168.55.203: icmp_seq=13 ttl=63 time=1.026 ms
64 bytes from 192.168.55.203: icmp_seq=14 ttl=63 time=1.130 ms
64 bytes from 192.168.55.203: icmp_seq=15 ttl=63 time=4.504 ms
64 bytes from 192.168.55.203: icmp_seq=16 ttl=63 time=1.187 ms
64 bytes from 192.168.55.203: icmp_seq=17 ttl=63 time=1.228 ms
64 bytes from 192.168.55.203: icmp_seq=18 ttl=63 time=3.571 ms
64 bytes from 192.168.55.203: icmp_seq=19 ttl=63 time=3.517 ms
64 bytes from 192.168.55.203: icmp_seq=20 ttl=63 time=1.189 ms
64 bytes from 192.168.55.203: icmp_seq=21 ttl=63 time=3.648 ms
64 bytes from 192.168.55.203: icmp_seq=22 ttl=63 time=1.111 ms
64 bytes from 192.168.55.203: icmp_seq=23 ttl=63 time=3.613 ms
64 bytes from 192.168.55.203: icmp_seq=24 ttl=63 time=3.731 ms
64 bytes from 192.168.55.203: icmp_seq=25 ttl=63 time=1.140 ms
64 bytes from 192.168.55.203: icmp_seq=26 ttl=63 time=1.091 ms
64 bytes from 192.168.55.203: icmp_seq=27 ttl=63 time=2.069 ms
64 bytes from 192.168.55.203: icmp_seq=28 ttl=63 time=1.043 ms
64 bytes from 192.168.55.203: icmp_seq=29 ttl=63 time=1.032 ms
64 bytes from 192.168.55.203: icmp_seq=30 ttl=63 time=1.403 ms
64 bytes from 192.168.55.203: icmp_seq=31 ttl=63 time=1.053 ms
64 bytes from 192.168.55.203: icmp_seq=32 ttl=63 time=3.655 ms
64 bytes from 192.168.55.203: icmp_seq=33 ttl=63 time=1.136 ms
64 bytes from 192.168.55.203: icmp_seq=34 ttl=63 time=3.772 ms
64 bytes from 192.168.55.203: icmp_seq=35 ttl=63 time=3.553 ms
64 bytes from 192.168.55.203: icmp_seq=36 ttl=63 time=3.467 ms
64 bytes from 192.168.55.203: icmp_seq=37 ttl=63 time=3.671 ms
64 bytes from 192.168.55.203: icmp_seq=38 ttl=63 time=3.630 ms
64 bytes from 192.168.55.203: icmp_seq=39 ttl=63 time=3.737 ms
64 bytes from 192.168.55.203: icmp_seq=40 ttl=63 time=3.490 ms
64 bytes from 192.168.55.203: icmp_seq=41 ttl=63 time=3.601 ms
64 bytes from 192.168.55.203: icmp_seq=42 ttl=63 time=4.075 ms
64 bytes from 192.168.55.203: icmp_seq=43 ttl=63 time=1.106 ms
64 bytes from 192.168.55.203: icmp_seq=44 ttl=63 time=3.670 ms
64 bytes from 192.168.55.203: icmp_seq=45 ttl=63 time=3.636 ms
64 bytes from 192.168.55.203: icmp_seq=46 ttl=63 time=3.697 ms
64 bytes from 192.168.55.203: icmp_seq=47 ttl=63 time=3.524 ms
64 bytes from 192.168.55.203: icmp_seq=48 ttl=63 time=3.598 ms
64 bytes from 192.168.55.203: icmp_seq=49 ttl=63 time=1.138 ms
64 bytes from 192.168.55.203: icmp_seq=50 ttl=63 time=3.611 ms
64 bytes from 192.168.55.203: icmp_seq=51 ttl=63 time=1.945 ms
64 bytes from 192.168.55.203: icmp_seq=52 ttl=63 time=1.087 ms
64 bytes from 192.168.55.203: icmp_seq=53 ttl=63 time=0.924 ms
64 bytes from 192.168.55.203: icmp_seq=54 ttl=63 time=1.233 ms
64 bytes from 192.168.55.203: icmp_seq=55 ttl=63 time=1.543 ms
64 bytes from 192.168.55.203: icmp_seq=56 ttl=63 time=1.055 ms
64 bytes from 192.168.55.203: icmp_seq=57 ttl=63 time=3.645 ms
64 bytes from 192.168.55.203: icmp_seq=58 ttl=63 time=0.859 ms
64 bytes from 192.168.55.203: icmp_seq=59 ttl=63 time=3.413 ms
64 bytes from 192.168.55.203: icmp_seq=60 ttl=63 time=3.638 ms
64 bytes from 192.168.55.203: icmp_seq=61 ttl=63 time=1.028 ms
64 bytes from 192.168.55.203: icmp_seq=62 ttl=63 time=0.986 ms
64 bytes from 192.168.55.203: icmp_seq=63 ttl=63 time=3.646 ms
64 bytes from 192.168.55.203: icmp_seq=64 ttl=63 time=1.067 ms
64 bytes from 192.168.55.203: icmp_seq=65 ttl=63 time=0.966 ms
64 bytes from 192.168.55.203: icmp_seq=66 ttl=63 time=0.945 ms
64 bytes from 192.168.55.203: icmp_seq=67 ttl=63 time=1.026 ms
64 bytes from 192.168.55.203: icmp_seq=68 ttl=63 time=1.051 ms
64 bytes from 192.168.55.203: icmp_seq=69 ttl=63 time=1.092 ms
64 bytes from 192.168.55.203: icmp_seq=70 ttl=63 time=1.813 ms
64 bytes from 192.168.55.203: icmp_seq=71 ttl=63 time=1.142 ms
64 bytes from 192.168.55.203: icmp_seq=72 ttl=63 time=1.150 ms
64 bytes from 192.168.55.203: icmp_seq=73 ttl=63 time=1.267 ms
64 bytes from 192.168.55.203: icmp_seq=74 ttl=63 time=1.202 ms
64 bytes from 192.168.55.203: icmp_seq=75 ttl=63 time=1.095 ms
64 bytes from 192.168.55.203: icmp_seq=76 ttl=63 time=1.088 ms
64 bytes from 192.168.55.203: icmp_seq=77 ttl=63 time=1.769 ms
64 bytes from 192.168.55.203: icmp_seq=78 ttl=63 time=1.109 ms
64 bytes from 192.168.55.203: icmp_seq=79 ttl=63 time=1.049 ms
64 bytes from 192.168.55.203: icmp_seq=80 ttl=63 time=1.062 ms
64 bytes from 192.168.55.203: icmp_seq=81 ttl=63 time=1.054 ms
64 bytes from 192.168.55.203: icmp_seq=82 ttl=63 time=3.740 ms
64 bytes from 192.168.55.203: icmp_seq=83 ttl=63 time=4.763 ms
64 bytes from 192.168.55.203: icmp_seq=84 ttl=63 time=3.596 ms
64 bytes from 192.168.55.203: icmp_seq=85 ttl=63 time=3.774 ms
64 bytes from 192.168.55.203: icmp_seq=86 ttl=63 time=3.662 ms
64 bytes from 192.168.55.203: icmp_seq=87 ttl=63 time=1.198 ms
64 bytes from 192.168.55.203: icmp_seq=88 ttl=63 time=0.948 ms
64 bytes from 192.168.55.203: icmp_seq=89 ttl=63 time=0.962 ms
64 bytes from 192.168.55.203: icmp_seq=90 ttl=63 time=3.466 ms
64 bytes from 192.168.55.203: icmp_seq=91 ttl=63 time=0.940 ms
64 bytes from 192.168.55.203: icmp_seq=92 ttl=63 time=0.962 ms
64 bytes from 192.168.55.203: icmp_seq=93 ttl=63 time=0.999 ms
64 bytes from 192.168.55.203: icmp_seq=94 ttl=63 time=3.567 ms
64 bytes from 192.168.55.203: icmp_seq=95 ttl=63 time=3.496 ms
64 bytes from 192.168.55.203: icmp_seq=96 ttl=63 time=3.768 ms
64 bytes from 192.168.55.203: icmp_seq=97 ttl=63 time=1.273 ms
64 bytes from 192.168.55.203: icmp_seq=98 ttl=63 time=3.626 ms
64 bytes from 192.168.55.203: icmp_seq=99 ttl=63 time=3.586 ms
64 bytes from 192.168.55.203: icmp_seq=100 ttl=63 time=3.641 ms
64 bytes from 192.168.55.203: icmp_seq=101 ttl=63 time=3.542 ms
64 bytes from 192.168.55.203: icmp_seq=102 ttl=63 time=1.324 ms
64 bytes from 192.168.55.203: icmp_seq=103 ttl=63 time=1.186 ms
64 bytes from 192.168.55.203: icmp_seq=104 ttl=63 time=1.109 ms
64 bytes from 192.168.55.203: icmp_seq=105 ttl=63 time=3.798 ms
64 bytes from 192.168.55.203: icmp_seq=106 ttl=63 time=3.612 ms
64 bytes from 192.168.55.203: icmp_seq=107 ttl=63 time=1.395 ms
64 bytes from 192.168.55.203: icmp_seq=108 ttl=63 time=3.641 ms
64 bytes from 192.168.55.203: icmp_seq=109 ttl=63 time=3.718 ms
64 bytes from 192.168.55.203: icmp_seq=110 ttl=63 time=3.696 ms
64 bytes from 192.168.55.203: icmp_seq=111 ttl=63 time=3.558 ms
64 bytes from 192.168.55.203: icmp_seq=112 ttl=63 time=3.643 ms
64 bytes from 192.168.55.203: icmp_seq=113 ttl=63 time=2.412 ms
64 bytes from 192.168.55.203: icmp_seq=114 ttl=63 time=3.671 ms
64 bytes from 192.168.55.203: icmp_seq=115 ttl=63 time=3.772 ms
64 bytes from 192.168.55.203: icmp_seq=116 ttl=63 time=3.759 ms
64 bytes from 192.168.55.203: icmp_seq=117 ttl=63 time=3.718 ms
64 bytes from 192.168.55.203: icmp_seq=118 ttl=63 time=3.640 ms
64 bytes from 192.168.55.203: icmp_seq=119 ttl=63 time=3.725 ms
64 bytes from 192.168.55.203: icmp_seq=120 ttl=63 time=3.679 ms
64 bytes from 192.168.55.203: icmp_seq=121 ttl=63 time=1.244 ms
64 bytes from 192.168.55.203: icmp_seq=122 ttl=63 time=3.776 ms
64 bytes from 192.168.55.203: icmp_seq=123 ttl=63 time=3.865 ms
64 bytes from 192.168.55.203: icmp_seq=124 ttl=63 time=3.728 ms
64 bytes from 192.168.55.203: icmp_seq=125 ttl=63 time=3.676 ms
64 bytes from 192.168.55.203: icmp_seq=126 ttl=63 time=1.369 ms
64 bytes from 192.168.55.203: icmp_seq=127 ttl=63 time=3.694 ms
64 bytes from 192.168.55.203: icmp_seq=128 ttl=63 time=3.683 ms
64 bytes from 192.168.55.203: icmp_seq=129 ttl=63 time=3.673 ms
64 bytes from 192.168.55.203: icmp_seq=130 ttl=63 time=3.755 ms
64 bytes from 192.168.55.203: icmp_seq=131 ttl=63 time=1.275 ms
64 bytes from 192.168.55.203: icmp_seq=132 ttl=63 time=3.673 ms
64 bytes from 192.168.55.203: icmp_seq=133 ttl=63 time=3.673 ms
64 bytes from 192.168.55.203: icmp_seq=134 ttl=63 time=3.670 ms
64 bytes from 192.168.55.203: icmp_seq=135 ttl=63 time=1.093 ms
64 bytes from 192.168.55.203: icmp_seq=136 ttl=63 time=1.148 ms
64 bytes from 192.168.55.203: icmp_seq=137 ttl=63 time=3.352 ms
64 bytes from 192.168.55.203: icmp_seq=138 ttl=63 time=1.132 ms
64 bytes from 192.168.55.203: icmp_seq=139 ttl=63 time=1.117 ms
64 bytes from 192.168.55.203: icmp_seq=140 ttl=63 time=1.125 ms
64 bytes from 192.168.55.203: icmp_seq=141 ttl=63 time=3.851 ms
64 bytes from 192.168.55.203: icmp_seq=142 ttl=63 time=1.139 ms
64 bytes from 192.168.55.203: icmp_seq=143 ttl=63 time=3.725 ms
64 bytes from 192.168.55.203: icmp_seq=144 ttl=63 time=3.695 ms
64 bytes from 192.168.55.203: icmp_seq=145 ttl=63 time=3.557 ms
64 bytes from 192.168.55.203: icmp_seq=146 ttl=63 time=1.990 ms
64 bytes from 192.168.55.203: icmp_seq=147 ttl=63 time=3.321 ms
64 bytes from 192.168.55.203: icmp_seq=148 ttl=63 time=4.425 ms
64 bytes from 192.168.55.203: icmp_seq=149 ttl=63 time=1.147 ms
64 bytes from 192.168.55.203: icmp_seq=150 ttl=63 time=3.656 ms
64 bytes from 192.168.55.203: icmp_seq=151 ttl=63 time=3.887 ms
64 bytes from 192.168.55.203: icmp_seq=152 ttl=63 time=3.705 ms
64 bytes from 192.168.55.203: icmp_seq=153 ttl=63 time=3.664 ms
64 bytes from 192.168.55.203: icmp_seq=154 ttl=63 time=1.183 ms
64 bytes from 192.168.55.203: icmp_seq=155 ttl=63 time=3.554 ms
64 bytes from 192.168.55.203: icmp_seq=156 ttl=63 time=1.093 ms
64 bytes from 192.168.55.203: icmp_seq=157 ttl=63 time=3.815 ms
64 bytes from 192.168.55.203: icmp_seq=158 ttl=63 time=3.673 ms
64 bytes from 192.168.55.203: icmp_seq=159 ttl=63 time=1.251 ms
64 bytes from 192.168.55.203: icmp_seq=160 ttl=63 time=3.698 ms
64 bytes from 192.168.55.203: icmp_seq=161 ttl=63 time=3.751 ms
64 bytes from 192.168.55.203: icmp_seq=162 ttl=63 time=4.069 ms
64 bytes from 192.168.55.203: icmp_seq=163 ttl=63 time=3.609 ms
64 bytes from 192.168.55.203: icmp_seq=164 ttl=63 time=3.714 ms
64 bytes from 192.168.55.203: icmp_seq=165 ttl=63 time=3.546 ms
64 bytes from 192.168.55.203: icmp_seq=166 ttl=63 time=3.647 ms
64 bytes from 192.168.55.203: icmp_seq=167 ttl=63 time=3.679 ms
64 bytes from 192.168.55.203: icmp_seq=168 ttl=63 time=3.767 ms
64 bytes from 192.168.55.203: icmp_seq=169 ttl=63 time=1.221 ms
64 bytes from 192.168.55.203: icmp_seq=170 ttl=63 time=1.130 ms
64 bytes from 192.168.55.203: icmp_seq=171 ttl=63 time=4.006 ms
64 bytes from 192.168.55.203: icmp_seq=172 ttl=63 time=3.715 ms
64 bytes from 192.168.55.203: icmp_seq=173 ttl=63 time=3.691 ms
64 bytes from 192.168.55.203: icmp_seq=174 ttl=63 time=1.306 ms
64 bytes from 192.168.55.203: icmp_seq=175 ttl=63 time=2.189 ms
64 bytes from 192.168.55.203: icmp_seq=176 ttl=63 time=3.693 ms
64 bytes from 192.168.55.203: icmp_seq=177 ttl=63 time=3.771 ms
64 bytes from 192.168.55.203: icmp_seq=178 ttl=63 time=1.210 ms
64 bytes from 192.168.55.203: icmp_seq=179 ttl=63 time=3.783 ms
64 bytes from 192.168.55.203: icmp_seq=180 ttl=63 time=1.076 ms
64 bytes from 192.168.55.203: icmp_seq=181 ttl=63 time=1.088 ms
64 bytes from 192.168.55.203: icmp_seq=182 ttl=63 time=1.119 ms
64 bytes from 192.168.55.203: icmp_seq=183 ttl=63 time=1.088 ms
64 bytes from 192.168.55.203: icmp_seq=184 ttl=63 time=1.099 ms
64 bytes from 192.168.55.203: icmp_seq=185 ttl=63 time=1.405 ms
64 bytes from 192.168.55.203: icmp_seq=186 ttl=63 time=1.125 ms
64 bytes from 192.168.55.203: icmp_seq=187 ttl=63 time=1.031 ms
64 bytes from 192.168.55.203: icmp_seq=188 ttl=63 time=1.180 ms
64 bytes from 192.168.55.203: icmp_seq=189 ttl=63 time=3.941 ms
64 bytes from 192.168.55.203: icmp_seq=190 ttl=63 time=3.722 ms
64 bytes from 192.168.55.203: icmp_seq=191 ttl=63 time=1.088 ms
64 bytes from 192.168.55.203: icmp_seq=192 ttl=63 time=3.683 ms
64 bytes from 192.168.55.203: icmp_seq=193 ttl=63 time=1.539 ms
64 bytes from 192.168.55.203: icmp_seq=194 ttl=63 time=3.711 ms
64 bytes from 192.168.55.203: icmp_seq=195 ttl=63 time=3.751 ms
64 bytes from 192.168.55.203: icmp_seq=196 ttl=63 time=1.009 ms
64 bytes from 192.168.55.203: icmp_seq=197 ttl=63 time=3.632 ms
64 bytes from 192.168.55.203: icmp_seq=198 ttl=63 time=3.653 ms
64 bytes from 192.168.55.203: icmp_seq=199 ttl=63 time=1.102 ms
64 bytes from 192.168.55.203: icmp_seq=200 ttl=63 time=3.704 ms
64 bytes from 192.168.55.203: icmp_seq=201 ttl=63 time=1.102 ms
64 bytes from 192.168.55.203: icmp_seq=202 ttl=63 time=1.129 ms
64 bytes from 192.168.55.203: icmp_seq=203 ttl=63 time=3.777 ms
64 bytes from 192.168.55.203: icmp_seq=204 ttl=63 time=3.825 ms
64 bytes from 192.168.55.203: icmp_seq=205 ttl=63 time=3.636 ms
64 bytes from 192.168.55.203: icmp_seq=206 ttl=63 time=3.633 ms
64 bytes from 192.168.55.203: icmp_seq=207 ttl=63 time=1.501 ms
64 bytes from 192.168.55.203: icmp_seq=208 ttl=63 time=3.858 ms
64 bytes from 192.168.55.203: icmp_seq=209 ttl=63 time=3.615 ms
64 bytes from 192.168.55.203: icmp_seq=210 ttl=63 time=1.107 ms
64 bytes from 192.168.55.203: icmp_seq=211 ttl=63 time=1.117 ms
64 bytes from 192.168.55.203: icmp_seq=212 ttl=63 time=3.601 ms
64 bytes from 192.168.55.203: icmp_seq=213 ttl=63 time=1.130 ms
64 bytes from 192.168.55.203: icmp_seq=214 ttl=63 time=1.111 ms
64 bytes from 192.168.55.203: icmp_seq=215 ttl=63 time=1.100 ms
64 bytes from 192.168.55.203: icmp_seq=216 ttl=63 time=2.438 ms
64 bytes from 192.168.55.203: icmp_seq=217 ttl=63 time=1.113 ms
64 bytes from 192.168.55.203: icmp_seq=218 ttl=63 time=3.718 ms
64 bytes from 192.168.55.203: icmp_seq=219 ttl=63 time=3.763 ms
64 bytes from 192.168.55.203: icmp_seq=220 ttl=63 time=3.722 ms
64 bytes from 192.168.55.203: icmp_seq=221 ttl=63 time=1.128 ms
64 bytes from 192.168.55.203: icmp_seq=222 ttl=63 time=3.621 ms
64 bytes from 192.168.55.203: icmp_seq=223 ttl=63 time=3.742 ms
64 bytes from 192.168.55.203: icmp_seq=224 ttl=63 time=3.699 ms
64 bytes from 192.168.55.203: icmp_seq=225 ttl=63 time=1.254 ms
64 bytes from 192.168.55.203: icmp_seq=226 ttl=63 time=3.018 ms
64 bytes from 192.168.55.203: icmp_seq=227 ttl=63 time=3.674 ms
64 bytes from 192.168.55.203: icmp_seq=228 ttl=63 time=3.683 ms
64 bytes from 192.168.55.203: icmp_seq=229 ttl=63 time=1.460 ms
64 bytes from 192.168.55.203: icmp_seq=230 ttl=63 time=3.941 ms
64 bytes from 192.168.55.203: icmp_seq=231 ttl=63 time=3.654 ms
64 bytes from 192.168.55.203: icmp_seq=232 ttl=63 time=3.700 ms
64 bytes from 192.168.55.203: icmp_seq=233 ttl=63 time=3.749 ms
64 bytes from 192.168.55.203: icmp_seq=234 ttl=63 time=1.261 ms
64 bytes from 192.168.55.203: icmp_seq=235 ttl=63 time=3.724 ms
64 bytes from 192.168.55.203: icmp_seq=236 ttl=63 time=3.765 ms
64 bytes from 192.168.55.203: icmp_seq=237 ttl=63 time=3.538 ms
64 bytes from 192.168.55.203: icmp_seq=238 ttl=63 time=3.811 ms
64 bytes from 192.168.55.203: icmp_seq=239 ttl=63 time=1.262 ms
64 bytes from 192.168.55.203: icmp_seq=240 ttl=63 time=1.849 ms
64 bytes from 192.168.55.203: icmp_seq=241 ttl=63 time=3.709 ms
64 bytes from 192.168.55.203: icmp_seq=242 ttl=63 time=3.639 ms
64 bytes from 192.168.55.203: icmp_seq=243 ttl=63 time=3.724 ms
64 bytes from 192.168.55.203: icmp_seq=244 ttl=63 time=1.251 ms
64 bytes from 192.168.55.203: icmp_seq=245 ttl=63 time=3.493 ms
64 bytes from 192.168.55.203: icmp_seq=246 ttl=63 time=3.697 ms
64 bytes from 192.168.55.203: icmp_seq=247 ttl=63 time=1.153 ms
64 bytes from 192.168.55.203: icmp_seq=248 ttl=63 time=3.746 ms
64 bytes from 192.168.55.203: icmp_seq=249 ttl=63 time=1.328 ms
64 bytes from 192.168.55.203: icmp_seq=250 ttl=63 time=3.779 ms
64 bytes from 192.168.55.203: icmp_seq=251 ttl=63 time=3.625 ms
64 bytes from 192.168.55.203: icmp_seq=252 ttl=63 time=3.726 ms
64 bytes from 192.168.55.203: icmp_seq=253 ttl=63 time=3.816 ms
64 bytes from 192.168.55.203: icmp_seq=254 ttl=63 time=1.824 ms
64 bytes from 192.168.55.203: icmp_seq=255 ttl=63 time=1.154 ms
64 bytes from 192.168.55.203: icmp_seq=256 ttl=63 time=1.131 ms
64 bytes from 192.168.55.203: icmp_seq=257 ttl=63 time=1.153 ms
64 bytes from 192.168.55.203: icmp_seq=258 ttl=63 time=1.142 ms
64 bytes from 192.168.55.203: icmp_seq=259 ttl=63 time=1.168 ms
64 bytes from 192.168.55.203: icmp_seq=260 ttl=63 time=1.138 ms
64 bytes from 192.168.55.203: icmp_seq=261 ttl=63 time=3.676 ms
64 bytes from 192.168.55.203: icmp_seq=262 ttl=63 time=1.116 ms
64 bytes from 192.168.55.203: icmp_seq=263 ttl=63 time=4.077 ms
64 bytes from 192.168.55.203: icmp_seq=264 ttl=63 time=2.156 ms
64 bytes from 192.168.55.203: icmp_seq=265 ttl=63 time=3.727 ms
64 bytes from 192.168.55.203: icmp_seq=266 ttl=63 time=1.135 ms
64 bytes from 192.168.55.203: icmp_seq=267 ttl=63 time=3.616 ms
64 bytes from 192.168.55.203: icmp_seq=268 ttl=63 time=1.293 ms
64 bytes from 192.168.55.203: icmp_seq=269 ttl=63 time=2.746 ms
64 bytes from 192.168.55.203: icmp_seq=270 ttl=63 time=3.629 ms
64 bytes from 192.168.55.203: icmp_seq=271 ttl=63 time=3.612 ms
64 bytes from 192.168.55.203: icmp_seq=272 ttl=63 time=3.720 ms
64 bytes from 192.168.55.203: icmp_seq=273 ttl=63 time=1.285 ms
64 bytes from 192.168.55.203: icmp_seq=274 ttl=63 time=1.162 ms
64 bytes from 192.168.55.203: icmp_seq=275 ttl=63 time=3.652 ms
64 bytes from 192.168.55.203: icmp_seq=276 ttl=63 time=3.698 ms
64 bytes from 192.168.55.203: icmp_seq=277 ttl=63 time=3.657 ms
64 bytes from 192.168.55.203: icmp_seq=278 ttl=63 time=1.279 ms
64 bytes from 192.168.55.203: icmp_seq=279 ttl=63 time=3.610 ms
64 bytes from 192.168.55.203: icmp_seq=280 ttl=63 time=3.718 ms
64 bytes from 192.168.55.203: icmp_seq=281 ttl=63 time=0.884 ms
64 bytes from 192.168.55.203: icmp_seq=282 ttl=63 time=3.819 ms
64 bytes from 192.168.55.203: icmp_seq=283 ttl=63 time=3.594 ms
64 bytes from 192.168.55.203: icmp_seq=284 ttl=63 time=4.423 ms
64 bytes from 192.168.55.203: icmp_seq=285 ttl=63 time=3.758 ms
64 bytes from 192.168.55.203: icmp_seq=286 ttl=63 time=3.641 ms
64 bytes from 192.168.55.203: icmp_seq=287 ttl=63 time=3.601 ms
64 bytes from 192.168.55.203: icmp_seq=288 ttl=63 time=1.307 ms
64 bytes from 192.168.55.203: icmp_seq=289 ttl=63 time=3.604 ms
64 bytes from 192.168.55.203: icmp_seq=290 ttl=63 time=3.612 ms
64 bytes from 192.168.55.203: icmp_seq=291 ttl=63 time=3.642 ms
64 bytes from 192.168.55.203: icmp_seq=292 ttl=63 time=3.734 ms
64 bytes from 192.168.55.203: icmp_seq=293 ttl=63 time=1.735 ms
64 bytes from 192.168.55.203: icmp_seq=294 ttl=63 time=3.576 ms
64 bytes from 192.168.55.203: icmp_seq=295 ttl=63 time=3.649 ms
64 bytes from 192.168.55.203: icmp_seq=296 ttl=63 time=3.610 ms
64 bytes from 192.168.55.203: icmp_seq=297 ttl=63 time=1.261 ms
64 bytes from 192.168.55.203: icmp_seq=298 ttl=63 time=3.751 ms
64 bytes from 192.168.55.203: icmp_seq=299 ttl=63 time=3.629 ms

--- 192.168.55.203 ping statistics ---
300 packets transmitted, 300 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.859/2.735/30.155/2.013 ms

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 10:11 am
by yhfung
For comparison, I have made a ping time for 2.4GHz of my hAP ac lite tower. The results are not very good and is very similar to hAP ac^2 2.4G.

I guess this is a general problem in MikroTik 2.4G WiFi interface. If MikroTik can resolve this issue, then the sales of APs of MikrroTik will be increased significantly.

Ping Time summary
round-trip min/avg/max/stddev = 0.887/363.637/5657.065/844.916 ms

Listing 1: hAP ac lite tower, 2.4GHz ping test
ping -c 300 192.168.55.203
PING 192.168.55.203 (192.168.55.203): 56 data bytes
64 bytes from 192.168.55.203: icmp_seq=0 ttl=64 time=323.829 ms
64 bytes from 192.168.55.203: icmp_seq=1 ttl=64 time=25.955 ms
64 bytes from 192.168.55.203: icmp_seq=2 ttl=64 time=8.973 ms
64 bytes from 192.168.55.203: icmp_seq=3 ttl=64 time=19.913 ms
64 bytes from 192.168.55.203: icmp_seq=4 ttl=64 time=1.082 ms
64 bytes from 192.168.55.203: icmp_seq=5 ttl=64 time=5.317 ms
64 bytes from 192.168.55.203: icmp_seq=6 ttl=64 time=1.086 ms
64 bytes from 192.168.55.203: icmp_seq=7 ttl=64 time=308.667 ms
64 bytes from 192.168.55.203: icmp_seq=8 ttl=64 time=1.047 ms
64 bytes from 192.168.55.203: icmp_seq=9 ttl=64 time=1.251 ms
64 bytes from 192.168.55.203: icmp_seq=10 ttl=64 time=1.086 ms
64 bytes from 192.168.55.203: icmp_seq=11 ttl=64 time=5.718 ms
64 bytes from 192.168.55.203: icmp_seq=12 ttl=64 time=4.751 ms
64 bytes from 192.168.55.203: icmp_seq=13 ttl=64 time=3.753 ms
64 bytes from 192.168.55.203: icmp_seq=14 ttl=64 time=2.244 ms
64 bytes from 192.168.55.203: icmp_seq=15 ttl=64 time=3.609 ms
64 bytes from 192.168.55.203: icmp_seq=16 ttl=64 time=1.634 ms
64 bytes from 192.168.55.203: icmp_seq=17 ttl=64 time=8.625 ms
64 bytes from 192.168.55.203: icmp_seq=18 ttl=64 time=325.600 ms
64 bytes from 192.168.55.203: icmp_seq=19 ttl=64 time=7.690 ms
64 bytes from 192.168.55.203: icmp_seq=20 ttl=64 time=69.038 ms
64 bytes from 192.168.55.203: icmp_seq=21 ttl=64 time=201.804 ms
64 bytes from 192.168.55.203: icmp_seq=22 ttl=64 time=1.041 ms
64 bytes from 192.168.55.203: icmp_seq=23 ttl=64 time=3.656 ms
64 bytes from 192.168.55.203: icmp_seq=24 ttl=64 time=173.902 ms
64 bytes from 192.168.55.203: icmp_seq=25 ttl=64 time=86.742 ms
64 bytes from 192.168.55.203: icmp_seq=26 ttl=64 time=71.184 ms
64 bytes from 192.168.55.203: icmp_seq=27 ttl=64 time=2.409 ms
64 bytes from 192.168.55.203: icmp_seq=28 ttl=64 time=13.397 ms
64 bytes from 192.168.55.203: icmp_seq=29 ttl=64 time=5.820 ms
64 bytes from 192.168.55.203: icmp_seq=30 ttl=64 time=1.253 ms
64 bytes from 192.168.55.203: icmp_seq=31 ttl=64 time=4.284 ms
64 bytes from 192.168.55.203: icmp_seq=32 ttl=64 time=3.501 ms
64 bytes from 192.168.55.203: icmp_seq=33 ttl=64 time=7.068 ms
64 bytes from 192.168.55.203: icmp_seq=34 ttl=64 time=26.712 ms
64 bytes from 192.168.55.203: icmp_seq=35 ttl=64 time=1.661 ms
64 bytes from 192.168.55.203: icmp_seq=36 ttl=64 time=4.608 ms
64 bytes from 192.168.55.203: icmp_seq=37 ttl=64 time=3.720 ms
64 bytes from 192.168.55.203: icmp_seq=38 ttl=64 time=45.346 ms
64 bytes from 192.168.55.203: icmp_seq=39 ttl=64 time=21.216 ms
64 bytes from 192.168.55.203: icmp_seq=40 ttl=64 time=903.666 ms
64 bytes from 192.168.55.203: icmp_seq=41 ttl=64 time=12.080 ms
64 bytes from 192.168.55.203: icmp_seq=42 ttl=64 time=955.356 ms
64 bytes from 192.168.55.203: icmp_seq=43 ttl=64 time=658.905 ms
64 bytes from 192.168.55.203: icmp_seq=44 ttl=64 time=8.816 ms
64 bytes from 192.168.55.203: icmp_seq=45 ttl=64 time=5.255 ms
64 bytes from 192.168.55.203: icmp_seq=46 ttl=64 time=260.629 ms
64 bytes from 192.168.55.203: icmp_seq=47 ttl=64 time=137.395 ms
64 bytes from 192.168.55.203: icmp_seq=48 ttl=64 time=3.624 ms
64 bytes from 192.168.55.203: icmp_seq=49 ttl=64 time=369.378 ms
64 bytes from 192.168.55.203: icmp_seq=50 ttl=64 time=3.673 ms
64 bytes from 192.168.55.203: icmp_seq=51 ttl=64 time=1.616 ms
64 bytes from 192.168.55.203: icmp_seq=52 ttl=64 time=18.931 ms
64 bytes from 192.168.55.203: icmp_seq=53 ttl=64 time=98.884 ms
64 bytes from 192.168.55.203: icmp_seq=54 ttl=64 time=815.632 ms
Request timeout for icmp_seq 55
Request timeout for icmp_seq 56
64 bytes from 192.168.55.203: icmp_seq=55 ttl=64 time=2042.497 ms
64 bytes from 192.168.55.203: icmp_seq=56 ttl=64 time=1044.335 ms
64 bytes from 192.168.55.203: icmp_seq=57 ttl=64 time=47.291 ms
64 bytes from 192.168.55.203: icmp_seq=58 ttl=64 time=1248.707 ms
64 bytes from 192.168.55.203: icmp_seq=59 ttl=64 time=350.423 ms
64 bytes from 192.168.55.203: icmp_seq=60 ttl=64 time=3.607 ms
64 bytes from 192.168.55.203: icmp_seq=61 ttl=64 time=2.391 ms
64 bytes from 192.168.55.203: icmp_seq=62 ttl=64 time=3.636 ms
64 bytes from 192.168.55.203: icmp_seq=63 ttl=64 time=9.358 ms
64 bytes from 192.168.55.203: icmp_seq=64 ttl=64 time=6.331 ms
64 bytes from 192.168.55.203: icmp_seq=65 ttl=64 time=5.662 ms
64 bytes from 192.168.55.203: icmp_seq=66 ttl=64 time=3.671 ms
64 bytes from 192.168.55.203: icmp_seq=67 ttl=64 time=3.518 ms
64 bytes from 192.168.55.203: icmp_seq=68 ttl=64 time=3.533 ms
64 bytes from 192.168.55.203: icmp_seq=69 ttl=64 time=1.260 ms
64 bytes from 192.168.55.203: icmp_seq=70 ttl=64 time=1.005 ms
64 bytes from 192.168.55.203: icmp_seq=71 ttl=64 time=50.148 ms
64 bytes from 192.168.55.203: icmp_seq=72 ttl=64 time=3.387 ms
64 bytes from 192.168.55.203: icmp_seq=73 ttl=64 time=4.388 ms
64 bytes from 192.168.55.203: icmp_seq=74 ttl=64 time=9.662 ms
64 bytes from 192.168.55.203: icmp_seq=75 ttl=64 time=8.966 ms
64 bytes from 192.168.55.203: icmp_seq=76 ttl=64 time=242.610 ms
64 bytes from 192.168.55.203: icmp_seq=77 ttl=64 time=1.422 ms
64 bytes from 192.168.55.203: icmp_seq=78 ttl=64 time=19.737 ms
64 bytes from 192.168.55.203: icmp_seq=79 ttl=64 time=3.715 ms
64 bytes from 192.168.55.203: icmp_seq=80 ttl=64 time=5.808 ms
64 bytes from 192.168.55.203: icmp_seq=81 ttl=64 time=2.149 ms
64 bytes from 192.168.55.203: icmp_seq=82 ttl=64 time=3.644 ms
64 bytes from 192.168.55.203: icmp_seq=83 ttl=64 time=3.790 ms
64 bytes from 192.168.55.203: icmp_seq=84 ttl=64 time=6.156 ms
64 bytes from 192.168.55.203: icmp_seq=85 ttl=64 time=3.552 ms
64 bytes from 192.168.55.203: icmp_seq=86 ttl=64 time=18.714 ms
64 bytes from 192.168.55.203: icmp_seq=87 ttl=64 time=3.570 ms
64 bytes from 192.168.55.203: icmp_seq=88 ttl=64 time=469.629 ms
64 bytes from 192.168.55.203: icmp_seq=89 ttl=64 time=25.599 ms
64 bytes from 192.168.55.203: icmp_seq=90 ttl=64 time=143.794 ms
64 bytes from 192.168.55.203: icmp_seq=91 ttl=64 time=22.200 ms
64 bytes from 192.168.55.203: icmp_seq=92 ttl=64 time=58.597 ms
64 bytes from 192.168.55.203: icmp_seq=93 ttl=64 time=1.431 ms
64 bytes from 192.168.55.203: icmp_seq=94 ttl=64 time=5.642 ms
64 bytes from 192.168.55.203: icmp_seq=95 ttl=64 time=6.033 ms
64 bytes from 192.168.55.203: icmp_seq=96 ttl=64 time=8.576 ms
64 bytes from 192.168.55.203: icmp_seq=97 ttl=64 time=15.394 ms
64 bytes from 192.168.55.203: icmp_seq=98 ttl=64 time=211.708 ms
64 bytes from 192.168.55.203: icmp_seq=99 ttl=64 time=11.861 ms
64 bytes from 192.168.55.203: icmp_seq=100 ttl=64 time=3.588 ms
64 bytes from 192.168.55.203: icmp_seq=101 ttl=64 time=11.166 ms
64 bytes from 192.168.55.203: icmp_seq=102 ttl=64 time=3.585 ms
64 bytes from 192.168.55.203: icmp_seq=103 ttl=64 time=10.426 ms
64 bytes from 192.168.55.203: icmp_seq=104 ttl=64 time=3.533 ms
64 bytes from 192.168.55.203: icmp_seq=105 ttl=64 time=15.693 ms
64 bytes from 192.168.55.203: icmp_seq=106 ttl=64 time=9.308 ms
64 bytes from 192.168.55.203: icmp_seq=107 ttl=64 time=14.143 ms
64 bytes from 192.168.55.203: icmp_seq=108 ttl=64 time=9.740 ms
64 bytes from 192.168.55.203: icmp_seq=109 ttl=64 time=1.259 ms
64 bytes from 192.168.55.203: icmp_seq=110 ttl=64 time=12.101 ms
64 bytes from 192.168.55.203: icmp_seq=111 ttl=64 time=4.117 ms
64 bytes from 192.168.55.203: icmp_seq=112 ttl=64 time=5.445 ms
64 bytes from 192.168.55.203: icmp_seq=113 ttl=64 time=652.753 ms
64 bytes from 192.168.55.203: icmp_seq=114 ttl=64 time=8.860 ms
64 bytes from 192.168.55.203: icmp_seq=115 ttl=64 time=1015.888 ms
64 bytes from 192.168.55.203: icmp_seq=116 ttl=64 time=11.783 ms
64 bytes from 192.168.55.203: icmp_seq=117 ttl=64 time=34.679 ms
64 bytes from 192.168.55.203: icmp_seq=118 ttl=64 time=999.000 ms
64 bytes from 192.168.55.203: icmp_seq=119 ttl=64 time=1.044 ms
64 bytes from 192.168.55.203: icmp_seq=120 ttl=64 time=118.934 ms
64 bytes from 192.168.55.203: icmp_seq=121 ttl=64 time=8.439 ms
64 bytes from 192.168.55.203: icmp_seq=122 ttl=64 time=8.630 ms
64 bytes from 192.168.55.203: icmp_seq=123 ttl=64 time=395.233 ms
64 bytes from 192.168.55.203: icmp_seq=124 ttl=64 time=15.358 ms
64 bytes from 192.168.55.203: icmp_seq=125 ttl=64 time=46.203 ms
64 bytes from 192.168.55.203: icmp_seq=126 ttl=64 time=8.448 ms
64 bytes from 192.168.55.203: icmp_seq=127 ttl=64 time=942.771 ms
64 bytes from 192.168.55.203: icmp_seq=128 ttl=64 time=2.540 ms
64 bytes from 192.168.55.203: icmp_seq=129 ttl=64 time=2926.906 ms
64 bytes from 192.168.55.203: icmp_seq=130 ttl=64 time=1972.429 ms
64 bytes from 192.168.55.203: icmp_seq=131 ttl=64 time=967.220 ms
64 bytes from 192.168.55.203: icmp_seq=132 ttl=64 time=53.792 ms
64 bytes from 192.168.55.203: icmp_seq=133 ttl=64 time=15.725 ms
64 bytes from 192.168.55.203: icmp_seq=134 ttl=64 time=2638.465 ms
64 bytes from 192.168.55.203: icmp_seq=135 ttl=64 time=2665.206 ms
64 bytes from 192.168.55.203: icmp_seq=136 ttl=64 time=1663.327 ms
64 bytes from 192.168.55.203: icmp_seq=137 ttl=64 time=660.046 ms
64 bytes from 192.168.55.203: icmp_seq=138 ttl=64 time=3.670 ms
64 bytes from 192.168.55.203: icmp_seq=139 ttl=64 time=21.990 ms
64 bytes from 192.168.55.203: icmp_seq=140 ttl=64 time=5.590 ms
64 bytes from 192.168.55.203: icmp_seq=141 ttl=64 time=70.232 ms
64 bytes from 192.168.55.203: icmp_seq=142 ttl=64 time=689.859 ms
64 bytes from 192.168.55.203: icmp_seq=143 ttl=64 time=3.699 ms
64 bytes from 192.168.55.203: icmp_seq=144 ttl=64 time=3.619 ms
64 bytes from 192.168.55.203: icmp_seq=145 ttl=64 time=3.586 ms
64 bytes from 192.168.55.203: icmp_seq=146 ttl=64 time=16.308 ms
64 bytes from 192.168.55.203: icmp_seq=147 ttl=64 time=945.166 ms
64 bytes from 192.168.55.203: icmp_seq=148 ttl=64 time=72.766 ms
Request timeout for icmp_seq 151
64 bytes from 192.168.55.203: icmp_seq=149 ttl=64 time=3691.616 ms
64 bytes from 192.168.55.203: icmp_seq=150 ttl=64 time=2742.110 ms
64 bytes from 192.168.55.203: icmp_seq=151 ttl=64 time=1736.903 ms
64 bytes from 192.168.55.203: icmp_seq=152 ttl=64 time=1943.827 ms
64 bytes from 192.168.55.203: icmp_seq=153 ttl=64 time=3550.628 ms
64 bytes from 192.168.55.203: icmp_seq=154 ttl=64 time=2862.499 ms
64 bytes from 192.168.55.203: icmp_seq=155 ttl=64 time=1858.807 ms
64 bytes from 192.168.55.203: icmp_seq=156 ttl=64 time=1000.242 ms
64 bytes from 192.168.55.203: icmp_seq=157 ttl=64 time=156.300 ms
64 bytes from 192.168.55.203: icmp_seq=158 ttl=64 time=162.944 ms
64 bytes from 192.168.55.203: icmp_seq=159 ttl=64 time=6.964 ms
64 bytes from 192.168.55.203: icmp_seq=160 ttl=64 time=681.985 ms
64 bytes from 192.168.55.203: icmp_seq=161 ttl=64 time=3.004 ms
64 bytes from 192.168.55.203: icmp_seq=162 ttl=64 time=4.004 ms
64 bytes from 192.168.55.203: icmp_seq=163 ttl=64 time=63.840 ms
64 bytes from 192.168.55.203: icmp_seq=164 ttl=64 time=293.595 ms
64 bytes from 192.168.55.203: icmp_seq=165 ttl=64 time=13.991 ms
64 bytes from 192.168.55.203: icmp_seq=166 ttl=64 time=15.580 ms
64 bytes from 192.168.55.203: icmp_seq=167 ttl=64 time=1043.481 ms
64 bytes from 192.168.55.203: icmp_seq=168 ttl=64 time=50.526 ms
Request timeout for icmp_seq 172
Request timeout for icmp_seq 173
64 bytes from 192.168.55.203: icmp_seq=169 ttl=64 time=5657.065 ms
64 bytes from 192.168.55.203: icmp_seq=170 ttl=64 time=4656.415 ms
64 bytes from 192.168.55.203: icmp_seq=171 ttl=64 time=4449.446 ms
64 bytes from 192.168.55.203: icmp_seq=172 ttl=64 time=3448.902 ms
64 bytes from 192.168.55.203: icmp_seq=173 ttl=64 time=2447.741 ms
64 bytes from 192.168.55.203: icmp_seq=174 ttl=64 time=2037.000 ms
64 bytes from 192.168.55.203: icmp_seq=175 ttl=64 time=1107.396 ms
64 bytes from 192.168.55.203: icmp_seq=176 ttl=64 time=2520.979 ms
64 bytes from 192.168.55.203: icmp_seq=177 ttl=64 time=4325.378 ms
64 bytes from 192.168.55.203: icmp_seq=178 ttl=64 time=3324.211 ms
64 bytes from 192.168.55.203: icmp_seq=179 ttl=64 time=2322.537 ms
64 bytes from 192.168.55.203: icmp_seq=180 ttl=64 time=1378.471 ms
64 bytes from 192.168.55.203: icmp_seq=181 ttl=64 time=1013.442 ms
64 bytes from 192.168.55.203: icmp_seq=182 ttl=64 time=1447.896 ms
64 bytes from 192.168.55.203: icmp_seq=183 ttl=64 time=1049.812 ms
64 bytes from 192.168.55.203: icmp_seq=184 ttl=64 time=135.074 ms
64 bytes from 192.168.55.203: icmp_seq=185 ttl=64 time=856.081 ms
64 bytes from 192.168.55.203: icmp_seq=186 ttl=64 time=307.958 ms
64 bytes from 192.168.55.203: icmp_seq=187 ttl=64 time=123.919 ms
64 bytes from 192.168.55.203: icmp_seq=188 ttl=64 time=1.955 ms
64 bytes from 192.168.55.203: icmp_seq=189 ttl=64 time=3.784 ms
64 bytes from 192.168.55.203: icmp_seq=190 ttl=64 time=929.739 ms
64 bytes from 192.168.55.203: icmp_seq=191 ttl=64 time=3.820 ms
64 bytes from 192.168.55.203: icmp_seq=192 ttl=64 time=1008.507 ms
64 bytes from 192.168.55.203: icmp_seq=193 ttl=64 time=4.258 ms
64 bytes from 192.168.55.203: icmp_seq=194 ttl=64 time=121.701 ms
64 bytes from 192.168.55.203: icmp_seq=195 ttl=64 time=10.071 ms
64 bytes from 192.168.55.203: icmp_seq=196 ttl=64 time=4.092 ms
64 bytes from 192.168.55.203: icmp_seq=197 ttl=64 time=766.000 ms
64 bytes from 192.168.55.203: icmp_seq=198 ttl=64 time=22.536 ms
64 bytes from 192.168.55.203: icmp_seq=199 ttl=64 time=3.506 ms
64 bytes from 192.168.55.203: icmp_seq=200 ttl=64 time=127.787 ms
64 bytes from 192.168.55.203: icmp_seq=201 ttl=64 time=12.945 ms
64 bytes from 192.168.55.203: icmp_seq=202 ttl=64 time=87.565 ms
64 bytes from 192.168.55.203: icmp_seq=203 ttl=64 time=4.451 ms
64 bytes from 192.168.55.203: icmp_seq=204 ttl=64 time=4.271 ms
64 bytes from 192.168.55.203: icmp_seq=205 ttl=64 time=12.390 ms
64 bytes from 192.168.55.203: icmp_seq=206 ttl=64 time=380.000 ms
64 bytes from 192.168.55.203: icmp_seq=207 ttl=64 time=360.771 ms
64 bytes from 192.168.55.203: icmp_seq=208 ttl=64 time=3.043 ms
64 bytes from 192.168.55.203: icmp_seq=209 ttl=64 time=7.938 ms
64 bytes from 192.168.55.203: icmp_seq=210 ttl=64 time=170.338 ms
64 bytes from 192.168.55.203: icmp_seq=211 ttl=64 time=27.902 ms
64 bytes from 192.168.55.203: icmp_seq=212 ttl=64 time=3.556 ms
64 bytes from 192.168.55.203: icmp_seq=213 ttl=64 time=1.197 ms
64 bytes from 192.168.55.203: icmp_seq=214 ttl=64 time=22.265 ms
64 bytes from 192.168.55.203: icmp_seq=215 ttl=64 time=144.067 ms
64 bytes from 192.168.55.203: icmp_seq=216 ttl=64 time=14.172 ms
64 bytes from 192.168.55.203: icmp_seq=217 ttl=64 time=42.653 ms
64 bytes from 192.168.55.203: icmp_seq=218 ttl=64 time=117.578 ms
64 bytes from 192.168.55.203: icmp_seq=219 ttl=64 time=1.740 ms
64 bytes from 192.168.55.203: icmp_seq=220 ttl=64 time=11.123 ms
64 bytes from 192.168.55.203: icmp_seq=221 ttl=64 time=14.451 ms
64 bytes from 192.168.55.203: icmp_seq=222 ttl=64 time=3.884 ms
64 bytes from 192.168.55.203: icmp_seq=223 ttl=64 time=3.571 ms
64 bytes from 192.168.55.203: icmp_seq=224 ttl=64 time=180.045 ms
64 bytes from 192.168.55.203: icmp_seq=225 ttl=64 time=81.360 ms
64 bytes from 192.168.55.203: icmp_seq=226 ttl=64 time=7.933 ms
64 bytes from 192.168.55.203: icmp_seq=227 ttl=64 time=9.435 ms
64 bytes from 192.168.55.203: icmp_seq=228 ttl=64 time=398.361 ms
64 bytes from 192.168.55.203: icmp_seq=229 ttl=64 time=7.907 ms
64 bytes from 192.168.55.203: icmp_seq=230 ttl=64 time=4.020 ms
64 bytes from 192.168.55.203: icmp_seq=231 ttl=64 time=492.640 ms
64 bytes from 192.168.55.203: icmp_seq=232 ttl=64 time=392.614 ms
64 bytes from 192.168.55.203: icmp_seq=233 ttl=64 time=79.671 ms
64 bytes from 192.168.55.203: icmp_seq=234 ttl=64 time=781.387 ms
64 bytes from 192.168.55.203: icmp_seq=235 ttl=64 time=1.269 ms
64 bytes from 192.168.55.203: icmp_seq=236 ttl=64 time=309.901 ms
64 bytes from 192.168.55.203: icmp_seq=237 ttl=64 time=968.565 ms
64 bytes from 192.168.55.203: icmp_seq=238 ttl=64 time=197.807 ms
64 bytes from 192.168.55.203: icmp_seq=239 ttl=64 time=2.623 ms
64 bytes from 192.168.55.203: icmp_seq=240 ttl=64 time=185.850 ms
64 bytes from 192.168.55.203: icmp_seq=241 ttl=64 time=41.420 ms
64 bytes from 192.168.55.203: icmp_seq=242 ttl=64 time=6.254 ms
64 bytes from 192.168.55.203: icmp_seq=243 ttl=64 time=3.591 ms
64 bytes from 192.168.55.203: icmp_seq=244 ttl=64 time=1.716 ms
64 bytes from 192.168.55.203: icmp_seq=245 ttl=64 time=1.782 ms
64 bytes from 192.168.55.203: icmp_seq=246 ttl=64 time=2.717 ms
64 bytes from 192.168.55.203: icmp_seq=247 ttl=64 time=4.223 ms
64 bytes from 192.168.55.203: icmp_seq=248 ttl=64 time=198.611 ms
64 bytes from 192.168.55.203: icmp_seq=249 ttl=64 time=115.740 ms
64 bytes from 192.168.55.203: icmp_seq=250 ttl=64 time=2.429 ms
64 bytes from 192.168.55.203: icmp_seq=251 ttl=64 time=4.319 ms
64 bytes from 192.168.55.203: icmp_seq=252 ttl=64 time=126.684 ms
64 bytes from 192.168.55.203: icmp_seq=253 ttl=64 time=6.412 ms
64 bytes from 192.168.55.203: icmp_seq=254 ttl=64 time=3.020 ms
64 bytes from 192.168.55.203: icmp_seq=255 ttl=64 time=17.724 ms
64 bytes from 192.168.55.203: icmp_seq=256 ttl=64 time=2.272 ms
64 bytes from 192.168.55.203: icmp_seq=257 ttl=64 time=8.133 ms
64 bytes from 192.168.55.203: icmp_seq=258 ttl=64 time=5.098 ms
64 bytes from 192.168.55.203: icmp_seq=259 ttl=64 time=3.665 ms
64 bytes from 192.168.55.203: icmp_seq=260 ttl=64 time=3.215 ms
64 bytes from 192.168.55.203: icmp_seq=261 ttl=64 time=4.786 ms
64 bytes from 192.168.55.203: icmp_seq=262 ttl=64 time=59.884 ms
64 bytes from 192.168.55.203: icmp_seq=263 ttl=64 time=70.311 ms
64 bytes from 192.168.55.203: icmp_seq=264 ttl=64 time=15.643 ms
64 bytes from 192.168.55.203: icmp_seq=265 ttl=64 time=8.407 ms
64 bytes from 192.168.55.203: icmp_seq=266 ttl=64 time=11.019 ms
64 bytes from 192.168.55.203: icmp_seq=267 ttl=64 time=80.516 ms
64 bytes from 192.168.55.203: icmp_seq=268 ttl=64 time=3.595 ms
64 bytes from 192.168.55.203: icmp_seq=269 ttl=64 time=600.583 ms
64 bytes from 192.168.55.203: icmp_seq=270 ttl=64 time=9.681 ms
64 bytes from 192.168.55.203: icmp_seq=271 ttl=64 time=1246.536 ms
64 bytes from 192.168.55.203: icmp_seq=272 ttl=64 time=244.207 ms
64 bytes from 192.168.55.203: icmp_seq=273 ttl=64 time=23.429 ms
64 bytes from 192.168.55.203: icmp_seq=274 ttl=64 time=8.768 ms
64 bytes from 192.168.55.203: icmp_seq=275 ttl=64 time=3.902 ms
64 bytes from 192.168.55.203: icmp_seq=276 ttl=64 time=8.676 ms
64 bytes from 192.168.55.203: icmp_seq=277 ttl=64 time=9.641 ms
64 bytes from 192.168.55.203: icmp_seq=278 ttl=64 time=4.941 ms
64 bytes from 192.168.55.203: icmp_seq=279 ttl=64 time=132.146 ms
64 bytes from 192.168.55.203: icmp_seq=280 ttl=64 time=0.988 ms
64 bytes from 192.168.55.203: icmp_seq=281 ttl=64 time=146.081 ms
64 bytes from 192.168.55.203: icmp_seq=282 ttl=64 time=8.360 ms
64 bytes from 192.168.55.203: icmp_seq=283 ttl=64 time=11.471 ms
64 bytes from 192.168.55.203: icmp_seq=284 ttl=64 time=2.027 ms
64 bytes from 192.168.55.203: icmp_seq=285 ttl=64 time=8.243 ms
64 bytes from 192.168.55.203: icmp_seq=286 ttl=64 time=113.780 ms
64 bytes from 192.168.55.203: icmp_seq=287 ttl=64 time=149.475 ms
64 bytes from 192.168.55.203: icmp_seq=288 ttl=64 time=65.441 ms
64 bytes from 192.168.55.203: icmp_seq=289 ttl=64 time=0.887 ms
64 bytes from 192.168.55.203: icmp_seq=290 ttl=64 time=157.972 ms
64 bytes from 192.168.55.203: icmp_seq=291 ttl=64 time=11.564 ms
64 bytes from 192.168.55.203: icmp_seq=292 ttl=64 time=7.736 ms
64 bytes from 192.168.55.203: icmp_seq=293 ttl=64 time=3.693 ms
64 bytes from 192.168.55.203: icmp_seq=294 ttl=64 time=5.207 ms
64 bytes from 192.168.55.203: icmp_seq=295 ttl=64 time=184.576 ms
64 bytes from 192.168.55.203: icmp_seq=296 ttl=64 time=6.856 ms
64 bytes from 192.168.55.203: icmp_seq=297 ttl=64 time=14.765 ms
64 bytes from 192.168.55.203: icmp_seq=298 ttl=64 time=29.816 ms
64 bytes from 192.168.55.203: icmp_seq=299 ttl=64 time=15.382 ms

--- 192.168.55.203 ping statistics ---
300 packets transmitted, 300 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.887/363.637/5657.065/844.916 ms

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 10:27 am
by vecernik87
yhfung - I am sorry to bother you with this. Thank you for your effort and all tests but there was a misunderstanding - I did not ask for turning off other devices but for detection of interference. Thing is that even simple devices as power supplies have some EM field and if wrongly designed, it can affect wifi. Same goes to devices which you cannot affect (neighbours, nearby traffic etc..) If you cannot do spectral scan, its fine - i just asked to make sure if there is possibility to confirm/disprove interference.

Due to the fact that your hAP ac lite (atheros chip) is having same issue, I have strong reason to believe that this might point to interference. Hard to believe that multiple different mikrotik devices would have such issue. (coincidence - I have two of these as well but no issue found)

I learned this the hard way while establishing 2.4GHz wifi in the middle of nowhere - there was no other 2.4GHz device but the wifi did not work well - guess why - to provide power, we had a petrol generator and few portable coolers... It was bloody awful to see a spectral scan but on normal frequency usage graph it looked clear (because the interference was not wifi signal) Since then, I am well aware that weird wifi behavior can be caused by literary everything around.

I also fully agree that ping over several seconds is not acceptable. Ping over 100 seconds is just ridiculous and seems to me more like total disconnection of the network instead of just "poor performance". With this kind of performance, it would be totally unusable.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 10:29 am
by strods
We have released 6.43rc RouterOS version that includes potential fix for wireless performance problems on RouterBOARD hAP ac^2 and cAP ac.

Please upgrade and test. Report results back to support@mikrotik.com if you still experience problems even after an upgrade.

"wireless - improved wireless throughput on hAP ac^2 and cAP ac"

viewtopic.php?f=21&t=133420&p=657428#p657426

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 11:47 am
by HZsolt

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 1:11 pm
by squall0833
seems like it fixed for all my mobile devices that had wireless performance issue connecting to hap ac2

but still not for my PC that's using TP-Link Archer T4U USB Adapter, still low speed 1-4Mbps download speed on 2.4Ghz and about 4Mbps on 5Ghz

upload speed are normal 11-12Mbps for my internet connection (35Mbps/12Mbps)

this is a computer with TP Link Archer T4U WiFi AC USB Adapter
2.4Ghz down 4Mbps up 12Mbps
2.4ghz.jpg
5Ghz down 4Mbps up 12Mbps
011.jpg

could it be the compatible problem between the WiFi USB Adapter vs hap ac2?

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 1:23 pm
by mozerd
seems like it fixed for all my mobile devices that had wireless performance issue connecting to hap ac2

but still not for my PC that's using TP-Link Archer T14 USB Adapter, still low speed lesser than 1mbps download speed on 2.4Ghz and about 4Mbps on 5Ghz

upload speed are normal 11-12Mbps for my internet connection (35Mbps/12Mbps)

could it be the compatible problem between the WiFi USB Adapter vs hap ac2?
@squall0833, superior results are only with the same wireless chip on the client side. so YES tour TP-Link Archer T14 USB Adapter is not as capable as it would be if it used the QUALCOMM chip. FYI, your TP link uses the MediaTek MT7610U chip set --- so that chip is compatable BUT not as CAPABLE.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 1:32 pm
by squall0833
seems like it fixed for all my mobile devices that had wireless performance issue connecting to hap ac2

but still not for my PC that's using TP-Link Archer T14 USB Adapter, still low speed lesser than 1mbps download speed on 2.4Ghz and about 4Mbps on 5Ghz

upload speed are normal 11-12Mbps for my internet connection (35Mbps/12Mbps)

could it be the compatible problem between the WiFi USB Adapter vs hap ac2?
@squall0833, superior results are only with the same wireless chip on the client side. so YES tour TP-Link Archer T14 USB Adapter is not as capable as it would be if it used the QUALCOMM chip. FYI, your TP link uses the MediaTek MT7610U chip set --- so that chip is compatable BUT not as CAPABLE.
isn't it too low only up to 4Mbps download speed even it's not that capable ? guess I need to look for another better wifi ac adapter, only that pc has to use wireless

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 1:40 pm
by jrpaz
Still seeing issues with the RX on the hAPac^2 it doesn't get over 100 Mbps on IPERF,
However TX from the hAPac^2 is very much improved well over 300 Mbps.

Tests done about 5m away from hAPac^2

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 1:57 pm
by yhfung
You have to specify the ac device that you used. For my case, I used MacBook Pro Retina 2015. Also CHUWI computer, etc.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 2:30 pm
by squall0833
Alright guys

since the new RC5 improved pretty much improved all my mobile device performance issues on hac ac2 previous I had, so i moved to further test on T4U

after more testing,

I finally found the issue why my T4U isn't getting good speed on hap ac2
i tried following and found out why:

Mobile devices -> hap ac2 FAST
PC + T4U -> TPLink C1200 FAST
PC + T4U -> hap ac = BAD
PC + T4U -> Access Point -> hap ac2 = also BAD
Mobiles Devices --> Access Point -> hap ac2 = FAST

something is not right because that same wifi issue t4u had also happened on Access Point

then i tried PC + T4U --> OnePlus 3T 4G Hotspot = extreme poor performance, lesser than 1Mbps (which was working fine months ago)

went to do some search on T4U, found out the driver for T4U comes with Windows 10 Creator Update is broken, many user has download speed dropped around 4Mbps exactly same as me

So I went to download the old 2016 driver from TP link instead of using windows 10's , problem solved, now works perfectly

it was T4U windows 10 driver fault, causing problem on T4U connect to routers other than TP-Link's

glad I found the actual problem :lol:

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 2:51 pm
by mozerd
Here are my iperf3 test results for the hAP ac2 with firmware 6.43.rc5 using 5G AC only
unfortunately the performance is only marginally better by 10%

Apple MacbookAir as iperf3 Server
Apple OS: High Sierra
Apple wireless Chipset: Broadcom BCM4360

Acer Aspire E17 as iperf3 client
OS Windows 10 Home edition version 1803 build 17134.1
wireless NIC: Qualcomm Atheros QCA9377 Wireless Network Adapter
Distance from hAPac2: 7 meters
C:\MyTemp\iperf3>iperf3 -c 192.168.88.250 -t 60
Connecting to host 192.168.88.250, port 5201
[  4] local 192.168.88.251 port 62851 connected to 192.168.88.250 port 5201
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-1.00   sec  13.1 MBytes   110 Mbits/sec
[  4]   1.00-2.00   sec  13.1 MBytes   110 Mbits/sec
[  4]   2.00-3.00   sec  12.9 MBytes   108 Mbits/sec
[  4]   3.00-4.00   sec  11.8 MBytes  98.8 Mbits/sec
[  4]   4.00-5.00   sec  13.8 MBytes   115 Mbits/sec
[  4]   5.00-6.00   sec  13.8 MBytes   115 Mbits/sec
[  4]   6.00-7.01   sec  13.1 MBytes   110 Mbits/sec
[  4]   7.01-8.00   sec  13.1 MBytes   111 Mbits/sec
[  4]   8.00-9.00   sec  12.9 MBytes   108 Mbits/sec
[  4]   9.00-10.00  sec  13.1 MBytes   110 Mbits/sec
[  4]  10.00-11.01  sec  13.8 MBytes   114 Mbits/sec
[  4]  11.01-12.00  sec  13.1 MBytes   111 Mbits/sec
[  4]  12.00-13.00  sec  13.4 MBytes   112 Mbits/sec
[  4]  13.00-14.00  sec  12.5 MBytes   105 Mbits/sec
[  4]  14.00-15.00  sec  12.4 MBytes   104 Mbits/sec
[  4]  15.00-16.00  sec  13.4 MBytes   112 Mbits/sec
[  4]  16.00-17.00  sec  13.4 MBytes   112 Mbits/sec
[  4]  17.00-18.00  sec  13.6 MBytes   114 Mbits/sec
[  4]  18.00-19.00  sec  13.8 MBytes   115 Mbits/sec
[  4]  19.00-20.00  sec  13.6 MBytes   114 Mbits/sec
[  4]  20.00-21.00  sec  13.2 MBytes   111 Mbits/sec
[  4]  21.00-22.00  sec  13.5 MBytes   113 Mbits/sec
[  4]  22.00-23.00  sec  13.4 MBytes   112 Mbits/sec
[  4]  23.00-24.00  sec  13.5 MBytes   113 Mbits/sec
[  4]  24.00-25.01  sec  13.4 MBytes   112 Mbits/sec
[  4]  25.01-26.00  sec  13.0 MBytes   110 Mbits/sec
[  4]  26.00-27.00  sec  12.6 MBytes   106 Mbits/sec
[  4]  27.00-28.00  sec  13.2 MBytes   111 Mbits/sec
[  4]  28.00-29.00  sec  13.2 MBytes   111 Mbits/sec
[  4]  29.00-30.00  sec  12.8 MBytes   107 Mbits/sec
[  4]  30.00-31.00  sec  12.8 MBytes   107 Mbits/sec
[  4]  31.00-32.00  sec  13.2 MBytes   111 Mbits/sec
[  4]  32.00-33.00  sec  13.6 MBytes   114 Mbits/sec
[  4]  33.00-34.01  sec  13.4 MBytes   112 Mbits/sec
[  4]  34.01-35.00  sec  13.5 MBytes   114 Mbits/sec
[  4]  35.00-36.00  sec  14.0 MBytes   117 Mbits/sec
[  4]  36.00-37.00  sec  13.4 MBytes   112 Mbits/sec
[  4]  37.00-38.00  sec  13.5 MBytes   113 Mbits/sec
[  4]  38.00-39.00  sec  13.5 MBytes   113 Mbits/sec
[  4]  39.00-40.00  sec  12.8 MBytes   107 Mbits/sec
[  4]  40.00-41.00  sec  12.9 MBytes   108 Mbits/sec
[  4]  41.00-42.00  sec  13.2 MBytes   111 Mbits/sec
[  4]  42.00-43.00  sec  13.1 MBytes   110 Mbits/sec
[  4]  43.00-44.00  sec  13.1 MBytes   110 Mbits/sec
[  4]  44.00-45.00  sec  13.2 MBytes   111 Mbits/sec
[  4]  45.00-46.00  sec  13.5 MBytes   113 Mbits/sec
[  4]  46.00-47.00  sec  13.1 MBytes   110 Mbits/sec
[  4]  47.00-48.00  sec  13.4 MBytes   112 Mbits/sec
[  4]  48.00-49.00  sec  13.1 MBytes   110 Mbits/sec
[  4]  49.00-50.00  sec  13.6 MBytes   114 Mbits/sec
[  4]  50.00-51.00  sec  13.1 MBytes   111 Mbits/sec
[  4]  51.00-52.00  sec  13.5 MBytes   113 Mbits/sec
[  4]  52.00-53.00  sec  12.9 MBytes   108 Mbits/sec
[  4]  53.00-54.00  sec  12.0 MBytes   100 Mbits/sec
[  4]  54.00-55.00  sec  12.5 MBytes   105 Mbits/sec
[  4]  55.00-56.00  sec  12.1 MBytes   102 Mbits/sec
[  4]  56.00-57.00  sec  12.6 MBytes   106 Mbits/sec
[  4]  57.00-58.00  sec  13.2 MBytes   111 Mbits/sec
[  4]  58.00-59.00  sec  12.8 MBytes   107 Mbits/sec
[  4]  59.00-60.00  sec  13.1 MBytes   110 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-60.00  sec   789 MBytes   110 Mbits/sec                  sender
[  4]   0.00-60.00  sec   789 MBytes   110 Mbits/sec                  receiver
So this is a test that is done between 2 wirless clients residing on a LAN.

Wireless performance done from WAN to LAN and LAN to WAN is significantly better than within the LAN --- between 200 and 300 Mbps --- this is very strange indeed!

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 3:03 pm
by yhfung
yhfung - I am sorry to bother you with this. Thank you for your effort and all tests but there was a misunderstanding - I did not ask for turning off other devices but for detection of interference. Thing is that even simple devices as power supplies have some EM field and if wrongly designed, it can affect wifi. Same goes to devices which you cannot affect (neighbours, nearby traffic etc..) If you cannot do spectral scan, its fine - i just asked to make sure if there is possibility to confirm/disprove interference.

Due to the fact that your hAP ac lite (atheros chip) is having same issue, I have strong reason to believe that this might point to interference. Hard to believe that multiple different mikrotik devices would have such issue. (coincidence - I have two of these as well but no issue found)

I learned this the hard way while establishing 2.4GHz wifi in the middle of nowhere - there was no other 2.4GHz device but the wifi did not work well - guess why - to provide power, we had a petrol generator and few portable coolers... It was bloody awful to see a spectral scan but on normal frequency usage graph it looked clear (because the interference was not wifi signal) Since then, I am well aware that weird wifi behavior can be caused by literary everything around.

I also fully agree that ping over several seconds is not acceptable. Ping over 100 seconds is just ridiculous and seems to me more like total disconnection of the network instead of just "poor performance". With this kind of performance, it would be totally unusable.
Thank you for your comments such that I moved the whole setup away from my office to another room. I use Android WiFi Analyzer to scan the surrounding environment and found a lot of WiFi signal nearby. Also the reason that I moved the whole setup to another room to eliminate the possibility of getting interfered by other devices such that AC-DC adapters. Anyway, it seems that it improved a lot. Also I narrowed the radio bandwidth from 40MHz to 20MHz as well. The new environment and new settings on radio bandwidth, the results obtained seems better than the previous location.

It seems that we can allow the interference from other devices and other electrical appliances. The best choice is to use 5GHz ac or n.

Anyway, many thanks for your advice.

YH

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 3:10 pm
by yhfung
Here are my iperf3 test results for the hAP ac2 with firmware 6.43.rc5 using 5G AC only
unfortunately the performance is only marginally better by 10%

[ ID] Interval Transfer Bandwidth
[ 4] 0.00-60.00 sec 789 MBytes 110 Mbits/sec sender
[ 4] 0.00-60.00 sec 789 MBytes 110 Mbits/sec receiver[/code]
So this is a test that is done between 2 wirless clients residing on a LAN.

Wireless performance done from WAN to LAN and LAN to WAN is significantly better than within the LAN --- between 200 and 300 Mbps --- this is very strange indeed!
It seems the current ac device can give a maximum throughput to 400Mbps (for my case). For your case, it is around 300Mbps. If two laptop pc's talk to transfer file in between, then the throughput will be divided by two. This is what I guess, MikroTik can give a definite answer for this question. Nevertheless, the overall performance for the 5GHz WiFi has been significantly improved.

YH

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 4:05 pm
by yhfung
added remarks. The two routers are about 5m away with a concrete wall in between. I did not take down the test results with only laptop to the R1.

Also I included a log of using labtop MacBook to the remote R1, the test results is summarised below:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-300.01 sec 10.6 GBytes 304 Mbits/sec 343 sender

-------------------
I would like to share the good results for my setup.

I have two hAP ac^2 (R1 and R2) connected by back-to-back mode via 5GHz link. The WAN of R1 was connected to the Internet. wlan2 of R1 was connected to wlan2 of R2, which became the WAN port of R2 with masquerade NAT. I attached my laptop MacBook Pro Retina 2015 to the LAN port of R2. There was a file server attached to the LAN port of R1 forming an iperf3 server. I initiated a download test from my MacBook and I got the following results.

As seen in Listing 1, the results are very satisfactory and the Retr count is 612, which may be the combination of two hAP ac^2 routers. This reading is acceptable.

Listing 1: Two hAP ac^2 connected by back-to-back mode
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-300.01 sec 8.30 GBytes 238 Mbits/sec 612 sender

Listing 2: Results in details
Accepted connection from 192.168.55.42, port 62918
[  5] local 192.168.55.203 port 5201 connected to 192.168.55.42 port 62919
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.01   sec  19.4 MBytes   162 Mbits/sec    6    417 KBytes
[  5]   1.01-2.01   sec  25.4 MBytes   213 Mbits/sec    0    478 KBytes
[  5]   2.01-3.01   sec  33.2 MBytes   279 Mbits/sec    0    519 KBytes
[  5]   3.01-4.01   sec  33.0 MBytes   277 Mbits/sec    0    546 KBytes
[  5]   4.01-5.01   sec  25.5 MBytes   214 Mbits/sec    4    396 KBytes
[  5]   5.01-6.01   sec  26.1 MBytes   219 Mbits/sec    2    321 KBytes
[  5]   6.01-7.01   sec  7.02 MBytes  58.9 Mbits/sec   42   59.4 KBytes
[  5]   7.01-8.00   sec  17.3 MBytes   146 Mbits/sec    0   83.4 KBytes
[  5]   8.00-9.01   sec  18.2 MBytes   152 Mbits/sec    0    103 KBytes
[  5]   9.01-10.01  sec  21.7 MBytes   182 Mbits/sec    0    122 KBytes
[  5]  10.01-11.01  sec  22.0 MBytes   185 Mbits/sec    0    139 KBytes
[  5]  11.01-12.01  sec  23.7 MBytes   199 Mbits/sec    0    154 KBytes
[  5]  12.01-13.01  sec  24.2 MBytes   203 Mbits/sec    0    170 KBytes
[  5]  13.01-14.01  sec  25.5 MBytes   214 Mbits/sec    0    184 KBytes
[  5]  14.01-15.00  sec  25.9 MBytes   218 Mbits/sec    0    197 KBytes
[  5]  15.00-16.01  sec  25.8 MBytes   215 Mbits/sec    0    232 KBytes
[  5]  16.01-17.01  sec  26.9 MBytes   226 Mbits/sec    0    324 KBytes
[  5]  17.01-18.00  sec  30.9 MBytes   261 Mbits/sec    0    440 KBytes
[  5]  18.00-19.01  sec  29.4 MBytes   245 Mbits/sec    2    368 KBytes
[  5]  19.01-20.01  sec  29.9 MBytes   251 Mbits/sec    0    423 KBytes
[  5]  20.01-21.01  sec  32.1 MBytes   270 Mbits/sec    0    461 KBytes
[  5]  21.01-22.00  sec  29.8 MBytes   250 Mbits/sec    0    484 KBytes
[  5]  22.00-23.00  sec  30.6 MBytes   257 Mbits/sec    0    496 KBytes
[  5]  23.00-24.00  sec  28.2 MBytes   237 Mbits/sec    0    502 KBytes
[  5]  24.00-25.01  sec  24.7 MBytes   206 Mbits/sec    0    502 KBytes
[  5]  25.01-26.00  sec  26.6 MBytes   225 Mbits/sec    0    503 KBytes
[  5]  26.00-27.01  sec  29.1 MBytes   243 Mbits/sec    0    505 KBytes
[  5]  27.01-28.01  sec  24.0 MBytes   202 Mbits/sec    0    513 KBytes
[  5]  28.01-29.01  sec  25.7 MBytes   216 Mbits/sec    1    366 KBytes
[  5]  29.01-30.01  sec  28.3 MBytes   237 Mbits/sec    0    397 KBytes
[  5]  30.01-31.01  sec  30.0 MBytes   252 Mbits/sec    0    414 KBytes
[  5]  31.01-32.00  sec  27.8 MBytes   235 Mbits/sec    0    423 KBytes
[  5]  32.00-33.01  sec  27.7 MBytes   230 Mbits/sec    0    424 KBytes
[  5]  33.01-34.01  sec  27.7 MBytes   232 Mbits/sec    0    426 KBytes
[  5]  34.01-35.01  sec  31.6 MBytes   265 Mbits/sec    0    426 KBytes
[  5]  35.01-36.01  sec  32.6 MBytes   274 Mbits/sec    0    431 KBytes
[  5]  36.01-37.01  sec  29.1 MBytes   244 Mbits/sec    0    444 KBytes
[  5]  37.01-38.01  sec  27.0 MBytes   227 Mbits/sec    0    469 KBytes
[  5]  38.01-39.01  sec  27.7 MBytes   233 Mbits/sec    0    509 KBytes
[  5]  39.01-40.01  sec  29.1 MBytes   244 Mbits/sec    6    397 KBytes
[  5]  40.01-41.01  sec  27.0 MBytes   226 Mbits/sec    0    461 KBytes
[  5]  41.01-42.01  sec  27.3 MBytes   229 Mbits/sec    0    505 KBytes
[  5]  42.01-43.01  sec  27.5 MBytes   231 Mbits/sec    0    535 KBytes
[  5]  43.01-44.00  sec  28.1 MBytes   237 Mbits/sec    1    383 KBytes
[  5]  44.00-45.01  sec  26.9 MBytes   225 Mbits/sec    0    410 KBytes
[  5]  45.01-46.01  sec  26.7 MBytes   224 Mbits/sec    0    426 KBytes
[  5]  46.01-47.00  sec  27.6 MBytes   233 Mbits/sec    0    431 KBytes
[  5]  47.00-48.01  sec  27.0 MBytes   225 Mbits/sec    0    433 KBytes
[  5]  48.01-49.01  sec  28.0 MBytes   235 Mbits/sec    0    434 KBytes
[  5]  49.01-50.01  sec  26.1 MBytes   219 Mbits/sec    0    434 KBytes
[  5]  50.01-51.01  sec  27.1 MBytes   227 Mbits/sec    0    441 KBytes
[  5]  51.01-52.00  sec  27.5 MBytes   232 Mbits/sec    0    458 KBytes
[  5]  52.00-53.01  sec  27.6 MBytes   230 Mbits/sec    0    486 KBytes
[  5]  53.01-54.01  sec  27.7 MBytes   232 Mbits/sec    0    529 KBytes
[  5]  54.01-55.01  sec  27.5 MBytes   231 Mbits/sec    1    404 KBytes
[  5]  55.01-56.01  sec  25.0 MBytes   210 Mbits/sec    0    447 KBytes
[  5]  56.01-57.01  sec  26.1 MBytes   219 Mbits/sec    0    475 KBytes
[  5]  57.01-58.01  sec  28.5 MBytes   239 Mbits/sec    0    492 KBytes
[  5]  58.01-59.00  sec  30.6 MBytes   259 Mbits/sec    0    499 KBytes
[  5]  59.00-60.01  sec  29.5 MBytes   246 Mbits/sec    0    501 KBytes
[  5]  60.01-61.01  sec  27.9 MBytes   234 Mbits/sec    0    501 KBytes
[  5]  61.01-62.01  sec  23.2 MBytes   194 Mbits/sec    0    502 KBytes
[  5]  62.01-63.01  sec  24.4 MBytes   204 Mbits/sec    0    508 KBytes
[  5]  63.01-64.01  sec  23.9 MBytes   200 Mbits/sec    0    523 KBytes
[  5]  64.01-65.01  sec  25.9 MBytes   217 Mbits/sec    0    550 KBytes
[  5]  65.01-66.01  sec  28.7 MBytes   241 Mbits/sec   26    437 KBytes
[  5]  66.01-67.01  sec  27.5 MBytes   231 Mbits/sec    0    489 KBytes
[  5]  67.01-68.01  sec  28.9 MBytes   242 Mbits/sec    0    525 KBytes
[  5]  68.01-69.01  sec  29.9 MBytes   251 Mbits/sec    0    546 KBytes
[  5]  69.01-70.01  sec  29.5 MBytes   248 Mbits/sec   11    410 KBytes
[  5]  70.01-71.01  sec  29.2 MBytes   245 Mbits/sec    0    441 KBytes
[  5]  71.01-72.01  sec  27.8 MBytes   234 Mbits/sec    0    458 KBytes
[  5]  72.01-73.01  sec  29.8 MBytes   251 Mbits/sec    0    467 KBytes
[  5]  73.01-74.00  sec  29.6 MBytes   249 Mbits/sec    0    469 KBytes
[  5]  74.00-75.01  sec  28.1 MBytes   235 Mbits/sec    0    469 KBytes
[  5]  75.01-76.01  sec  28.8 MBytes   242 Mbits/sec    0    471 KBytes
[  5]  76.01-77.01  sec  28.5 MBytes   239 Mbits/sec    0    475 KBytes
[  5]  77.01-78.01  sec  29.1 MBytes   244 Mbits/sec    0    488 KBytes
[  5]  78.01-79.01  sec  29.3 MBytes   246 Mbits/sec    0    512 KBytes
[  5]  79.01-80.01  sec  29.0 MBytes   243 Mbits/sec   14    362 KBytes
[  5]  80.01-81.01  sec  29.1 MBytes   244 Mbits/sec    0    419 KBytes
[  5]  81.01-82.01  sec  30.2 MBytes   253 Mbits/sec    0    457 KBytes
[  5]  82.01-83.01  sec  32.2 MBytes   270 Mbits/sec    0    481 KBytes
[  5]  83.01-84.01  sec  29.0 MBytes   243 Mbits/sec    0    495 KBytes
[  5]  84.01-85.00  sec  29.5 MBytes   248 Mbits/sec    0    501 KBytes
[  5]  85.00-86.01  sec  28.9 MBytes   241 Mbits/sec    0    501 KBytes
[  5]  86.01-87.01  sec  30.1 MBytes   253 Mbits/sec    0    502 KBytes
[  5]  87.01-88.01  sec  28.8 MBytes   241 Mbits/sec    0    503 KBytes
[  5]  88.01-89.01  sec  29.0 MBytes   243 Mbits/sec    0    512 KBytes
[  5]  89.01-90.00  sec  31.0 MBytes   261 Mbits/sec    5    406 KBytes
[  5]  90.00-91.01  sec  32.7 MBytes   273 Mbits/sec    0    454 KBytes
[  5]  91.01-92.01  sec  32.3 MBytes   271 Mbits/sec    0    486 KBytes
[  5]  92.01-93.01  sec  28.1 MBytes   236 Mbits/sec    0    505 KBytes
[  5]  93.01-94.01  sec  32.9 MBytes   276 Mbits/sec    0    513 KBytes
[  5]  94.01-95.01  sec  32.2 MBytes   270 Mbits/sec    0    516 KBytes
[  5]  95.01-96.01  sec  34.5 MBytes   289 Mbits/sec    0    516 KBytes
[  5]  96.01-97.01  sec  35.2 MBytes   295 Mbits/sec    0    518 KBytes
[  5]  97.01-98.01  sec  35.0 MBytes   293 Mbits/sec    0    522 KBytes
[  5]  98.01-99.01  sec  36.3 MBytes   305 Mbits/sec    0    532 KBytes
[  5]  99.01-100.01 sec  34.2 MBytes   287 Mbits/sec    8    417 KBytes
[  5] 100.01-101.01 sec  33.2 MBytes   279 Mbits/sec    0    469 KBytes
[  5] 101.01-102.01 sec  36.0 MBytes   302 Mbits/sec    0    505 KBytes
[  5] 102.01-103.00 sec  35.2 MBytes   297 Mbits/sec    0    526 KBytes
[  5] 103.00-104.01 sec  35.5 MBytes   298 Mbits/sec    0    537 KBytes
[  5] 104.01-105.01 sec  35.4 MBytes   297 Mbits/sec    0    542 KBytes
[  5] 105.01-106.00 sec  35.0 MBytes   294 Mbits/sec    0    542 KBytes
[  5] 106.00-107.01 sec  33.8 MBytes   283 Mbits/sec    0    543 KBytes
[  5] 107.01-108.01 sec  35.7 MBytes   299 Mbits/sec    0    546 KBytes
[  5] 108.01-109.01 sec  35.7 MBytes   299 Mbits/sec   24    426 KBytes
[  5] 109.01-110.01 sec  26.7 MBytes   224 Mbits/sec   41    329 KBytes
[  5] 110.01-111.01 sec  31.9 MBytes   267 Mbits/sec    0    352 KBytes
[  5] 111.01-112.01 sec  31.9 MBytes   267 Mbits/sec    0    365 KBytes
[  5] 112.01-113.00 sec  31.1 MBytes   262 Mbits/sec    0    369 KBytes
[  5] 113.00-114.00 sec  31.6 MBytes   266 Mbits/sec    0    369 KBytes
[  5] 114.00-115.00 sec  31.4 MBytes   264 Mbits/sec    0    370 KBytes
[  5] 115.00-116.01 sec  23.6 MBytes   196 Mbits/sec    0    372 KBytes
[  5] 116.01-117.00 sec  28.5 MBytes   239 Mbits/sec    0    382 KBytes
[  5] 117.00-118.00 sec  30.4 MBytes   255 Mbits/sec    0    400 KBytes
[  5] 118.00-119.01 sec  30.8 MBytes   257 Mbits/sec    0    433 KBytes
[  5] 119.01-120.01 sec  33.2 MBytes   278 Mbits/sec    0    481 KBytes
[  5] 120.01-121.00 sec  32.9 MBytes   277 Mbits/sec    0    551 KBytes
[  5] 121.00-122.01 sec  32.1 MBytes   268 Mbits/sec   18    450 KBytes
[  5] 122.01-123.01 sec  32.6 MBytes   274 Mbits/sec    0    508 KBytes
[  5] 123.01-124.01 sec  33.1 MBytes   277 Mbits/sec    0    549 KBytes
[  5] 124.01-125.00 sec  33.2 MBytes   280 Mbits/sec    0    574 KBytes
[  5] 125.00-126.01 sec  32.1 MBytes   269 Mbits/sec   13    438 KBytes
[  5] 126.01-127.00 sec  32.4 MBytes   273 Mbits/sec    0    465 KBytes
[  5] 127.00-128.01 sec  29.9 MBytes   250 Mbits/sec    0    479 KBytes
[  5] 128.01-129.01 sec  31.7 MBytes   266 Mbits/sec    0    486 KBytes
[  5] 129.01-130.01 sec  29.1 MBytes   244 Mbits/sec    0    488 KBytes
[  5] 130.01-131.00 sec  31.8 MBytes   268 Mbits/sec    0    489 KBytes
[  5] 131.00-132.00 sec  32.0 MBytes   268 Mbits/sec    0    489 KBytes
[  5] 132.00-133.01 sec  28.7 MBytes   240 Mbits/sec    0    496 KBytes
[  5] 133.01-134.01 sec   636 KBytes  5.21 Mbits/sec  133   45.2 KBytes
[  5] 134.01-135.01 sec  16.4 MBytes   138 Mbits/sec    1    655 KBytes
[  5] 135.01-136.01 sec  31.1 MBytes   261 Mbits/sec   86    378 KBytes
[  5] 136.01-137.01 sec  33.2 MBytes   279 Mbits/sec    0    416 KBytes
[  5] 137.01-138.01 sec  28.8 MBytes   242 Mbits/sec    0    440 KBytes
[  5] 138.01-139.00 sec  23.4 MBytes   198 Mbits/sec    9    324 KBytes
[  5] 139.00-140.01 sec  25.7 MBytes   214 Mbits/sec    0    355 KBytes
[  5] 140.01-141.01 sec  28.0 MBytes   235 Mbits/sec    0    372 KBytes
[  5] 141.01-142.01 sec  32.2 MBytes   270 Mbits/sec    0    380 KBytes
[  5] 142.01-143.00 sec  29.5 MBytes   248 Mbits/sec    0    383 KBytes
[  5] 143.00-144.00 sec  29.3 MBytes   246 Mbits/sec    0    385 KBytes
[  5] 144.00-145.01 sec  28.9 MBytes   241 Mbits/sec    0    385 KBytes
[  5] 145.01-146.01 sec  29.4 MBytes   247 Mbits/sec    0    389 KBytes
[  5] 146.01-147.01 sec  29.8 MBytes   250 Mbits/sec    0    403 KBytes
[  5] 147.01-148.01 sec  29.4 MBytes   247 Mbits/sec    0    427 KBytes
[  5] 148.01-149.01 sec  31.4 MBytes   264 Mbits/sec    0    465 KBytes
[  5] 149.01-150.01 sec  25.8 MBytes   216 Mbits/sec    0    520 KBytes
[  5] 150.01-151.01 sec  29.3 MBytes   246 Mbits/sec    3    426 KBytes
[  5] 151.01-152.00 sec  30.3 MBytes   254 Mbits/sec    0    475 KBytes
[  5] 152.00-153.01 sec  31.4 MBytes   263 Mbits/sec    0    510 KBytes
[  5] 153.01-154.01 sec  31.4 MBytes   263 Mbits/sec    0    530 KBytes
[  5] 154.01-155.01 sec  32.1 MBytes   270 Mbits/sec    0    540 KBytes
[  5] 155.01-156.01 sec  32.5 MBytes   273 Mbits/sec    0    544 KBytes
[  5] 156.01-157.01 sec  32.5 MBytes   273 Mbits/sec    0    544 KBytes
[  5] 157.01-158.00 sec  28.9 MBytes   244 Mbits/sec    0    543 KBytes
[  5] 158.00-159.01 sec  28.6 MBytes   239 Mbits/sec   28    420 KBytes
[  5] 159.01-160.01 sec  26.6 MBytes   223 Mbits/sec    0    472 KBytes
[  5] 160.01-161.01 sec  30.4 MBytes   255 Mbits/sec    0    509 KBytes
[  5] 161.01-162.01 sec  28.3 MBytes   237 Mbits/sec    0    530 KBytes
[  5] 162.01-163.01 sec  27.1 MBytes   227 Mbits/sec    2    375 KBytes
[  5] 163.01-164.01 sec  28.5 MBytes   239 Mbits/sec    0    403 KBytes
[  5] 164.01-165.00 sec  30.9 MBytes   260 Mbits/sec    0    417 KBytes
[  5] 165.00-166.01 sec  27.3 MBytes   229 Mbits/sec    0    424 KBytes
[  5] 166.01-167.01 sec  27.8 MBytes   234 Mbits/sec    0    426 KBytes
[  5] 167.01-168.00 sec  27.3 MBytes   229 Mbits/sec    0    427 KBytes
[  5] 168.00-169.00 sec  27.2 MBytes   228 Mbits/sec    0    427 KBytes
[  5] 169.00-170.01 sec  27.1 MBytes   227 Mbits/sec    0    434 KBytes
[  5] 170.01-171.01 sec  29.4 MBytes   247 Mbits/sec    0    450 KBytes
[  5] 171.01-172.01 sec  29.9 MBytes   251 Mbits/sec    0    477 KBytes
[  5] 172.01-173.01 sec  21.9 MBytes   184 Mbits/sec    3    304 KBytes
[  5] 173.01-174.01 sec  26.4 MBytes   222 Mbits/sec    0    325 KBytes
[  5] 174.01-175.01 sec  26.7 MBytes   224 Mbits/sec    0    338 KBytes
[  5] 175.01-176.01 sec  27.0 MBytes   226 Mbits/sec    0    342 KBytes
[  5] 176.01-177.00 sec  26.0 MBytes   220 Mbits/sec    0    342 KBytes
[  5] 177.00-178.01 sec  26.4 MBytes   220 Mbits/sec    0    344 KBytes
[  5] 178.01-179.01 sec  26.3 MBytes   221 Mbits/sec    0    345 KBytes
[  5] 179.01-180.01 sec  27.0 MBytes   226 Mbits/sec    0    355 KBytes
[  5] 180.01-181.00 sec  27.2 MBytes   229 Mbits/sec    0    375 KBytes
[  5] 181.00-182.00 sec  26.8 MBytes   225 Mbits/sec    0    407 KBytes
[  5] 182.00-183.01 sec  26.5 MBytes   222 Mbits/sec    0    457 KBytes
[  5] 183.01-184.01 sec  27.0 MBytes   226 Mbits/sec    0    525 KBytes
[  5] 184.01-185.01 sec  27.8 MBytes   233 Mbits/sec   19    431 KBytes
[  5] 185.01-186.01 sec  26.7 MBytes   224 Mbits/sec    0    488 KBytes
[  5] 186.01-187.01 sec  25.8 MBytes   216 Mbits/sec    0    526 KBytes
[  5] 187.01-188.01 sec  27.3 MBytes   229 Mbits/sec    3    404 KBytes
[  5] 188.01-189.01 sec  25.5 MBytes   214 Mbits/sec    0    428 KBytes
[  5] 189.01-190.01 sec  25.5 MBytes   214 Mbits/sec    0    443 KBytes
[  5] 190.01-191.00 sec  27.2 MBytes   229 Mbits/sec    0    450 KBytes
[  5] 191.00-192.01 sec  29.0 MBytes   242 Mbits/sec    0    450 KBytes
[  5] 192.01-193.01 sec  28.3 MBytes   238 Mbits/sec    0    451 KBytes
[  5] 193.01-194.01 sec  29.4 MBytes   247 Mbits/sec    0    451 KBytes
[  5] 194.01-195.01 sec  29.9 MBytes   251 Mbits/sec    0    460 KBytes
[  5] 195.01-196.00 sec  29.1 MBytes   245 Mbits/sec    0    477 KBytes
[  5] 196.00-197.01 sec  27.8 MBytes   232 Mbits/sec    0    506 KBytes
[  5] 197.01-198.01 sec  25.2 MBytes   211 Mbits/sec    0    551 KBytes
[  5] 198.01-199.01 sec  25.5 MBytes   214 Mbits/sec    8    445 KBytes
[  5] 199.01-200.01 sec  24.2 MBytes   203 Mbits/sec    0    494 KBytes
[  5] 200.01-201.01 sec  28.4 MBytes   238 Mbits/sec    0    527 KBytes
[  5] 201.01-202.01 sec  30.4 MBytes   255 Mbits/sec    0    546 KBytes
[  5] 202.01-203.01 sec  28.2 MBytes   236 Mbits/sec    0    556 KBytes
[  5] 203.01-204.01 sec  27.3 MBytes   229 Mbits/sec   14    376 KBytes
[  5] 204.01-205.01 sec  27.2 MBytes   228 Mbits/sec    0    403 KBytes
[  5] 205.01-206.01 sec  27.2 MBytes   228 Mbits/sec    0    417 KBytes
[  5] 206.01-207.01 sec  30.3 MBytes   254 Mbits/sec    0    423 KBytes
[  5] 207.01-208.01 sec  28.3 MBytes   237 Mbits/sec    0    424 KBytes
[  5] 208.01-209.01 sec  30.9 MBytes   259 Mbits/sec    0    426 KBytes
[  5] 209.01-210.01 sec  31.3 MBytes   262 Mbits/sec    0    426 KBytes
[  5] 210.01-211.01 sec  29.3 MBytes   246 Mbits/sec    0    433 KBytes
[  5] 211.01-212.01 sec  28.4 MBytes   238 Mbits/sec    0    450 KBytes
[  5] 212.01-213.00 sec  29.3 MBytes   247 Mbits/sec    0    478 KBytes
[  5] 213.00-214.01 sec  28.6 MBytes   239 Mbits/sec    0    522 KBytes
[  5] 214.01-215.00 sec  31.8 MBytes   267 Mbits/sec    4    424 KBytes
[  5] 215.00-216.01 sec  24.5 MBytes   205 Mbits/sec    0    469 KBytes
[  5] 216.01-217.00 sec  28.8 MBytes   242 Mbits/sec    0    501 KBytes
[  5] 217.00-218.01 sec  26.7 MBytes   223 Mbits/sec    0    518 KBytes
[  5] 218.01-219.00 sec  26.2 MBytes   221 Mbits/sec    0    526 KBytes
[  5] 219.00-220.01 sec  25.0 MBytes   209 Mbits/sec    0    527 KBytes
[  5] 220.01-221.01 sec  28.8 MBytes   242 Mbits/sec    0    527 KBytes
[  5] 221.01-222.01 sec  29.9 MBytes   251 Mbits/sec    0    529 KBytes
[  5] 222.01-223.01 sec  28.5 MBytes   239 Mbits/sec    0    535 KBytes
[  5] 223.01-224.01 sec  23.2 MBytes   195 Mbits/sec    0    547 KBytes
[  5] 224.01-225.01 sec  27.8 MBytes   233 Mbits/sec   21    414 KBytes
[  5] 225.01-226.01 sec  28.6 MBytes   240 Mbits/sec    0    474 KBytes
[  5] 226.01-227.01 sec  29.3 MBytes   246 Mbits/sec    0    515 KBytes
[  5] 227.01-228.00 sec  21.6 MBytes   182 Mbits/sec    4    389 KBytes
[  5] 228.00-229.01 sec  22.0 MBytes   183 Mbits/sec    0    421 KBytes
[  5] 229.01-230.01 sec  24.4 MBytes   205 Mbits/sec    0    440 KBytes
[  5] 230.01-231.00 sec  23.8 MBytes   201 Mbits/sec    0    450 KBytes
[  5] 231.00-232.01 sec  26.3 MBytes   220 Mbits/sec    0    452 KBytes
[  5] 232.01-233.00 sec  25.2 MBytes   213 Mbits/sec    0    452 KBytes
[  5] 233.00-234.00 sec  26.3 MBytes   220 Mbits/sec    0    454 KBytes
[  5] 234.00-235.01 sec  24.7 MBytes   206 Mbits/sec    0    458 KBytes
[  5] 235.01-236.01 sec  23.6 MBytes   198 Mbits/sec    0    469 KBytes
[  5] 236.01-237.01 sec  23.4 MBytes   197 Mbits/sec    0    492 KBytes
[  5] 237.01-238.01 sec  28.8 MBytes   241 Mbits/sec    0    529 KBytes
[  5] 238.01-239.01 sec  30.6 MBytes   257 Mbits/sec   12    417 KBytes
[  5] 239.01-240.01 sec  31.0 MBytes   260 Mbits/sec    0    475 KBytes
[  5] 240.01-241.01 sec  30.4 MBytes   255 Mbits/sec    0    516 KBytes
[  5] 241.01-242.01 sec  29.3 MBytes   245 Mbits/sec    1    361 KBytes
[  5] 242.01-243.01 sec  30.1 MBytes   252 Mbits/sec    0    393 KBytes
[  5] 243.01-244.01 sec  29.6 MBytes   249 Mbits/sec    0    411 KBytes
[  5] 244.01-245.01 sec  28.8 MBytes   242 Mbits/sec    0    421 KBytes
[  5] 245.01-246.00 sec  29.7 MBytes   251 Mbits/sec    0    424 KBytes
[  5] 246.00-247.00 sec  29.8 MBytes   250 Mbits/sec    0    426 KBytes
[  5] 247.00-248.01 sec  29.8 MBytes   249 Mbits/sec    0    426 KBytes
[  5] 248.01-249.01 sec  28.9 MBytes   242 Mbits/sec    0    430 KBytes
[  5] 249.01-250.01 sec  27.9 MBytes   234 Mbits/sec    0    441 KBytes
[  5] 250.01-251.01 sec  26.9 MBytes   226 Mbits/sec    0    464 KBytes
[  5] 251.01-252.00 sec  26.6 MBytes   224 Mbits/sec    0    501 KBytes
[  5] 252.00-253.01 sec  31.0 MBytes   259 Mbits/sec    7    400 KBytes
[  5] 253.01-254.00 sec  28.2 MBytes   237 Mbits/sec    0    454 KBytes
[  5] 254.00-255.01 sec  25.0 MBytes   209 Mbits/sec    0    491 KBytes
[  5] 255.01-256.01 sec  25.8 MBytes   216 Mbits/sec    0    512 KBytes
[  5] 256.01-257.01 sec  32.9 MBytes   276 Mbits/sec    0    525 KBytes
[  5] 257.01-258.01 sec  30.0 MBytes   251 Mbits/sec    0    529 KBytes
[  5] 258.01-259.00 sec  32.6 MBytes   274 Mbits/sec    0    529 KBytes
[  5] 259.00-260.01 sec  32.3 MBytes   270 Mbits/sec    0    530 KBytes
[  5] 260.01-261.01 sec  31.9 MBytes   267 Mbits/sec    4    414 KBytes
[  5] 261.01-262.01 sec  30.4 MBytes   255 Mbits/sec    0    464 KBytes
[  5] 262.01-263.01 sec  30.4 MBytes   255 Mbits/sec    0    498 KBytes
[  5] 263.01-264.01 sec  32.6 MBytes   273 Mbits/sec    0    518 KBytes
[  5] 264.01-265.01 sec  31.3 MBytes   262 Mbits/sec    0    527 KBytes
[  5] 265.01-266.01 sec  27.0 MBytes   227 Mbits/sec    0    530 KBytes
[  5] 266.01-267.01 sec  27.3 MBytes   229 Mbits/sec    9    387 KBytes
[  5] 267.01-268.01 sec  28.5 MBytes   239 Mbits/sec    0    445 KBytes
[  5] 268.01-269.01 sec  29.3 MBytes   246 Mbits/sec    0    485 KBytes
[  5] 269.01-270.01 sec  25.1 MBytes   211 Mbits/sec    3    359 KBytes
[  5] 270.01-271.01 sec  23.6 MBytes   198 Mbits/sec    0    385 KBytes
[  5] 271.01-272.00 sec  25.1 MBytes   211 Mbits/sec    0    397 KBytes
[  5] 272.00-273.01 sec  26.2 MBytes   219 Mbits/sec    0    404 KBytes
[  5] 273.01-274.00 sec  26.0 MBytes   219 Mbits/sec    0    404 KBytes
[  5] 274.00-275.00 sec  26.2 MBytes   219 Mbits/sec    0    406 KBytes
[  5] 275.00-276.01 sec  26.4 MBytes   221 Mbits/sec    0    406 KBytes
[  5] 276.01-277.01 sec  26.6 MBytes   223 Mbits/sec    0    414 KBytes
[  5] 277.01-278.01 sec  27.5 MBytes   231 Mbits/sec    0    431 KBytes
[  5] 278.01-279.01 sec  27.1 MBytes   227 Mbits/sec    0    461 KBytes
[  5] 279.01-280.01 sec  29.0 MBytes   243 Mbits/sec    0    506 KBytes
[  5] 280.01-281.01 sec  29.6 MBytes   248 Mbits/sec    7    404 KBytes
[  5] 281.01-282.01 sec  29.2 MBytes   245 Mbits/sec    0    461 KBytes
[  5] 282.01-283.01 sec  29.3 MBytes   246 Mbits/sec    0    502 KBytes
[  5] 283.01-284.01 sec  29.6 MBytes   249 Mbits/sec    0    526 KBytes
[  5] 284.01-285.01 sec  29.3 MBytes   246 Mbits/sec    0    540 KBytes
[  5] 285.01-286.01 sec  29.5 MBytes   247 Mbits/sec    0    546 KBytes
[  5] 286.01-287.01 sec  28.0 MBytes   235 Mbits/sec    2    362 KBytes
[  5] 287.01-288.01 sec  27.9 MBytes   234 Mbits/sec    0    395 KBytes
[  5] 288.01-289.01 sec  29.3 MBytes   246 Mbits/sec    0    413 KBytes
[  5] 289.01-290.01 sec  27.5 MBytes   230 Mbits/sec    0    423 KBytes
[  5] 290.01-291.01 sec  26.1 MBytes   220 Mbits/sec    0    426 KBytes
[  5] 291.01-292.01 sec  26.7 MBytes   224 Mbits/sec    0    426 KBytes
[  5] 292.01-293.01 sec  25.8 MBytes   216 Mbits/sec    0    427 KBytes
[  5] 293.01-294.01 sec  27.6 MBytes   231 Mbits/sec    0    431 KBytes
[  5] 294.01-295.01 sec  26.8 MBytes   226 Mbits/sec    0    443 KBytes
[  5] 295.01-296.01 sec  26.5 MBytes   222 Mbits/sec    0    465 KBytes
[  5] 296.01-297.01 sec  24.9 MBytes   208 Mbits/sec    0    502 KBytes
[  5] 297.01-298.01 sec  27.0 MBytes   227 Mbits/sec    4    399 KBytes
[  5] 298.01-299.00 sec  26.6 MBytes   224 Mbits/sec    0    454 KBytes
[  5] 299.00-300.01 sec  27.2 MBytes   227 Mbits/sec    0    491 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-300.01 sec  8.30 GBytes   238 Mbits/sec  612             sender
#

Listing 2: Laptop MacBook to hAP ac^2
Accepted connection from 192.168.55.42, port 64270
[  5] local 192.168.55.203 port 5201 connected to 192.168.55.42 port 64271
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  12.4 MBytes   104 Mbits/sec    0    482 KBytes
[  5]   1.00-2.01   sec  14.6 MBytes   121 Mbits/sec   10    501 KBytes
[  5]   2.01-3.01   sec  39.6 MBytes   334 Mbits/sec    0    557 KBytes
[  5]   3.01-4.01   sec  38.6 MBytes   322 Mbits/sec    1    356 KBytes
[  5]   4.01-5.01   sec  37.7 MBytes   317 Mbits/sec    0    390 KBytes
[  5]   5.01-6.00   sec  37.9 MBytes   321 Mbits/sec    0    410 KBytes
[  5]   6.00-7.01   sec  37.8 MBytes   315 Mbits/sec    0    421 KBytes
[  5]   7.01-8.00   sec  37.6 MBytes   317 Mbits/sec    0    424 KBytes
[  5]   8.00-9.01   sec  37.7 MBytes   313 Mbits/sec    0    426 KBytes
[  5]   9.01-10.01  sec  35.8 MBytes   302 Mbits/sec    0    426 KBytes
[  5]  10.01-11.01  sec  35.6 MBytes   297 Mbits/sec    0    428 KBytes
[  5]  11.01-12.01  sec  36.2 MBytes   304 Mbits/sec    0    440 KBytes
[  5]  12.01-13.01  sec  36.7 MBytes   310 Mbits/sec    0    461 KBytes
[  5]  13.01-14.01  sec  36.7 MBytes   307 Mbits/sec    0    498 KBytes
[  5]  14.01-15.01  sec  36.6 MBytes   307 Mbits/sec    0    551 KBytes
[  5]  15.01-16.01  sec  35.8 MBytes   301 Mbits/sec    1    426 KBytes
[  5]  16.01-17.01  sec  35.6 MBytes   299 Mbits/sec    0    482 KBytes
[  5]  17.01-18.01  sec  34.9 MBytes   291 Mbits/sec    0    522 KBytes
[  5]  18.01-19.01  sec  35.5 MBytes   298 Mbits/sec    8    387 KBytes
[  5]  19.01-20.00  sec  35.7 MBytes   302 Mbits/sec    0    423 KBytes
[  5]  20.00-21.01  sec  36.5 MBytes   303 Mbits/sec    0    445 KBytes
[  5]  21.01-22.01  sec  36.9 MBytes   310 Mbits/sec    0    457 KBytes
[  5]  22.01-23.00  sec  38.7 MBytes   327 Mbits/sec    0    461 KBytes
[  5]  23.00-24.01  sec  38.5 MBytes   321 Mbits/sec    0    461 KBytes
[  5]  24.01-25.01  sec  38.4 MBytes   322 Mbits/sec    0    462 KBytes
[  5]  25.01-26.00  sec  38.0 MBytes   321 Mbits/sec    0    464 KBytes
[  5]  26.00-27.01  sec  37.0 MBytes   308 Mbits/sec    0    474 KBytes
[  5]  27.01-28.00  sec  35.2 MBytes   299 Mbits/sec    0    494 KBytes
[  5]  28.00-29.01  sec  35.9 MBytes   298 Mbits/sec    0    527 KBytes
[  5]  29.01-30.01  sec  30.6 MBytes   258 Mbits/sec    4    423 KBytes
[  5]  30.01-31.01  sec  30.9 MBytes   258 Mbits/sec    0    474 KBytes
[  5]  31.01-32.00  sec  32.5 MBytes   275 Mbits/sec    0    509 KBytes
[  5]  32.00-33.01  sec  33.3 MBytes   278 Mbits/sec    0    530 KBytes
[  5]  33.01-34.01  sec  32.3 MBytes   272 Mbits/sec    5    387 KBytes
[  5]  34.01-35.01  sec  32.3 MBytes   270 Mbits/sec    0    421 KBytes
[  5]  35.01-36.01  sec  35.4 MBytes   296 Mbits/sec    0    443 KBytes
[  5]  36.01-37.01  sec  35.1 MBytes   295 Mbits/sec    0    452 KBytes
[  5]  37.01-38.00  sec  36.8 MBytes   312 Mbits/sec    0    457 KBytes
[  5]  38.00-39.01  sec  36.4 MBytes   303 Mbits/sec    0    457 KBytes
[  5]  39.01-40.01  sec  37.3 MBytes   313 Mbits/sec    0    458 KBytes
[  5]  40.01-41.00  sec  35.7 MBytes   302 Mbits/sec    0    461 KBytes
[  5]  41.00-42.01  sec  36.7 MBytes   304 Mbits/sec    0    472 KBytes
[  5]  42.01-43.00  sec  35.3 MBytes   299 Mbits/sec    0    492 KBytes
[  5]  43.00-44.01  sec  38.0 MBytes   316 Mbits/sec    0    527 KBytes
[  5]  44.01-45.01  sec  35.3 MBytes   296 Mbits/sec    6    491 KBytes
[  5]  45.01-46.01  sec  37.7 MBytes   316 Mbits/sec    0    471 KBytes
[  5]  46.01-47.01  sec  35.0 MBytes   295 Mbits/sec    0    518 KBytes
[  5]  47.01-48.01  sec  36.7 MBytes   307 Mbits/sec    2    358 KBytes
[  5]  48.01-49.01  sec  35.0 MBytes   295 Mbits/sec    0    392 KBytes
[  5]  49.01-50.01  sec  35.5 MBytes   297 Mbits/sec    0    411 KBytes
[  5]  50.01-51.00  sec  36.4 MBytes   308 Mbits/sec    0    423 KBytes
[  5]  51.00-52.00  sec  34.1 MBytes   286 Mbits/sec    0    426 KBytes
[  5]  52.00-53.01  sec  35.0 MBytes   293 Mbits/sec    0    427 KBytes
[  5]  53.01-54.00  sec  35.1 MBytes   296 Mbits/sec    0    427 KBytes
[  5]  54.00-55.01  sec  34.2 MBytes   284 Mbits/sec    0    430 KBytes
[  5]  55.01-56.01  sec  34.2 MBytes   288 Mbits/sec    0    441 KBytes
[  5]  56.01-57.01  sec  32.5 MBytes   272 Mbits/sec    0    464 KBytes
[  5]  57.01-58.01  sec  33.2 MBytes   280 Mbits/sec    0    499 KBytes
[  5]  58.01-59.01  sec  35.9 MBytes   301 Mbits/sec    0    550 KBytes
[  5]  59.01-60.01  sec  34.7 MBytes   289 Mbits/sec   12    444 KBytes
[  5]  60.01-61.01  sec  36.4 MBytes   305 Mbits/sec    0    502 KBytes
[  5]  61.01-62.00  sec  36.0 MBytes   305 Mbits/sec    0    540 KBytes
[  5]  62.00-63.01  sec  35.4 MBytes   293 Mbits/sec    0    566 KBytes
[  5]  63.01-64.01  sec  35.6 MBytes   300 Mbits/sec    2    430 KBytes
[  5]  64.01-65.01  sec  33.9 MBytes   283 Mbits/sec    0    457 KBytes
[  5]  65.01-66.00  sec  36.2 MBytes   308 Mbits/sec    0    472 KBytes
[  5]  66.00-67.01  sec  34.9 MBytes   290 Mbits/sec    0    479 KBytes
[  5]  67.01-68.00  sec  34.9 MBytes   296 Mbits/sec    0    481 KBytes
[  5]  68.00-69.01  sec  36.7 MBytes   305 Mbits/sec    0    482 KBytes
[  5]  69.01-70.00  sec  34.9 MBytes   294 Mbits/sec    0    482 KBytes
[  5]  70.00-71.01  sec  36.7 MBytes   305 Mbits/sec    0    489 KBytes
[  5]  71.01-72.01  sec  36.5 MBytes   307 Mbits/sec    0    503 KBytes
[  5]  72.01-73.01  sec  37.3 MBytes   313 Mbits/sec    0    530 KBytes
[  5]  73.01-74.01  sec  35.7 MBytes   300 Mbits/sec    1    397 KBytes
[  5]  74.01-75.01  sec  34.1 MBytes   287 Mbits/sec    0    462 KBytes
[  5]  75.01-76.00  sec  37.4 MBytes   316 Mbits/sec    0    506 KBytes
[  5]  76.00-77.01  sec  37.8 MBytes   314 Mbits/sec    0    536 KBytes
[  5]  77.01-78.00  sec  38.7 MBytes   327 Mbits/sec    0    554 KBytes
[  5]  78.00-79.01  sec  38.0 MBytes   317 Mbits/sec    0    563 KBytes
[  5]  79.01-80.00  sec  36.3 MBytes   308 Mbits/sec    0    564 KBytes
[  5]  80.00-81.00  sec  35.9 MBytes   300 Mbits/sec   23    448 KBytes
[  5]  81.00-82.01  sec  36.4 MBytes   304 Mbits/sec    0    498 KBytes
[  5]  82.01-83.01  sec  34.9 MBytes   291 Mbits/sec    0    532 KBytes
[  5]  83.01-84.00  sec  36.7 MBytes   311 Mbits/sec    0    551 KBytes
[  5]  84.00-85.01  sec  35.8 MBytes   297 Mbits/sec    0    561 KBytes
[  5]  85.01-86.00  sec  37.3 MBytes   317 Mbits/sec    0    564 KBytes
[  5]  86.00-87.01  sec  36.7 MBytes   306 Mbits/sec    0    564 KBytes
[  5]  87.01-88.00  sec  35.2 MBytes   297 Mbits/sec   28    420 KBytes
[  5]  88.00-89.01  sec  33.4 MBytes   280 Mbits/sec    0    478 KBytes
[  5]  89.01-90.01  sec  36.7 MBytes   306 Mbits/sec    0    519 KBytes
[  5]  90.01-91.00  sec  37.2 MBytes   315 Mbits/sec    0    544 KBytes
[  5]  91.00-92.01  sec  36.4 MBytes   304 Mbits/sec    0    557 KBytes
[  5]  92.01-93.00  sec  36.7 MBytes   309 Mbits/sec    0    564 KBytes
[  5]  93.00-94.01  sec  37.1 MBytes   308 Mbits/sec    5    433 KBytes
[  5]  94.01-95.01  sec  35.9 MBytes   301 Mbits/sec    0    486 KBytes
[  5]  95.01-96.01  sec  36.0 MBytes   302 Mbits/sec    0    523 KBytes
[  5]  96.01-97.01  sec  34.0 MBytes   285 Mbits/sec    2    338 KBytes
[  5]  97.01-98.00  sec  33.6 MBytes   284 Mbits/sec    0    358 KBytes
[  5]  98.00-99.00  sec  35.0 MBytes   294 Mbits/sec    0    368 KBytes
[  5]  99.00-100.01 sec  36.0 MBytes   301 Mbits/sec    0    370 KBytes
[  5] 100.01-101.00 sec  37.2 MBytes   313 Mbits/sec    0    372 KBytes
[  5] 101.00-102.01 sec  36.9 MBytes   307 Mbits/sec    0    373 KBytes
[  5] 102.01-103.01 sec  34.6 MBytes   290 Mbits/sec    0    375 KBytes
[  5] 103.01-104.01 sec  35.7 MBytes   299 Mbits/sec    0    387 KBytes
[  5] 104.01-105.01 sec  36.5 MBytes   307 Mbits/sec    0    409 KBytes
[  5] 105.01-106.00 sec  38.0 MBytes   321 Mbits/sec    0    445 KBytes
[  5] 106.00-107.00 sec  37.0 MBytes   311 Mbits/sec    0    498 KBytes
[  5] 107.00-108.01 sec  37.2 MBytes   308 Mbits/sec    0    573 KBytes
[  5] 108.01-109.01 sec  35.0 MBytes   293 Mbits/sec   17    469 KBytes
[  5] 109.01-110.01 sec  36.8 MBytes   310 Mbits/sec    0    522 KBytes
[  5] 110.01-111.01 sec  36.2 MBytes   302 Mbits/sec    0    559 KBytes
[  5] 111.01-112.00 sec  35.9 MBytes   303 Mbits/sec    4    414 KBytes
[  5] 112.00-113.00 sec  36.4 MBytes   306 Mbits/sec    0    451 KBytes
[  5] 113.00-114.00 sec  36.7 MBytes   306 Mbits/sec    0    472 KBytes
[  5] 114.00-115.01 sec  36.1 MBytes   300 Mbits/sec    0    484 KBytes
[  5] 115.01-116.00 sec  38.1 MBytes   323 Mbits/sec    0    488 KBytes
[  5] 116.00-117.00 sec  37.0 MBytes   310 Mbits/sec    0    488 KBytes
[  5] 117.00-118.01 sec  36.2 MBytes   300 Mbits/sec    0    489 KBytes
[  5] 118.01-119.01 sec  37.2 MBytes   313 Mbits/sec    0    491 KBytes
[  5] 119.01-120.01 sec  35.6 MBytes   300 Mbits/sec    0    502 KBytes
[  5] 120.01-121.01 sec  36.0 MBytes   300 Mbits/sec    0    520 KBytes
[  5] 121.01-122.01 sec  37.0 MBytes   310 Mbits/sec    0    554 KBytes
[  5] 122.01-123.01 sec  37.3 MBytes   313 Mbits/sec   10    411 KBytes
[  5] 123.01-124.00 sec  37.2 MBytes   315 Mbits/sec    0    472 KBytes
[  5] 124.00-125.01 sec  36.8 MBytes   307 Mbits/sec    0    515 KBytes
[  5] 125.01-126.01 sec  36.5 MBytes   304 Mbits/sec    7    387 KBytes
[  5] 126.01-127.01 sec  36.7 MBytes   308 Mbits/sec    0    421 KBytes
[  5] 127.01-128.00 sec  36.5 MBytes   310 Mbits/sec    0    441 KBytes
[  5] 128.00-129.01 sec  37.0 MBytes   308 Mbits/sec    0    452 KBytes
[  5] 129.01-130.01 sec  36.2 MBytes   304 Mbits/sec    0    455 KBytes
[  5] 130.01-131.01 sec  34.3 MBytes   287 Mbits/sec    0    457 KBytes
[  5] 131.01-132.01 sec  36.0 MBytes   302 Mbits/sec    0    457 KBytes
[  5] 132.01-133.00 sec  36.9 MBytes   313 Mbits/sec    0    460 KBytes
[  5] 133.00-134.01 sec  37.8 MBytes   314 Mbits/sec    0    471 KBytes
[  5] 134.01-135.01 sec  37.7 MBytes   317 Mbits/sec    0    492 KBytes
[  5] 135.01-136.01 sec  36.7 MBytes   306 Mbits/sec    0    527 KBytes
[  5] 136.01-137.00 sec  36.7 MBytes   311 Mbits/sec    0    580 KBytes
[  5] 137.00-138.01 sec  36.3 MBytes   301 Mbits/sec    4    471 KBytes
[  5] 138.01-139.01 sec  37.5 MBytes   315 Mbits/sec    0    519 KBytes
[  5] 139.01-140.00 sec  36.8 MBytes   311 Mbits/sec    0    550 KBytes
[  5] 140.00-141.01 sec  37.1 MBytes   309 Mbits/sec    1    276 KBytes
[  5] 141.01-142.01 sec  33.6 MBytes   282 Mbits/sec    0    291 KBytes
[  5] 142.01-143.00 sec  35.5 MBytes   301 Mbits/sec    0    307 KBytes
[  5] 143.00-144.01 sec  35.4 MBytes   294 Mbits/sec    0    315 KBytes
[  5] 144.01-145.01 sec  34.8 MBytes   292 Mbits/sec    0    317 KBytes
[  5] 145.01-146.01 sec  34.4 MBytes   289 Mbits/sec    0    318 KBytes
[  5] 146.01-147.01 sec  35.1 MBytes   294 Mbits/sec    0    322 KBytes
[  5] 147.01-148.01 sec  35.2 MBytes   296 Mbits/sec    0    332 KBytes
[  5] 148.01-149.00 sec  32.4 MBytes   274 Mbits/sec    0    341 KBytes
[  5] 149.00-150.00 sec  35.9 MBytes   300 Mbits/sec    0    363 KBytes
[  5] 150.00-151.01 sec  35.6 MBytes   297 Mbits/sec    0    403 KBytes
[  5] 151.01-152.00 sec  37.0 MBytes   314 Mbits/sec    0    461 KBytes
[  5] 152.00-153.01 sec  34.2 MBytes   284 Mbits/sec    0    543 KBytes
[  5] 153.01-154.01 sec  37.3 MBytes   314 Mbits/sec   41    447 KBytes
[  5] 154.01-155.01 sec  36.9 MBytes   309 Mbits/sec    0    503 KBytes
[  5] 155.01-156.01 sec  38.3 MBytes   322 Mbits/sec    0    540 KBytes
[  5] 156.01-157.00 sec  36.6 MBytes   310 Mbits/sec    7    411 KBytes
[  5] 157.00-158.01 sec  36.9 MBytes   308 Mbits/sec    0    441 KBytes
[  5] 158.01-159.01 sec  37.5 MBytes   313 Mbits/sec    0    460 KBytes
[  5] 159.01-160.00 sec  37.1 MBytes   314 Mbits/sec    0    468 KBytes
[  5] 160.00-161.01 sec  37.6 MBytes   313 Mbits/sec    0    469 KBytes
[  5] 161.01-162.01 sec  37.3 MBytes   315 Mbits/sec    0    471 KBytes
[  5] 162.01-163.01 sec  38.0 MBytes   318 Mbits/sec    0    471 KBytes
[  5] 163.01-164.01 sec  37.4 MBytes   313 Mbits/sec    0    475 KBytes
[  5] 164.01-165.01 sec  38.7 MBytes   324 Mbits/sec    0    489 KBytes
[  5] 165.01-166.00 sec  39.0 MBytes   330 Mbits/sec    0    513 KBytes
[  5] 166.00-167.01 sec  38.9 MBytes   326 Mbits/sec    0    553 KBytes
[  5] 167.01-168.01 sec  37.8 MBytes   315 Mbits/sec    9    433 KBytes
[  5] 168.01-169.01 sec  37.7 MBytes   316 Mbits/sec    0    498 KBytes
[  5] 169.01-170.00 sec  38.7 MBytes   328 Mbits/sec    0    542 KBytes
[  5] 170.00-171.00 sec  38.0 MBytes   318 Mbits/sec   11    417 KBytes
[  5] 171.00-172.00 sec  37.8 MBytes   317 Mbits/sec    0    443 KBytes
[  5] 172.00-173.01 sec  38.2 MBytes   319 Mbits/sec    0    458 KBytes
[  5] 173.01-174.01 sec  37.7 MBytes   315 Mbits/sec    0    464 KBytes
[  5] 174.01-175.01 sec  37.5 MBytes   315 Mbits/sec    0    465 KBytes
[  5] 175.01-176.00 sec  38.7 MBytes   327 Mbits/sec    0    467 KBytes
[  5] 176.00-177.01 sec  37.6 MBytes   312 Mbits/sec    0    468 KBytes
[  5] 177.01-178.01 sec  37.7 MBytes   316 Mbits/sec    0    474 KBytes
[  5] 178.01-179.00 sec  37.9 MBytes   322 Mbits/sec    0    491 KBytes
[  5] 179.00-180.01 sec  38.3 MBytes   318 Mbits/sec    0    519 KBytes
[  5] 180.01-181.01 sec  36.8 MBytes   308 Mbits/sec   28    406 KBytes
[  5] 181.01-182.01 sec  37.5 MBytes   314 Mbits/sec    0    462 KBytes
[  5] 182.01-183.01 sec  38.2 MBytes   320 Mbits/sec    0    502 KBytes
[  5] 183.01-184.01 sec  39.1 MBytes   328 Mbits/sec    0    526 KBytes
[  5] 184.01-185.01 sec  37.2 MBytes   311 Mbits/sec    0    540 KBytes
[  5] 185.01-186.01 sec  38.2 MBytes   323 Mbits/sec    0    546 KBytes
[  5] 186.01-187.00 sec  38.5 MBytes   323 Mbits/sec    0    546 KBytes
[  5] 187.00-188.01 sec  38.6 MBytes   321 Mbits/sec    0    547 KBytes
[  5] 188.01-189.01 sec  39.1 MBytes   328 Mbits/sec    0    549 KBytes
[  5] 189.01-190.00 sec  37.4 MBytes   317 Mbits/sec   21    436 KBytes
[  5] 190.00-191.01 sec  38.3 MBytes   319 Mbits/sec    0    485 KBytes
[  5] 191.01-192.01 sec  38.0 MBytes   320 Mbits/sec    0    518 KBytes
[  5] 192.01-193.00 sec  38.8 MBytes   326 Mbits/sec    0    536 KBytes
[  5] 193.00-194.01 sec  39.3 MBytes   328 Mbits/sec    0    546 KBytes
[  5] 194.01-195.01 sec  38.3 MBytes   319 Mbits/sec    0    549 KBytes
[  5] 195.01-196.00 sec  39.5 MBytes   335 Mbits/sec    0    549 KBytes
[  5] 196.00-197.01 sec  35.6 MBytes   295 Mbits/sec    0    550 KBytes
[  5] 197.01-198.00 sec  36.4 MBytes   307 Mbits/sec    0    553 KBytes
[  5] 198.00-199.01 sec  36.0 MBytes   300 Mbits/sec    0    566 KBytes
[  5] 199.01-200.01 sec  36.2 MBytes   304 Mbits/sec    5    413 KBytes
[  5] 200.01-201.00 sec  34.4 MBytes   291 Mbits/sec    0    479 KBytes
[  5] 201.00-202.01 sec  36.0 MBytes   299 Mbits/sec    0    526 KBytes
[  5] 202.01-203.01 sec  36.0 MBytes   302 Mbits/sec    0    557 KBytes
[  5] 203.01-204.01 sec  36.3 MBytes   305 Mbits/sec    6    404 KBytes
[  5] 204.01-205.01 sec  35.3 MBytes   296 Mbits/sec    0    444 KBytes
[  5] 205.01-206.01 sec  36.3 MBytes   306 Mbits/sec    0    468 KBytes
[  5] 206.01-207.01 sec  36.4 MBytes   304 Mbits/sec    0    482 KBytes
[  5] 207.01-208.01 sec  36.4 MBytes   305 Mbits/sec    0    488 KBytes
[  5] 208.01-209.01 sec  38.5 MBytes   323 Mbits/sec    0    488 KBytes
[  5] 209.01-210.00 sec  37.8 MBytes   317 Mbits/sec    0    489 KBytes
[  5] 210.00-211.01 sec  38.2 MBytes   318 Mbits/sec    0    491 KBytes
[  5] 211.01-212.01 sec  37.6 MBytes   315 Mbits/sec    0    498 KBytes
[  5] 212.01-213.01 sec  38.5 MBytes   323 Mbits/sec    0    516 KBytes
[  5] 213.01-214.01 sec  38.8 MBytes   325 Mbits/sec    0    546 KBytes
[  5] 214.01-215.01 sec  39.2 MBytes   330 Mbits/sec    1    218 KBytes
[  5] 215.01-216.01 sec  31.3 MBytes   264 Mbits/sec    0    242 KBytes
[  5] 216.01-217.00 sec  31.4 MBytes   264 Mbits/sec    0    256 KBytes
[  5] 217.00-218.01 sec  29.0 MBytes   242 Mbits/sec    0    262 KBytes
[  5] 218.01-219.01 sec  25.2 MBytes   211 Mbits/sec    0    263 KBytes
[  5] 219.01-220.01 sec  30.9 MBytes   259 Mbits/sec    0    273 KBytes
[  5] 220.01-221.00 sec  31.6 MBytes   268 Mbits/sec    0    283 KBytes
[  5] 221.00-222.00 sec  31.3 MBytes   262 Mbits/sec    0    293 KBytes
[  5] 222.00-223.01 sec  31.8 MBytes   263 Mbits/sec    0    303 KBytes
[  5] 223.01-224.01 sec  33.1 MBytes   279 Mbits/sec    0    320 KBytes
[  5] 224.01-225.01 sec  33.9 MBytes   283 Mbits/sec    0    366 KBytes
[  5] 225.01-226.01 sec  35.5 MBytes   299 Mbits/sec    0    430 KBytes
[  5] 226.01-227.01 sec  34.9 MBytes   292 Mbits/sec    0    518 KBytes
[  5] 227.01-228.00 sec  35.3 MBytes   299 Mbits/sec    1    369 KBytes
[  5] 228.00-229.01 sec  34.2 MBytes   285 Mbits/sec    0    423 KBytes
[  5] 229.01-230.00 sec  35.4 MBytes   299 Mbits/sec    0    460 KBytes
[  5] 230.00-231.00 sec  35.2 MBytes   295 Mbits/sec    0    482 KBytes
[  5] 231.00-232.01 sec  35.3 MBytes   294 Mbits/sec    0    495 KBytes
[  5] 232.01-233.01 sec  36.2 MBytes   305 Mbits/sec    0    499 KBytes
[  5] 233.01-234.01 sec  36.0 MBytes   302 Mbits/sec    0    499 KBytes
[  5] 234.01-235.00 sec  35.0 MBytes   296 Mbits/sec    0    501 KBytes
[  5] 235.00-236.01 sec  35.4 MBytes   295 Mbits/sec    0    502 KBytes
[  5] 236.01-237.01 sec  35.4 MBytes   297 Mbits/sec    0    512 KBytes
[  5] 237.01-238.00 sec  35.0 MBytes   297 Mbits/sec    0    530 KBytes
[  5] 238.00-239.01 sec  36.5 MBytes   303 Mbits/sec    0    564 KBytes
[  5] 239.01-240.01 sec  36.5 MBytes   307 Mbits/sec    6    436 KBytes
[  5] 240.01-241.01 sec  35.1 MBytes   294 Mbits/sec    0    499 KBytes
[  5] 241.01-242.01 sec  35.2 MBytes   295 Mbits/sec    0    543 KBytes
[  5] 242.01-243.01 sec  36.8 MBytes   308 Mbits/sec    0    571 KBytes
[  5] 243.01-244.01 sec  38.0 MBytes   320 Mbits/sec   13    413 KBytes
[  5] 244.01-245.01 sec  37.9 MBytes   318 Mbits/sec    0    452 KBytes
[  5] 245.01-246.01 sec  37.7 MBytes   316 Mbits/sec    0    477 KBytes
[  5] 246.01-247.01 sec  38.2 MBytes   318 Mbits/sec    0    491 KBytes
[  5] 247.01-248.00 sec  36.7 MBytes   311 Mbits/sec    0    496 KBytes
[  5] 248.00-249.01 sec  37.2 MBytes   308 Mbits/sec    0    496 KBytes
[  5] 249.01-250.01 sec  38.0 MBytes   321 Mbits/sec    0    498 KBytes
[  5] 250.01-251.01 sec  37.3 MBytes   311 Mbits/sec    0    498 KBytes
[  5] 251.01-252.01 sec  36.0 MBytes   304 Mbits/sec    0    506 KBytes
[  5] 252.01-253.01 sec  37.8 MBytes   315 Mbits/sec    0    525 KBytes
[  5] 253.01-254.01 sec  35.8 MBytes   300 Mbits/sec    0    554 KBytes
[  5] 254.01-255.00 sec  37.9 MBytes   321 Mbits/sec    4    434 KBytes
[  5] 255.00-256.01 sec  36.1 MBytes   300 Mbits/sec    0    494 KBytes
[  5] 256.01-257.01 sec  37.7 MBytes   319 Mbits/sec    0    535 KBytes
[  5] 257.01-258.00 sec  37.8 MBytes   317 Mbits/sec    0    559 KBytes
[  5] 258.00-259.01 sec  38.0 MBytes   316 Mbits/sec    3    403 KBytes
[  5] 259.01-260.01 sec  36.8 MBytes   309 Mbits/sec    0    441 KBytes
[  5] 260.01-261.00 sec  38.4 MBytes   326 Mbits/sec    0    467 KBytes
[  5] 261.00-262.01 sec  38.1 MBytes   318 Mbits/sec    0    481 KBytes
[  5] 262.01-263.01 sec  37.5 MBytes   313 Mbits/sec    0    486 KBytes
[  5] 263.01-264.01 sec  38.3 MBytes   323 Mbits/sec    0    486 KBytes
[  5] 264.01-265.00 sec  36.0 MBytes   303 Mbits/sec    0    488 KBytes
[  5] 265.00-266.01 sec  37.7 MBytes   313 Mbits/sec    0    489 KBytes
[  5] 266.01-267.01 sec  36.8 MBytes   311 Mbits/sec    0    496 KBytes
[  5] 267.01-268.01 sec  37.3 MBytes   313 Mbits/sec    0    515 KBytes
[  5] 268.01-269.01 sec  38.2 MBytes   318 Mbits/sec    0    544 KBytes
[  5] 269.01-270.01 sec  38.3 MBytes   322 Mbits/sec    0    591 KBytes
[  5] 270.01-271.00 sec  37.5 MBytes   318 Mbits/sec   10    478 KBytes
[  5] 271.00-272.01 sec  37.8 MBytes   315 Mbits/sec    0    527 KBytes
[  5] 272.01-273.00 sec  38.8 MBytes   329 Mbits/sec    0    559 KBytes
[  5] 273.00-274.00 sec  37.8 MBytes   316 Mbits/sec    3    410 KBytes
[  5] 274.00-275.01 sec  36.4 MBytes   302 Mbits/sec    0    447 KBytes
[  5] 275.01-276.01 sec  37.8 MBytes   317 Mbits/sec    0    471 KBytes
[  5] 276.01-277.01 sec  38.3 MBytes   322 Mbits/sec    0    482 KBytes
[  5] 277.01-278.01 sec  35.0 MBytes   293 Mbits/sec    0    488 KBytes
[  5] 278.01-279.00 sec  38.0 MBytes   322 Mbits/sec    0    488 KBytes
[  5] 279.00-280.01 sec  37.8 MBytes   315 Mbits/sec    0    489 KBytes
[  5] 280.01-281.01 sec  38.8 MBytes   326 Mbits/sec    0    491 KBytes
[  5] 281.01-282.01 sec  37.5 MBytes   314 Mbits/sec    0    501 KBytes
[  5] 282.01-283.01 sec  38.1 MBytes   319 Mbits/sec    0    519 KBytes
[  5] 283.01-284.01 sec  38.1 MBytes   321 Mbits/sec    0    551 KBytes
[  5] 284.01-285.01 sec  35.8 MBytes   300 Mbits/sec    9    298 KBytes
[  5] 285.01-286.01 sec  34.2 MBytes   285 Mbits/sec    0    320 KBytes
[  5] 286.01-287.01 sec  34.2 MBytes   287 Mbits/sec    0    329 KBytes
[  5] 287.01-288.01 sec  35.0 MBytes   293 Mbits/sec    0    334 KBytes
[  5] 288.01-289.01 sec  35.7 MBytes   300 Mbits/sec    0    335 KBytes
[  5] 289.01-290.01 sec  36.4 MBytes   305 Mbits/sec    0    337 KBytes
[  5] 290.01-291.00 sec  35.4 MBytes   300 Mbits/sec    0    339 KBytes
[  5] 291.00-292.00 sec  36.2 MBytes   303 Mbits/sec    0    348 KBytes
[  5] 292.00-293.01 sec  36.7 MBytes   307 Mbits/sec    0    369 KBytes
[  5] 293.01-294.01 sec  36.8 MBytes   309 Mbits/sec    0    404 KBytes
[  5] 294.01-295.01 sec  36.8 MBytes   307 Mbits/sec    0    455 KBytes
[  5] 295.01-296.00 sec  35.6 MBytes   302 Mbits/sec    0    527 KBytes
[  5] 296.00-297.01 sec  38.5 MBytes   322 Mbits/sec   12    426 KBytes
[  5] 297.01-298.01 sec  35.6 MBytes   297 Mbits/sec    0    486 KBytes
[  5] 298.01-299.00 sec  38.2 MBytes   323 Mbits/sec    0    529 KBytes
[  5] 299.00-300.01 sec  38.3 MBytes   319 Mbits/sec    0    556 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-300.01 sec  10.6 GBytes   304 Mbits/sec  343             sender
[code]

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 4:23 pm
by yhfung
Concerning the hAP ac^2 2.4G issue, I got more results as follows.

Test condition: Only one hAP ac^2 WiFi router in the test room. The WiFi radio was moved to the highest channel 2.472GHz with 20MHz radio bandwidth. A laptop of MacBook Pro Retina 2015 connected to the router via the 2.4GHz link.

Based on the following summary, the average ping time 628ms is too long. What about yours?

--- 192.168.10.1 ping statistics ---
300 packets transmitted, 299 packets received, 0.3% packet loss
round-trip min/avg/max/stddev = 0.767/628.493/11921.971/1855.951 ms

Listing 1: hAP ac^2 2.4G ping performance
ping -t 300 192.168.10.1
PING 192.168.10.1 (192.168.10.1): 56 data bytes
64 bytes from 192.168.10.1: icmp_seq=0 ttl=64 time=0.767 ms
64 bytes from 192.168.10.1: icmp_seq=1 ttl=64 time=254.699 ms
64 bytes from 192.168.10.1: icmp_seq=2 ttl=64 time=0.872 ms
64 bytes from 192.168.10.1: icmp_seq=3 ttl=64 time=0.984 ms
64 bytes from 192.168.10.1: icmp_seq=4 ttl=64 time=36.223 ms
64 bytes from 192.168.10.1: icmp_seq=5 ttl=64 time=3.521 ms
64 bytes from 192.168.10.1: icmp_seq=6 ttl=64 time=1.082 ms
64 bytes from 192.168.10.1: icmp_seq=7 ttl=64 time=1.410 ms
64 bytes from 192.168.10.1: icmp_seq=8 ttl=64 time=3.557 ms
64 bytes from 192.168.10.1: icmp_seq=9 ttl=64 time=3.490 ms
64 bytes from 192.168.10.1: icmp_seq=10 ttl=64 time=3.415 ms
64 bytes from 192.168.10.1: icmp_seq=11 ttl=64 time=3.748 ms
64 bytes from 192.168.10.1: icmp_seq=12 ttl=64 time=0.801 ms
64 bytes from 192.168.10.1: icmp_seq=13 ttl=64 time=3.566 ms
64 bytes from 192.168.10.1: icmp_seq=14 ttl=64 time=1.044 ms
64 bytes from 192.168.10.1: icmp_seq=15 ttl=64 time=0.979 ms
64 bytes from 192.168.10.1: icmp_seq=16 ttl=64 time=1.141 ms
64 bytes from 192.168.10.1: icmp_seq=17 ttl=64 time=2.878 ms
64 bytes from 192.168.10.1: icmp_seq=18 ttl=64 time=3.435 ms
64 bytes from 192.168.10.1: icmp_seq=19 ttl=64 time=3.389 ms
64 bytes from 192.168.10.1: icmp_seq=20 ttl=64 time=8.379 ms
64 bytes from 192.168.10.1: icmp_seq=21 ttl=64 time=3.453 ms
64 bytes from 192.168.10.1: icmp_seq=22 ttl=64 time=105.113 ms
64 bytes from 192.168.10.1: icmp_seq=23 ttl=64 time=36.958 ms
64 bytes from 192.168.10.1: icmp_seq=24 ttl=64 time=3.533 ms
64 bytes from 192.168.10.1: icmp_seq=25 ttl=64 time=3.749 ms
64 bytes from 192.168.10.1: icmp_seq=26 ttl=64 time=780.509 ms
64 bytes from 192.168.10.1: icmp_seq=27 ttl=64 time=3.600 ms
64 bytes from 192.168.10.1: icmp_seq=28 ttl=64 time=0.936 ms
64 bytes from 192.168.10.1: icmp_seq=29 ttl=64 time=4.225 ms
64 bytes from 192.168.10.1: icmp_seq=30 ttl=64 time=4.545 ms
64 bytes from 192.168.10.1: icmp_seq=31 ttl=64 time=0.841 ms
64 bytes from 192.168.10.1: icmp_seq=32 ttl=64 time=0.944 ms
64 bytes from 192.168.10.1: icmp_seq=33 ttl=64 time=3.405 ms
64 bytes from 192.168.10.1: icmp_seq=34 ttl=64 time=3.256 ms
64 bytes from 192.168.10.1: icmp_seq=35 ttl=64 time=18.098 ms
64 bytes from 192.168.10.1: icmp_seq=36 ttl=64 time=3.639 ms
64 bytes from 192.168.10.1: icmp_seq=37 ttl=64 time=0.947 ms
64 bytes from 192.168.10.1: icmp_seq=38 ttl=64 time=3.122 ms
64 bytes from 192.168.10.1: icmp_seq=39 ttl=64 time=0.905 ms
64 bytes from 192.168.10.1: icmp_seq=40 ttl=64 time=73.420 ms
64 bytes from 192.168.10.1: icmp_seq=41 ttl=64 time=0.767 ms
64 bytes from 192.168.10.1: icmp_seq=42 ttl=64 time=1.419 ms
64 bytes from 192.168.10.1: icmp_seq=43 ttl=64 time=3.612 ms
64 bytes from 192.168.10.1: icmp_seq=44 ttl=64 time=0.809 ms
64 bytes from 192.168.10.1: icmp_seq=45 ttl=64 time=0.851 ms
64 bytes from 192.168.10.1: icmp_seq=46 ttl=64 time=0.848 ms
64 bytes from 192.168.10.1: icmp_seq=47 ttl=64 time=3.627 ms
64 bytes from 192.168.10.1: icmp_seq=48 ttl=64 time=839.621 ms
64 bytes from 192.168.10.1: icmp_seq=49 ttl=64 time=0.914 ms
64 bytes from 192.168.10.1: icmp_seq=50 ttl=64 time=432.966 ms
64 bytes from 192.168.10.1: icmp_seq=51 ttl=64 time=0.915 ms
64 bytes from 192.168.10.1: icmp_seq=52 ttl=64 time=0.904 ms
64 bytes from 192.168.10.1: icmp_seq=53 ttl=64 time=752.950 ms
64 bytes from 192.168.10.1: icmp_seq=54 ttl=64 time=467.707 ms
64 bytes from 192.168.10.1: icmp_seq=55 ttl=64 time=220.057 ms
64 bytes from 192.168.10.1: icmp_seq=56 ttl=64 time=0.817 ms
64 bytes from 192.168.10.1: icmp_seq=57 ttl=64 time=189.125 ms
64 bytes from 192.168.10.1: icmp_seq=58 ttl=64 time=61.821 ms
64 bytes from 192.168.10.1: icmp_seq=59 ttl=64 time=24.813 ms
64 bytes from 192.168.10.1: icmp_seq=60 ttl=64 time=2.369 ms
64 bytes from 192.168.10.1: icmp_seq=61 ttl=64 time=1.226 ms
64 bytes from 192.168.10.1: icmp_seq=62 ttl=64 time=0.888 ms
64 bytes from 192.168.10.1: icmp_seq=63 ttl=64 time=0.799 ms
64 bytes from 192.168.10.1: icmp_seq=64 ttl=64 time=1.831 ms
64 bytes from 192.168.10.1: icmp_seq=65 ttl=64 time=247.241 ms
64 bytes from 192.168.10.1: icmp_seq=66 ttl=64 time=0.856 ms
64 bytes from 192.168.10.1: icmp_seq=67 ttl=64 time=2.997 ms
64 bytes from 192.168.10.1: icmp_seq=68 ttl=64 time=3.636 ms
64 bytes from 192.168.10.1: icmp_seq=69 ttl=64 time=6.674 ms
64 bytes from 192.168.10.1: icmp_seq=70 ttl=64 time=3.709 ms
64 bytes from 192.168.10.1: icmp_seq=71 ttl=64 time=4.828 ms
64 bytes from 192.168.10.1: icmp_seq=72 ttl=64 time=21.100 ms
64 bytes from 192.168.10.1: icmp_seq=73 ttl=64 time=0.959 ms
64 bytes from 192.168.10.1: icmp_seq=74 ttl=64 time=1.077 ms
64 bytes from 192.168.10.1: icmp_seq=75 ttl=64 time=0.859 ms
64 bytes from 192.168.10.1: icmp_seq=76 ttl=64 time=0.881 ms
64 bytes from 192.168.10.1: icmp_seq=77 ttl=64 time=1.388 ms
64 bytes from 192.168.10.1: icmp_seq=78 ttl=64 time=3.555 ms
64 bytes from 192.168.10.1: icmp_seq=79 ttl=64 time=4.829 ms
64 bytes from 192.168.10.1: icmp_seq=80 ttl=64 time=3.560 ms
64 bytes from 192.168.10.1: icmp_seq=81 ttl=64 time=437.949 ms
64 bytes from 192.168.10.1: icmp_seq=82 ttl=64 time=4.745 ms
64 bytes from 192.168.10.1: icmp_seq=83 ttl=64 time=3.560 ms
64 bytes from 192.168.10.1: icmp_seq=84 ttl=64 time=6.816 ms
64 bytes from 192.168.10.1: icmp_seq=85 ttl=64 time=103.429 ms
64 bytes from 192.168.10.1: icmp_seq=86 ttl=64 time=0.854 ms
64 bytes from 192.168.10.1: icmp_seq=87 ttl=64 time=3.437 ms
64 bytes from 192.168.10.1: icmp_seq=88 ttl=64 time=32.559 ms
64 bytes from 192.168.10.1: icmp_seq=89 ttl=64 time=1.085 ms
64 bytes from 192.168.10.1: icmp_seq=90 ttl=64 time=166.090 ms
64 bytes from 192.168.10.1: icmp_seq=91 ttl=64 time=0.886 ms
64 bytes from 192.168.10.1: icmp_seq=92 ttl=64 time=1.920 ms
64 bytes from 192.168.10.1: icmp_seq=93 ttl=64 time=3.506 ms
64 bytes from 192.168.10.1: icmp_seq=94 ttl=64 time=5.409 ms
64 bytes from 192.168.10.1: icmp_seq=95 ttl=64 time=3.619 ms
64 bytes from 192.168.10.1: icmp_seq=96 ttl=64 time=0.839 ms
64 bytes from 192.168.10.1: icmp_seq=97 ttl=64 time=8.415 ms
64 bytes from 192.168.10.1: icmp_seq=98 ttl=64 time=3.570 ms
64 bytes from 192.168.10.1: icmp_seq=99 ttl=64 time=3.604 ms
64 bytes from 192.168.10.1: icmp_seq=100 ttl=64 time=0.875 ms
64 bytes from 192.168.10.1: icmp_seq=101 ttl=64 time=3.518 ms
64 bytes from 192.168.10.1: icmp_seq=102 ttl=64 time=3.491 ms
64 bytes from 192.168.10.1: icmp_seq=103 ttl=64 time=3.599 ms
64 bytes from 192.168.10.1: icmp_seq=104 ttl=64 time=31.118 ms
64 bytes from 192.168.10.1: icmp_seq=105 ttl=64 time=3.557 ms
64 bytes from 192.168.10.1: icmp_seq=106 ttl=64 time=49.857 ms
64 bytes from 192.168.10.1: icmp_seq=107 ttl=64 time=11.188 ms
64 bytes from 192.168.10.1: icmp_seq=108 ttl=64 time=3.621 ms
64 bytes from 192.168.10.1: icmp_seq=109 ttl=64 time=491.800 ms
64 bytes from 192.168.10.1: icmp_seq=110 ttl=64 time=3.500 ms
64 bytes from 192.168.10.1: icmp_seq=111 ttl=64 time=3.463 ms
64 bytes from 192.168.10.1: icmp_seq=112 ttl=64 time=3.485 ms
64 bytes from 192.168.10.1: icmp_seq=113 ttl=64 time=3.887 ms
64 bytes from 192.168.10.1: icmp_seq=114 ttl=64 time=0.812 ms
64 bytes from 192.168.10.1: icmp_seq=115 ttl=64 time=182.740 ms
64 bytes from 192.168.10.1: icmp_seq=116 ttl=64 time=3.776 ms
64 bytes from 192.168.10.1: icmp_seq=117 ttl=64 time=3.455 ms
64 bytes from 192.168.10.1: icmp_seq=118 ttl=64 time=3.544 ms
64 bytes from 192.168.10.1: icmp_seq=119 ttl=64 time=3.532 ms
64 bytes from 192.168.10.1: icmp_seq=120 ttl=64 time=69.196 ms
64 bytes from 192.168.10.1: icmp_seq=121 ttl=64 time=3.491 ms
64 bytes from 192.168.10.1: icmp_seq=122 ttl=64 time=180.061 ms
64 bytes from 192.168.10.1: icmp_seq=123 ttl=64 time=501.785 ms
64 bytes from 192.168.10.1: icmp_seq=124 ttl=64 time=3.722 ms
64 bytes from 192.168.10.1: icmp_seq=125 ttl=64 time=909.490 ms
64 bytes from 192.168.10.1: icmp_seq=126 ttl=64 time=9.995 ms
64 bytes from 192.168.10.1: icmp_seq=127 ttl=64 time=4.242 ms
64 bytes from 192.168.10.1: icmp_seq=128 ttl=64 time=6.496 ms
64 bytes from 192.168.10.1: icmp_seq=129 ttl=64 time=4.646 ms
64 bytes from 192.168.10.1: icmp_seq=130 ttl=64 time=228.661 ms
64 bytes from 192.168.10.1: icmp_seq=131 ttl=64 time=30.053 ms
64 bytes from 192.168.10.1: icmp_seq=132 ttl=64 time=3.603 ms
64 bytes from 192.168.10.1: icmp_seq=133 ttl=64 time=3.511 ms
64 bytes from 192.168.10.1: icmp_seq=134 ttl=64 time=6.221 ms
64 bytes from 192.168.10.1: icmp_seq=135 ttl=64 time=114.242 ms
Request timeout for icmp_seq 136
Request timeout for icmp_seq 137
64 bytes from 192.168.10.1: icmp_seq=136 ttl=64 time=2753.144 ms
64 bytes from 192.168.10.1: icmp_seq=137 ttl=64 time=1751.753 ms
64 bytes from 192.168.10.1: icmp_seq=138 ttl=64 time=746.581 ms
64 bytes from 192.168.10.1: icmp_seq=139 ttl=64 time=2012.453 ms
64 bytes from 192.168.10.1: icmp_seq=140 ttl=64 time=1007.541 ms
64 bytes from 192.168.10.1: icmp_seq=141 ttl=64 time=711.815 ms
64 bytes from 192.168.10.1: icmp_seq=142 ttl=64 time=2165.397 ms
Request timeout for icmp_seq 145
Request timeout for icmp_seq 146
Request timeout for icmp_seq 147
Request timeout for icmp_seq 148
Request timeout for icmp_seq 149
Request timeout for icmp_seq 150
64 bytes from 192.168.10.1: icmp_seq=143 ttl=64 time=9034.264 ms
64 bytes from 192.168.10.1: icmp_seq=144 ttl=64 time=8029.018 ms
64 bytes from 192.168.10.1: icmp_seq=145 ttl=64 time=7023.797 ms
64 bytes from 192.168.10.1: icmp_seq=146 ttl=64 time=6018.617 ms
64 bytes from 192.168.10.1: icmp_seq=147 ttl=64 time=5013.384 ms
64 bytes from 192.168.10.1: icmp_seq=148 ttl=64 time=7689.090 ms
64 bytes from 192.168.10.1: icmp_seq=149 ttl=64 time=6683.868 ms
64 bytes from 192.168.10.1: icmp_seq=150 ttl=64 time=5678.695 ms
64 bytes from 192.168.10.1: icmp_seq=151 ttl=64 time=4673.463 ms
Request timeout for icmp_seq 160
Request timeout for icmp_seq 161
Request timeout for icmp_seq 162
64 bytes from 192.168.10.1: icmp_seq=152 ttl=64 time=11921.971 ms
64 bytes from 192.168.10.1: icmp_seq=153 ttl=64 time=10916.761 ms
64 bytes from 192.168.10.1: icmp_seq=154 ttl=64 time=9912.151 ms
64 bytes from 192.168.10.1: icmp_seq=155 ttl=64 time=8908.622 ms
64 bytes from 192.168.10.1: icmp_seq=156 ttl=64 time=7906.533 ms
64 bytes from 192.168.10.1: icmp_seq=157 ttl=64 time=6901.273 ms
64 bytes from 192.168.10.1: icmp_seq=158 ttl=64 time=6861.443 ms
64 bytes from 192.168.10.1: icmp_seq=159 ttl=64 time=5856.218 ms
64 bytes from 192.168.10.1: icmp_seq=160 ttl=64 time=4850.955 ms
64 bytes from 192.168.10.1: icmp_seq=161 ttl=64 time=3845.786 ms
64 bytes from 192.168.10.1: icmp_seq=162 ttl=64 time=2840.555 ms
64 bytes from 192.168.10.1: icmp_seq=163 ttl=64 time=1835.400 ms
64 bytes from 192.168.10.1: icmp_seq=164 ttl=64 time=1743.649 ms
64 bytes from 192.168.10.1: icmp_seq=165 ttl=64 time=2376.210 ms
64 bytes from 192.168.10.1: icmp_seq=166 ttl=64 time=1371.329 ms
64 bytes from 192.168.10.1: icmp_seq=167 ttl=64 time=1751.956 ms
64 bytes from 192.168.10.1: icmp_seq=168 ttl=64 time=1509.335 ms
64 bytes from 192.168.10.1: icmp_seq=169 ttl=64 time=1211.865 ms
64 bytes from 192.168.10.1: icmp_seq=170 ttl=64 time=692.211 ms
64 bytes from 192.168.10.1: icmp_seq=171 ttl=64 time=489.062 ms
64 bytes from 192.168.10.1: icmp_seq=172 ttl=64 time=1187.254 ms
64 bytes from 192.168.10.1: icmp_seq=173 ttl=64 time=275.488 ms
64 bytes from 192.168.10.1: icmp_seq=174 ttl=64 time=3.493 ms
64 bytes from 192.168.10.1: icmp_seq=175 ttl=64 time=42.928 ms
64 bytes from 192.168.10.1: icmp_seq=176 ttl=64 time=0.818 ms
64 bytes from 192.168.10.1: icmp_seq=177 ttl=64 time=3.206 ms
64 bytes from 192.168.10.1: icmp_seq=178 ttl=64 time=174.734 ms
64 bytes from 192.168.10.1: icmp_seq=179 ttl=64 time=1.335 ms
64 bytes from 192.168.10.1: icmp_seq=180 ttl=64 time=1106.340 ms
64 bytes from 192.168.10.1: icmp_seq=181 ttl=64 time=196.663 ms
64 bytes from 192.168.10.1: icmp_seq=182 ttl=64 time=893.365 ms
64 bytes from 192.168.10.1: icmp_seq=183 ttl=64 time=431.204 ms
64 bytes from 192.168.10.1: icmp_seq=184 ttl=64 time=3.579 ms
64 bytes from 192.168.10.1: icmp_seq=185 ttl=64 time=0.812 ms
64 bytes from 192.168.10.1: icmp_seq=186 ttl=64 time=0.829 ms
64 bytes from 192.168.10.1: icmp_seq=187 ttl=64 time=1.567 ms
64 bytes from 192.168.10.1: icmp_seq=188 ttl=64 time=1.590 ms
64 bytes from 192.168.10.1: icmp_seq=189 ttl=64 time=59.312 ms
64 bytes from 192.168.10.1: icmp_seq=190 ttl=64 time=699.756 ms
64 bytes from 192.168.10.1: icmp_seq=191 ttl=64 time=665.853 ms
64 bytes from 192.168.10.1: icmp_seq=192 ttl=64 time=0.973 ms
64 bytes from 192.168.10.1: icmp_seq=193 ttl=64 time=3.663 ms
64 bytes from 192.168.10.1: icmp_seq=194 ttl=64 time=6.259 ms
64 bytes from 192.168.10.1: icmp_seq=195 ttl=64 time=1.368 ms
64 bytes from 192.168.10.1: icmp_seq=196 ttl=64 time=0.851 ms
64 bytes from 192.168.10.1: icmp_seq=197 ttl=64 time=0.828 ms
64 bytes from 192.168.10.1: icmp_seq=198 ttl=64 time=3.978 ms
64 bytes from 192.168.10.1: icmp_seq=199 ttl=64 time=3.386 ms
64 bytes from 192.168.10.1: icmp_seq=200 ttl=64 time=49.769 ms
64 bytes from 192.168.10.1: icmp_seq=201 ttl=64 time=1.830 ms
64 bytes from 192.168.10.1: icmp_seq=202 ttl=64 time=1.267 ms
64 bytes from 192.168.10.1: icmp_seq=203 ttl=64 time=1.102 ms
64 bytes from 192.168.10.1: icmp_seq=204 ttl=64 time=0.999 ms
64 bytes from 192.168.10.1: icmp_seq=205 ttl=64 time=3.558 ms
64 bytes from 192.168.10.1: icmp_seq=206 ttl=64 time=152.025 ms
64 bytes from 192.168.10.1: icmp_seq=207 ttl=64 time=0.811 ms
64 bytes from 192.168.10.1: icmp_seq=208 ttl=64 time=2.022 ms
64 bytes from 192.168.10.1: icmp_seq=209 ttl=64 time=149.067 ms
64 bytes from 192.168.10.1: icmp_seq=210 ttl=64 time=2.986 ms
64 bytes from 192.168.10.1: icmp_seq=211 ttl=64 time=46.411 ms
64 bytes from 192.168.10.1: icmp_seq=212 ttl=64 time=0.847 ms
64 bytes from 192.168.10.1: icmp_seq=213 ttl=64 time=19.442 ms
64 bytes from 192.168.10.1: icmp_seq=214 ttl=64 time=421.283 ms
64 bytes from 192.168.10.1: icmp_seq=215 ttl=64 time=6.336 ms
64 bytes from 192.168.10.1: icmp_seq=216 ttl=64 time=0.795 ms
64 bytes from 192.168.10.1: icmp_seq=217 ttl=64 time=4.342 ms
64 bytes from 192.168.10.1: icmp_seq=218 ttl=64 time=6.283 ms
64 bytes from 192.168.10.1: icmp_seq=219 ttl=64 time=383.912 ms
64 bytes from 192.168.10.1: icmp_seq=220 ttl=64 time=509.648 ms
64 bytes from 192.168.10.1: icmp_seq=221 ttl=64 time=31.643 ms
64 bytes from 192.168.10.1: icmp_seq=222 ttl=64 time=3.544 ms
64 bytes from 192.168.10.1: icmp_seq=223 ttl=64 time=3.549 ms
64 bytes from 192.168.10.1: icmp_seq=224 ttl=64 time=0.858 ms
64 bytes from 192.168.10.1: icmp_seq=225 ttl=64 time=835.787 ms
64 bytes from 192.168.10.1: icmp_seq=226 ttl=64 time=0.877 ms
64 bytes from 192.168.10.1: icmp_seq=227 ttl=64 time=0.850 ms
64 bytes from 192.168.10.1: icmp_seq=228 ttl=64 time=0.927 ms
64 bytes from 192.168.10.1: icmp_seq=229 ttl=64 time=2.135 ms
64 bytes from 192.168.10.1: icmp_seq=230 ttl=64 time=5.044 ms
64 bytes from 192.168.10.1: icmp_seq=231 ttl=64 time=1.033 ms
64 bytes from 192.168.10.1: icmp_seq=232 ttl=64 time=3.468 ms
64 bytes from 192.168.10.1: icmp_seq=233 ttl=64 time=338.178 ms
64 bytes from 192.168.10.1: icmp_seq=234 ttl=64 time=199.298 ms
64 bytes from 192.168.10.1: icmp_seq=235 ttl=64 time=1.584 ms
64 bytes from 192.168.10.1: icmp_seq=236 ttl=64 time=3.580 ms
64 bytes from 192.168.10.1: icmp_seq=237 ttl=64 time=0.837 ms
64 bytes from 192.168.10.1: icmp_seq=238 ttl=64 time=5.034 ms
64 bytes from 192.168.10.1: icmp_seq=239 ttl=64 time=3.690 ms
64 bytes from 192.168.10.1: icmp_seq=240 ttl=64 time=414.939 ms
64 bytes from 192.168.10.1: icmp_seq=241 ttl=64 time=3.479 ms
64 bytes from 192.168.10.1: icmp_seq=242 ttl=64 time=50.057 ms
64 bytes from 192.168.10.1: icmp_seq=243 ttl=64 time=3.679 ms
64 bytes from 192.168.10.1: icmp_seq=244 ttl=64 time=509.037 ms
64 bytes from 192.168.10.1: icmp_seq=245 ttl=64 time=1.477 ms
64 bytes from 192.168.10.1: icmp_seq=246 ttl=64 time=3.552 ms
64 bytes from 192.168.10.1: icmp_seq=247 ttl=64 time=3.498 ms
64 bytes from 192.168.10.1: icmp_seq=248 ttl=64 time=4.938 ms
64 bytes from 192.168.10.1: icmp_seq=249 ttl=64 time=162.862 ms
64 bytes from 192.168.10.1: icmp_seq=250 ttl=64 time=8.507 ms
64 bytes from 192.168.10.1: icmp_seq=251 ttl=64 time=3.643 ms
64 bytes from 192.168.10.1: icmp_seq=252 ttl=64 time=66.019 ms
64 bytes from 192.168.10.1: icmp_seq=253 ttl=64 time=5.769 ms
64 bytes from 192.168.10.1: icmp_seq=254 ttl=64 time=3.480 ms
64 bytes from 192.168.10.1: icmp_seq=255 ttl=64 time=198.763 ms
64 bytes from 192.168.10.1: icmp_seq=256 ttl=64 time=6.971 ms
64 bytes from 192.168.10.1: icmp_seq=257 ttl=64 time=3.840 ms
64 bytes from 192.168.10.1: icmp_seq=258 ttl=64 time=636.610 ms
64 bytes from 192.168.10.1: icmp_seq=259 ttl=64 time=956.080 ms
64 bytes from 192.168.10.1: icmp_seq=260 ttl=64 time=113.424 ms
64 bytes from 192.168.10.1: icmp_seq=261 ttl=64 time=0.888 ms
64 bytes from 192.168.10.1: icmp_seq=262 ttl=64 time=1.157 ms
64 bytes from 192.168.10.1: icmp_seq=263 ttl=64 time=3.461 ms
64 bytes from 192.168.10.1: icmp_seq=264 ttl=64 time=3.912 ms
64 bytes from 192.168.10.1: icmp_seq=265 ttl=64 time=627.363 ms
64 bytes from 192.168.10.1: icmp_seq=266 ttl=64 time=3.550 ms
64 bytes from 192.168.10.1: icmp_seq=267 ttl=64 time=7.242 ms
64 bytes from 192.168.10.1: icmp_seq=268 ttl=64 time=6.662 ms
64 bytes from 192.168.10.1: icmp_seq=269 ttl=64 time=3.653 ms
64 bytes from 192.168.10.1: icmp_seq=270 ttl=64 time=1.199 ms
64 bytes from 192.168.10.1: icmp_seq=271 ttl=64 time=0.868 ms
64 bytes from 192.168.10.1: icmp_seq=272 ttl=64 time=7.732 ms
64 bytes from 192.168.10.1: icmp_seq=273 ttl=64 time=0.898 ms
64 bytes from 192.168.10.1: icmp_seq=274 ttl=64 time=69.646 ms
64 bytes from 192.168.10.1: icmp_seq=275 ttl=64 time=0.973 ms
64 bytes from 192.168.10.1: icmp_seq=276 ttl=64 time=3.811 ms
64 bytes from 192.168.10.1: icmp_seq=277 ttl=64 time=0.960 ms
64 bytes from 192.168.10.1: icmp_seq=278 ttl=64 time=594.187 ms
64 bytes from 192.168.10.1: icmp_seq=279 ttl=64 time=2.292 ms
64 bytes from 192.168.10.1: icmp_seq=280 ttl=64 time=428.283 ms
64 bytes from 192.168.10.1: icmp_seq=281 ttl=64 time=3.840 ms
64 bytes from 192.168.10.1: icmp_seq=282 ttl=64 time=3.782 ms
64 bytes from 192.168.10.1: icmp_seq=283 ttl=64 time=3.602 ms
64 bytes from 192.168.10.1: icmp_seq=284 ttl=64 time=197.312 ms
64 bytes from 192.168.10.1: icmp_seq=285 ttl=64 time=3.457 ms
64 bytes from 192.168.10.1: icmp_seq=286 ttl=64 time=35.718 ms
64 bytes from 192.168.10.1: icmp_seq=287 ttl=64 time=3.571 ms
64 bytes from 192.168.10.1: icmp_seq=288 ttl=64 time=619.798 ms
64 bytes from 192.168.10.1: icmp_seq=289 ttl=64 time=3.510 ms
64 bytes from 192.168.10.1: icmp_seq=290 ttl=64 time=3.611 ms
64 bytes from 192.168.10.1: icmp_seq=291 ttl=64 time=3.610 ms
64 bytes from 192.168.10.1: icmp_seq=292 ttl=64 time=3.526 ms
64 bytes from 192.168.10.1: icmp_seq=293 ttl=64 time=3.602 ms
64 bytes from 192.168.10.1: icmp_seq=294 ttl=64 time=4.418 ms
64 bytes from 192.168.10.1: icmp_seq=295 ttl=64 time=3.821 ms
64 bytes from 192.168.10.1: icmp_seq=296 ttl=64 time=3.620 ms
64 bytes from 192.168.10.1: icmp_seq=297 ttl=64 time=3.668 ms
64 bytes from 192.168.10.1: icmp_seq=298 ttl=64 time=10.568 ms

--- 192.168.10.1 ping statistics ---
300 packets transmitted, 299 packets received, 0.3% packet loss
round-trip min/avg/max/stddev = 0.767/628.493/11921.971/1855.951 ms

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 4:43 pm
by Traveller
As seen in Listing 1, the results are very satisfactory and the Retr count is 612, which may be the combination of two hAP ac^2 routers. This reading is acceptable.
But I see one reduction of bandwidth in your table. It's better than it was, but worse than other WiFi devices. I received similar results on my mobile phone. 10-20 GB should be transmitted without a single reduction on 5 GHz and a distance of 1 meter.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 4:49 pm
by yhfung
I am sorry that I did not include the test environment for the test result you saw. In fact, there was a wall in between the two routers. They were about 5m apart.

YH

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 4:52 pm
by Traveller
In fact, there was a wall in between the two routers. They were about 5m apart.
Oh, for such conditions it's great results :).

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 4:53 pm
by squeeze
Given you have now shown you are in a noisy setting for 2.4GHz and are effectively testing stability rather than peak performance, have you

  • disabled auto-channel selection and used a WiFi analyzer to pick from 1,6,11,(14) channels?
  • use only 20MHz channel width
  • disabled a/b/g protocols

If so, then the final thing you can do is lower the transmit power as low as possible, preferably until the connection fails, then raise it back up just above that. Then test again. If stability does not return, then you know for sure it has nothing to do with interference issues (at least none that you as a consumer have to worry about).

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 5:03 pm
by Traveller
Given you have now shown you are in a noisy setting for 2.4GHz
It's for me? I tested AC 5GHz. When scanning hap ac ^ 2 did not find any transmitters 5 GHz near.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 5:07 pm
by yhfung
squeeze,

Many thanks for your advice.

I do not know the 2.4GHz WiFi problem came my side or something else. I need to carry out more tests as per your information/suggestions. However, the current release candidate of rc5 could resolve our 5GHz ac problem. It seems that there are some compatibility issues from other's members. If you are one of them, please send your findings to the Support with the details such that they can help you to resolve the issue.

YH

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 5:13 pm
by squeeze
Given you have now shown you are in a noisy setting for 2.4GHz
It's for me? I tested AC 5GHz. When scanning hap ac ^ 2 did not find any transmitters 5 GHz near.

Please note I was replying to yhfung, the OP, and talking exclusively about 2.4GHz.

However, the current release candidate of rc5 could resolve our 5GHz ac problem. It seems that there are some compatibility issues from other's members. If you are one of them, please send your findings to the Support with the details such that they can help you to resolve the issue.

I have not done any rc5 testing. I will test with 5GHz later.

I was just trying to help you with your 2.4GHz testing.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 5:49 pm
by morph1
for those, like me, that don't like looking up cross references (sorry for that, my previous thread was closed):
all measurements taken at 5180MHz, Channel width is the number next to the product name.
Laptop - WiFi - Router - WiFi - Device
x - axis is ping reponse time in [ms]
by linux "ping x.x.x.x -i 0.01 -c 60000"
photo_2018-04-26_16-45-02.jpg
my colleague updated the plots from the other thread with added data of rc5.
The number of pings >10ms was reduced, but still there are many reponses with very long response times.

to show this he also created an overview
photo_2018-04-26_16-41-21.jpg

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 6:00 pm
by mozerd
hAP ac2 running firmware version 6.43rc5 on the 5G network

using windows 10 file copy via file explorer --- 2.8 GB file from/to Synology NAS connected via Ethernet port from/to Acer Aspire E17 as wireless client
OS Windows 10 Home edition version 1803 build 17134.1
wireless NIC: Qualcomm Atheros QCA9377 Wireless Network Adapter

Distance from hAPac2: 7 meters

200 Mbps consistent in both directions and repeatable 5 times

IMO this is very nice result for 2 stream performance.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 6:20 pm
by yhfung
morph1,

I do not know whether you have upgraded the routerboard firmware as well (under system->routerboard tab). Based on my test results, I did not see many ping time longer than 100ms. You may refer to the previous post, as shown in Listing 2 of viewtopic.php?f=7&t=132648&p=657633&sid ... 87#p657416.

YH

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 6:40 pm
by morph1
I do not know whether you have upgraded the routerboard firmware as well (under system->routerboard tab)
what do you mean by "upgrading the routerboard"?
I installed the rc5 firmware as described by MikroTik using Winbox.
Anything else i have to upgrade besides the firmware of the device?

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 6:56 pm
by yottabit
I do not know whether you have upgraded the routerboard firmware as well (under system->routerboard tab)
what do you mean by "upgrading the routerboard"?
I installed the rc5 firmware as described by MikroTik using Winbox.
Anything else i have to upgrade besides the firmware of the device?
RouterOS is the software. You upgrade that first. Then you upgrade the Routerboard firmware to the version bundled with the software. System -> Routerboard -> Upgrade.

Sent from my Pixel XL using Tapatalk


Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 7:05 pm
by morph1
thanks for the clarification.
actually since we decided not to use this device i'm not sure i will spend more time with this issue.
good luck everybody!

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 8:31 pm
by squeeze
morph1,

If you are still here, can you tell us the models of the competitors you were comparing to or at least whether they were routers or APs. APs can have quite different antenna design ...

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 8:38 pm
by morph1
morph1,

If you are still here, can you tell us the models of the competitors you were comparing to or at least whether they were routers or APs. APs can have quite different antenna design ...
of course. i just didn't include this information because i didn't wanted to start any discussions about other brands and models here :)

Ubiquiti was UAP-AC-Pro (AP only, actually just used as golden standard and because thats our in-house-infrastructure)
TPLink was TL-WR902AC
and Linksys was EA-6200 (good old boy)

Since it bugs me on a personal level, i will perform the routerboard update tomorrow when i'm back in the office and will give it another try.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Apr 26, 2018 10:03 pm
by JasonZZR
Surely there is a way for a Check Box to Be Added on the Check for Updates part of Winbox that Dynamically adds a Permanently Selectable Options "Update the Router Board Firmware" at the same time as the ROS Software is ( Release Candidate or Stable Etc ) updated ( may or may not require two reboots to achieve ) his Could also pull back and dsisplay that the Board Firmware was out of date or a newer version would be available at next boot

Also if the Options in Winbox to display CPU , Uptime etc or in the Banner Showing the Connected Device and Installed ROS Version could also show the Board Firmware Version and Highlight that it may be update that would be helpful .

Cheers Jason

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Fri Apr 27, 2018 2:38 am
by vecernik87
Anyway, many thanks for your advice.
No worries mate :) Just one real example of all possible issues:
2018-04-10_1411_2ghz_wifi.png
This is an screenshot from my spectral scan during iPerf test. X axis is frequency, Y axis is time. Color shows strength of radio waves (according to the legend on left side). You can see that wireless communication became intense at -15:00 mark and continued for approximately two minutes.
The bandwidth was set up for 20MHz on channel 11 (center freq 2462, whole band 2451-2473) but it is clearly visible that whole 2.4GHz band was affected including channel 1. Many people believe that spacing like 1/6/11 means zero interference. Well, nope...
And that is just WiFi. Now add non-WiFi sources like Bluetooth, microwaves, wireless kb/mouses, unshielded power supplies and power generators... it is actually miracle that WiFi on 2.4GHz still works in this world!

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Fri Apr 27, 2018 3:40 am
by yhfung
vecernik87,

After having read your reply about the spectral scan and browse from the Internet, I found that there is a tool call Dude developed and distributed by MikroTik for free. In the past I have run the routerboard-based spectral scan but did not give much information except giving which frequency less congested.

Since I am a newbie of Dude tool, I do not know how to start with after installing Dude client on my MacOS via WINE programme.

As per your information, Dube-based spectral scan is a great tool. There is no clean 2.4GHz in the world!!! They are interfered to each other.

YH

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Fri Apr 27, 2018 4:51 am
by yottabit
Surely there is a way for a Check Box to Be Added on the Check for Updates part of Winbox that Dynamically adds a Permanently Selectable Options "Update the Router Board Firmware" at the same time as the ROS Software is ( Release Candidate or Stable Etc ) updated ( may or may not require two reboots to achieve ) his Could also pull back and dsisplay that the Board Firmware was out of date or a newer version would be available at next boot

Also if the Options in Winbox to display CPU , Uptime etc or in the Banner Showing the Connected Device and Installed ROS Version could also show the Board Firmware Version and Highlight that it may be update that would be helpful .

Cheers Jason
This latest release of RouterOS does include the auto-firmware-upgrade feature, at long last! But it's not enabled by default. And even when enabled, it seems an extra (manual) reboot is required. I wish it would just reboot the router twice: first for software update, be and second to enact the upgraded firmware.

Sent from my Pixel XL using Tapatalk


Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Fri Apr 27, 2018 5:09 am
by squeeze
Can you stop bumping the thread about completely unrelated issues, please. Some people receive a lot of notifications, including via email. Keep it specific to the hAP ac2 WiFi issues.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Fri Apr 27, 2018 8:03 am
by yhfung
Based on the presented results, the 5GHz WiFi was resolved as far as for my devices. However, I still have problems with 2.4GHz. How about yours? Do you have any problems with your 2.4GHz on hAP ac^2?

YH

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Fri Apr 27, 2018 8:09 am
by pepek
So OK, finally made my own quick test.

Test setup - empty config, all ETH and both wlans in bridge, DHCP client on bridge. Dell Precision 7520 with intel 8265. Setup in office - 5G almost empty, 2G with a lot of networks.

Used btest.exe (no link for this on MT download page!) against ip assigned to hAP ac^2 by DHCP
2G (40mhz)
Receive 110mbps
Send 170mbps
Ping not very stable

5G (80mhz)
Receive 330
Send 315
Ping mostly OK, sometimes with one long

Then I wanted to verify these speeds by file copy test from/to SMB share and all speeds were approximately the same. Except for one - 2,4GHz file upload from notebook to server showed 220mbps! Not rock stable, but still with high average! Peaks were about 80% usage of theoretical 300mbps maximum. In noisy environment. This is GREAT.

According to real 2,4GHz upload speed:
Download has half speed - it could be doubled.
Is it possible to get 5G from 300mbps to 500mbps reachable by Mikrotik staff? Or at least 400+?
Ping stability should be improved.

Get 2G Up/Down to 200+ and 5G to 400+ with stable ping and I will buy a lot of hAP ac^2 devices. There will be no other option for home AP than this one.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G (not yet for 2.4GHz) and 5G WiFi

Posted: Fri Apr 27, 2018 8:18 am
by yhfung
Using btest.exe will never let you have 400+, it is limited to 3xx (around 330mbps) as confirmed in my previous test results. Try to use iperf3 if you want higher throughput.

YH

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G (not yet for 2.4GHz) and 5G WiFi

Posted: Fri Apr 27, 2018 8:27 am
by pepek
Now, SMB 5G Up was better...
Image

5G Down is also slower, same as 2G
Image

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G (not yet for 2.4GHz) and 5G WiFi

Posted: Fri Apr 27, 2018 12:53 pm
by antonsb
Please try to compare SMB results with cable to check if it's not limited somewhere else.
For iperf3 please add -P 10 flag at the end of command to run several parallel streams

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G (not yet for 2.4GHz) and 5G WiFi

Posted: Sat Apr 28, 2018 6:19 am
by yhfung
I am still having the following problems in 2.4GHz on hAP ac^2.

1. Ping time fluctuates a lot and sometime is very long.
2. The transfer rate is around 50Mbps, never go beyond 100Mbps.

How about yours in these figures (ping time and transfer rate)?

If I compared the following link, perhaps, the current 2.4GHz performance is the best that MikroTik can achieve.

https://www.anandtech.com/show/7127/the ... 1ac-wifi/2

YH

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G (not yet for 2.4GHz) and 5G WiFi

Posted: Sat Apr 28, 2018 7:43 am
by yhfung
I know the way to improve the 2.4GHz performance. The following things that you may consider to deploy.

1. Use 802.11n only
2. Use Channel bandwidth 20MHz
3. Of course select the less and better channel using Android WiFi Analyzer or MikroTik Spectral Scan

The following log, shown in Listing 2, is iperf3 downstream test which I am interested in. I believe that this the best downlsteam test to my MacBook Pro. Please note the Retr count is reduced at least by two.

If MikroTik Team finds any means to improve it, it would be fine to all of MikroTik WiFi users.

Many thanks to all MikroTik Engineering Team Members to resolve this issue.

YH

Listing 1: Summary of the results of Listing 2.
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-300.01 sec  2.84 GBytes  81.3 Mbits/sec  526             sender
#

Listing 2: hAP ac^2 2.4G (using 802.11n, 20MHz bandwidth) iperf3 downlstream test results
Accepted connection from 192.168.55.42, port 55105
[  5] local 192.168.55.203 port 5201 connected to 192.168.55.42 port 55106
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.01   sec   881 KBytes  7.15 Mbits/sec    0   62.2 KBytes
[  5]   1.01-2.00   sec  6.21 MBytes  52.5 Mbits/sec    0    311 KBytes
[  5]   2.00-3.02   sec  10.6 MBytes  87.4 Mbits/sec   14    448 KBytes
[  5]   3.02-4.02   sec  9.69 MBytes  81.3 Mbits/sec    0    512 KBytes
[  5]   4.02-5.02   sec  10.4 MBytes  87.6 Mbits/sec    0    557 KBytes
[  5]   5.02-6.00   sec  10.1 MBytes  85.7 Mbits/sec   13    419 KBytes
[  5]   6.00-7.02   sec  8.76 MBytes  72.4 Mbits/sec    0    454 KBytes
[  5]   7.02-8.01   sec  10.3 MBytes  86.5 Mbits/sec    0    475 KBytes
[  5]   8.01-9.02   sec  2.61 MBytes  21.8 Mbits/sec    0    481 KBytes
[  5]   9.02-10.02  sec  0.00 Bytes  0.00 bits/sec  178    338 KBytes
[  5]  10.02-11.02  sec  5.72 MBytes  48.0 Mbits/sec    0    375 KBytes
[  5]  11.02-12.02  sec  5.72 MBytes  48.0 Mbits/sec    0    396 KBytes
[  5]  12.02-13.02  sec  6.28 MBytes  52.6 Mbits/sec    0    406 KBytes
[  5]  13.02-14.02  sec  6.34 MBytes  53.2 Mbits/sec    0    409 KBytes
[  5]  14.02-15.02  sec  5.10 MBytes  42.7 Mbits/sec    0    409 KBytes
[  5]  15.02-16.02  sec  6.28 MBytes  52.6 Mbits/sec    0    409 KBytes
[  5]  16.02-17.02  sec  5.72 MBytes  48.0 Mbits/sec    0    413 KBytes
[  5]  17.02-18.02  sec  6.34 MBytes  53.2 Mbits/sec    0    426 KBytes
[  5]  18.02-19.02  sec  5.65 MBytes  47.4 Mbits/sec    0    447 KBytes
[  5]  19.02-20.02  sec  6.21 MBytes  52.1 Mbits/sec    0    481 KBytes
[  5]  20.02-21.02  sec  5.65 MBytes  47.4 Mbits/sec    0    532 KBytes
[  5]  21.02-22.02  sec  5.65 MBytes  47.4 Mbits/sec    7    389 KBytes
[  5]  22.02-23.02  sec  4.97 MBytes  41.7 Mbits/sec    0    436 KBytes
[  5]  23.02-24.02  sec  5.65 MBytes  47.4 Mbits/sec    0    468 KBytes
[  5]  24.02-25.02  sec  4.35 MBytes  36.5 Mbits/sec    0    488 KBytes
[  5]  25.02-26.02  sec  5.03 MBytes  42.2 Mbits/sec    0    498 KBytes
[  5]  26.02-27.02  sec  5.59 MBytes  46.9 Mbits/sec    0    501 KBytes
[  5]  27.02-28.02  sec  5.59 MBytes  46.9 Mbits/sec    0    501 KBytes
[  5]  28.02-29.02  sec  5.65 MBytes  47.4 Mbits/sec    0    501 KBytes
[  5]  29.02-30.00  sec  6.21 MBytes  52.9 Mbits/sec    0    506 KBytes
[  5]  30.00-31.02  sec  5.59 MBytes  46.2 Mbits/sec    1    339 KBytes
[  5]  31.02-32.02  sec  5.16 MBytes  43.3 Mbits/sec    0    370 KBytes
[  5]  32.02-33.02  sec  6.90 MBytes  57.9 Mbits/sec    0    389 KBytes
[  5]  33.02-34.02  sec  8.58 MBytes  71.9 Mbits/sec    0    397 KBytes
[  5]  34.02-35.02  sec  10.4 MBytes  87.1 Mbits/sec    0    400 KBytes
[  5]  35.02-36.02  sec  10.2 MBytes  85.5 Mbits/sec    0    400 KBytes
[  5]  36.02-37.02  sec  10.1 MBytes  84.4 Mbits/sec    0    400 KBytes
[  5]  37.02-38.01  sec  10.2 MBytes  86.0 Mbits/sec    0    406 KBytes
[  5]  38.01-39.02  sec  10.3 MBytes  86.0 Mbits/sec    0    419 KBytes
[  5]  39.02-40.01  sec  10.4 MBytes  88.2 Mbits/sec    0    443 KBytes
[  5]  40.01-41.02  sec  8.95 MBytes  74.6 Mbits/sec    0    479 KBytes
[  5]  41.02-42.02  sec  9.94 MBytes  83.4 Mbits/sec    0    536 KBytes
[  5]  42.02-43.02  sec  9.76 MBytes  81.8 Mbits/sec   13    427 KBytes
[  5]  43.02-44.02  sec  10.3 MBytes  86.0 Mbits/sec    0    488 KBytes
[  5]  44.02-45.02  sec  9.20 MBytes  77.1 Mbits/sec    0    530 KBytes
[  5]  45.02-46.02  sec  9.57 MBytes  80.3 Mbits/sec    3    407 KBytes
[  5]  46.02-47.02  sec  10.7 MBytes  89.7 Mbits/sec    0    434 KBytes
[  5]  47.02-48.02  sec  10.4 MBytes  87.0 Mbits/sec    0    448 KBytes
[  5]  48.02-49.02  sec  8.89 MBytes  74.6 Mbits/sec    0    454 KBytes
[  5]  49.02-50.02  sec  9.01 MBytes  75.6 Mbits/sec    0    455 KBytes
[  5]  50.02-51.00  sec  9.45 MBytes  80.3 Mbits/sec    0    455 KBytes
[  5]  51.00-52.00  sec  10.8 MBytes  90.4 Mbits/sec    0    457 KBytes
[  5]  52.00-53.02  sec  10.7 MBytes  88.3 Mbits/sec    0    465 KBytes
[  5]  53.02-54.02  sec  10.9 MBytes  91.2 Mbits/sec    0    481 KBytes
[  5]  54.02-55.02  sec  10.4 MBytes  87.1 Mbits/sec    0    509 KBytes
[  5]  55.02-56.02  sec  10.6 MBytes  88.6 Mbits/sec    2    361 KBytes
[  5]  56.02-57.02  sec  10.9 MBytes  91.2 Mbits/sec    0    420 KBytes
[  5]  57.02-58.02  sec  10.4 MBytes  87.0 Mbits/sec    0    458 KBytes
[  5]  58.02-59.02  sec  10.1 MBytes  85.0 Mbits/sec    0    482 KBytes
[  5]  59.02-60.02  sec  9.63 MBytes  80.8 Mbits/sec    0    496 KBytes
[  5]  60.02-61.02  sec  9.88 MBytes  82.9 Mbits/sec    0    502 KBytes
[  5]  61.02-62.02  sec  9.94 MBytes  83.4 Mbits/sec    0    502 KBytes
[  5]  62.02-63.02  sec  8.33 MBytes  69.9 Mbits/sec    8    379 KBytes
[  5]  63.02-64.02  sec  10.3 MBytes  86.0 Mbits/sec    0    430 KBytes
[  5]  64.02-65.02  sec  9.63 MBytes  80.8 Mbits/sec    0    465 KBytes
[  5]  65.02-66.02  sec  9.38 MBytes  78.7 Mbits/sec    0    486 KBytes
[  5]  66.02-67.02  sec  10.3 MBytes  86.0 Mbits/sec    0    498 KBytes
[  5]  67.02-68.02  sec  10.4 MBytes  87.1 Mbits/sec    0    502 KBytes
[  5]  68.02-69.02  sec  10.4 MBytes  87.0 Mbits/sec    0    502 KBytes
[  5]  69.02-70.02  sec  10.0 MBytes  83.9 Mbits/sec    0    502 KBytes
[  5]  70.02-71.02  sec  10.4 MBytes  87.6 Mbits/sec    0    506 KBytes
[  5]  71.02-72.02  sec  10.9 MBytes  91.7 Mbits/sec    0    516 KBytes
[  5]  72.02-73.02  sec  10.8 MBytes  90.7 Mbits/sec    3    378 KBytes
[  5]  73.02-74.01  sec  10.9 MBytes  92.0 Mbits/sec    0    438 KBytes
[  5]  74.01-75.02  sec  9.57 MBytes  79.6 Mbits/sec    0    481 KBytes
[  5]  75.02-76.02  sec  9.20 MBytes  77.1 Mbits/sec    0    510 KBytes
[  5]  76.02-77.02  sec  9.63 MBytes  80.8 Mbits/sec    1    354 KBytes
[  5]  77.02-78.00  sec  9.94 MBytes  84.4 Mbits/sec    0    389 KBytes
[  5]  78.00-79.02  sec  10.1 MBytes  83.4 Mbits/sec    0    410 KBytes
[  5]  79.02-80.02  sec  9.51 MBytes  79.8 Mbits/sec    0    420 KBytes
[  5]  80.02-81.02  sec  9.69 MBytes  81.3 Mbits/sec    0    424 KBytes
[  5]  81.02-82.02  sec  10.3 MBytes  86.5 Mbits/sec    0    424 KBytes
[  5]  82.02-83.02  sec  9.20 MBytes  77.1 Mbits/sec    0    424 KBytes
[  5]  83.02-84.02  sec  9.76 MBytes  81.8 Mbits/sec    0    428 KBytes
[  5]  84.02-85.02  sec  8.39 MBytes  70.4 Mbits/sec    0    440 KBytes
[  5]  85.02-86.02  sec  10.9 MBytes  91.2 Mbits/sec    0    460 KBytes
[  5]  86.02-87.02  sec  11.2 MBytes  93.8 Mbits/sec    0    494 KBytes
[  5]  87.02-88.02  sec  10.0 MBytes  83.9 Mbits/sec    0    544 KBytes
[  5]  88.02-89.02  sec  10.7 MBytes  89.7 Mbits/sec   12    437 KBytes
[  5]  89.02-90.02  sec  10.9 MBytes  91.7 Mbits/sec    0    492 KBytes
[  5]  90.02-91.03  sec  10.8 MBytes  89.3 Mbits/sec    0    530 KBytes
[  5]  91.03-92.02  sec  10.5 MBytes  89.0 Mbits/sec    7    392 KBytes
[  5]  92.02-93.02  sec  10.9 MBytes  91.7 Mbits/sec    0    428 KBytes
[  5]  93.02-94.01  sec  11.0 MBytes  92.5 Mbits/sec    0    450 KBytes
[  5]  94.01-95.01  sec  10.5 MBytes  88.0 Mbits/sec    0    461 KBytes
[  5]  95.01-96.02  sec  6.59 MBytes  55.1 Mbits/sec    0    465 KBytes
[  5]  96.02-97.02  sec  10.1 MBytes  85.0 Mbits/sec    0    465 KBytes
[  5]  97.02-98.01  sec  10.4 MBytes  88.2 Mbits/sec    0    465 KBytes
[  5]  98.01-99.02  sec  9.63 MBytes  80.3 Mbits/sec    0    469 KBytes
[  5]  99.02-100.02 sec  10.9 MBytes  91.7 Mbits/sec    0    479 KBytes
[  5] 100.02-101.02 sec  11.3 MBytes  94.9 Mbits/sec    0    499 KBytes
[  5] 101.02-102.02 sec  10.6 MBytes  88.6 Mbits/sec    0    530 KBytes
[  5] 102.02-103.02 sec  10.4 MBytes  87.6 Mbits/sec    3    428 KBytes
[  5] 103.02-104.01 sec  11.6 MBytes  98.1 Mbits/sec    0    477 KBytes
[  5] 104.01-105.02 sec  9.26 MBytes  77.2 Mbits/sec    0    508 KBytes
[  5] 105.02-106.02 sec  10.4 MBytes  87.6 Mbits/sec    0    526 KBytes
[  5] 106.02-107.02 sec  10.2 MBytes  85.5 Mbits/sec    1    475 KBytes
[  5] 107.02-108.02 sec  10.4 MBytes  87.6 Mbits/sec    0    385 KBytes
[  5] 108.02-109.02 sec  9.88 MBytes  82.9 Mbits/sec    0    407 KBytes
[  5] 109.02-110.01 sec  10.4 MBytes  88.3 Mbits/sec    0    420 KBytes
[  5] 110.01-111.02 sec  9.88 MBytes  82.2 Mbits/sec    0    424 KBytes
[  5] 111.02-112.02 sec  9.69 MBytes  81.3 Mbits/sec    0    424 KBytes
[  5] 112.02-113.02 sec  10.2 MBytes  85.5 Mbits/sec    0    424 KBytes
[  5] 113.02-114.02 sec  9.51 MBytes  79.8 Mbits/sec    0    427 KBytes
[  5] 114.02-115.02 sec  9.45 MBytes  79.2 Mbits/sec    0    437 KBytes
[  5] 115.02-116.01 sec  9.63 MBytes  81.2 Mbits/sec    0    457 KBytes
[  5] 116.01-117.02 sec  9.76 MBytes  81.4 Mbits/sec    0    488 KBytes
[  5] 117.02-118.01 sec  10.5 MBytes  88.8 Mbits/sec    0    536 KBytes
[  5] 118.01-119.02 sec  10.6 MBytes  88.4 Mbits/sec   60    427 KBytes
[  5] 119.02-120.01 sec  11.1 MBytes  94.1 Mbits/sec    0    485 KBytes
[  5] 120.01-121.02 sec  9.76 MBytes  81.2 Mbits/sec    0    526 KBytes
[  5] 121.02-122.00 sec  10.2 MBytes  86.7 Mbits/sec   10    392 KBytes
[  5] 122.00-123.02 sec  9.76 MBytes  80.7 Mbits/sec    0    428 KBytes
[  5] 123.02-124.02 sec  11.2 MBytes  93.8 Mbits/sec    0    450 KBytes
[  5] 124.02-125.02 sec  9.76 MBytes  81.8 Mbits/sec    0    460 KBytes
[  5] 125.02-126.02 sec  11.4 MBytes  95.9 Mbits/sec    0    464 KBytes
[  5] 126.02-127.01 sec  10.9 MBytes  91.4 Mbits/sec    0    464 KBytes
[  5] 127.01-128.01 sec  10.3 MBytes  86.0 Mbits/sec    0    464 KBytes
[  5] 128.01-129.02 sec  10.9 MBytes  91.6 Mbits/sec    0    468 KBytes
[  5] 129.02-130.02 sec  11.4 MBytes  95.4 Mbits/sec    0    478 KBytes
[  5] 130.02-131.02 sec  11.0 MBytes  92.3 Mbits/sec    0    499 KBytes
[  5] 131.02-132.02 sec  10.9 MBytes  91.7 Mbits/sec    0    532 KBytes
[  5] 132.02-133.02 sec  9.88 MBytes  82.8 Mbits/sec   40    411 KBytes
[  5] 133.02-134.01 sec  10.1 MBytes  85.8 Mbits/sec    0    469 KBytes
[  5] 134.01-135.01 sec  9.76 MBytes  81.6 Mbits/sec    0    518 KBytes
[  5] 135.01-136.02 sec  10.6 MBytes  88.7 Mbits/sec    2    369 KBytes
[  5] 136.02-137.02 sec  11.4 MBytes  95.4 Mbits/sec    0    399 KBytes
[  5] 137.02-138.02 sec  11.0 MBytes  92.3 Mbits/sec    0    416 KBytes
[  5] 138.02-139.02 sec  10.2 MBytes  85.5 Mbits/sec    0    424 KBytes
[  5] 139.02-140.02 sec  10.1 MBytes  85.0 Mbits/sec    0    426 KBytes
[  5] 140.02-141.01 sec  10.9 MBytes  91.8 Mbits/sec    0    426 KBytes
[  5] 141.01-142.02 sec  10.5 MBytes  87.5 Mbits/sec    0    426 KBytes
[  5] 142.02-143.02 sec  10.3 MBytes  86.5 Mbits/sec    0    433 KBytes
[  5] 143.02-144.02 sec  9.45 MBytes  79.2 Mbits/sec    0    445 KBytes
[  5] 144.02-145.02 sec  8.95 MBytes  75.1 Mbits/sec    0    469 KBytes
[  5] 145.02-146.02 sec  10.1 MBytes  85.0 Mbits/sec    0    509 KBytes
[  5] 146.02-147.02 sec  10.8 MBytes  90.2 Mbits/sec    0    567 KBytes
[  5] 147.02-148.00 sec  11.0 MBytes  93.4 Mbits/sec    2    444 KBytes
[  5] 148.00-149.02 sec  9.20 MBytes  76.2 Mbits/sec    0    494 KBytes
[  5] 149.02-150.02 sec  10.4 MBytes  87.6 Mbits/sec    0    530 KBytes
[  5] 150.02-151.02 sec  10.9 MBytes  91.7 Mbits/sec    0    551 KBytes
[  5] 151.02-152.02 sec  10.4 MBytes  87.6 Mbits/sec   20    411 KBytes
[  5] 152.02-153.02 sec  9.07 MBytes  76.1 Mbits/sec    0    444 KBytes
[  5] 153.02-154.02 sec  9.38 MBytes  78.7 Mbits/sec    0    461 KBytes
[  5] 154.02-155.02 sec  9.57 MBytes  80.3 Mbits/sec    0    469 KBytes
[  5] 155.02-156.02 sec  10.3 MBytes  86.0 Mbits/sec    0    472 KBytes
[  5] 156.02-157.00 sec  9.57 MBytes  81.1 Mbits/sec    0    472 KBytes
[  5] 157.00-158.02 sec  9.63 MBytes  79.9 Mbits/sec    0    472 KBytes
[  5] 158.02-159.02 sec  9.51 MBytes  79.8 Mbits/sec    0    478 KBytes
[  5] 159.02-160.01 sec  10.6 MBytes  89.2 Mbits/sec    0    491 KBytes
[  5] 160.01-161.02 sec  9.63 MBytes  80.3 Mbits/sec    0    515 KBytes
[  5] 161.02-162.02 sec  9.76 MBytes  81.8 Mbits/sec    0    551 KBytes
[  5] 162.02-163.02 sec  9.01 MBytes  75.6 Mbits/sec   19    445 KBytes
[  5] 163.02-164.02 sec  9.94 MBytes  83.4 Mbits/sec    0    492 KBytes
[  5] 164.02-165.01 sec  10.4 MBytes  87.3 Mbits/sec    0    525 KBytes
[  5] 165.01-166.02 sec  8.82 MBytes  73.8 Mbits/sec    3    390 KBytes
[  5] 166.02-167.02 sec  8.58 MBytes  71.9 Mbits/sec    0    426 KBytes
[  5] 167.02-168.01 sec  10.8 MBytes  91.4 Mbits/sec    0    443 KBytes
[  5] 168.01-169.02 sec  9.57 MBytes  79.7 Mbits/sec    0    451 KBytes
[  5] 169.02-170.02 sec  9.82 MBytes  82.4 Mbits/sec    0    452 KBytes
[  5] 170.02-171.00 sec  9.20 MBytes  78.3 Mbits/sec    0    452 KBytes
[  5] 171.00-172.02 sec  10.8 MBytes  88.9 Mbits/sec    0    452 KBytes
[  5] 172.02-173.02 sec  10.1 MBytes  84.4 Mbits/sec    0    460 KBytes
[  5] 173.02-174.01 sec  10.7 MBytes  90.2 Mbits/sec    0    472 KBytes
[  5] 174.01-175.02 sec  10.2 MBytes  84.9 Mbits/sec    0    496 KBytes
[  5] 175.02-176.02 sec  9.13 MBytes  76.6 Mbits/sec    3    375 KBytes
[  5] 176.02-177.02 sec  10.1 MBytes  85.0 Mbits/sec    0    434 KBytes
[  5] 177.02-178.02 sec  9.76 MBytes  81.8 Mbits/sec    0    475 KBytes
[  5] 178.02-179.01 sec  10.4 MBytes  88.0 Mbits/sec    0    502 KBytes
[  5] 179.01-180.02 sec  9.94 MBytes  83.0 Mbits/sec    0    516 KBytes
[  5] 180.02-181.02 sec  7.95 MBytes  66.7 Mbits/sec    0    522 KBytes
[  5] 181.02-182.02 sec  10.4 MBytes  87.6 Mbits/sec    0    523 KBytes
[  5] 182.02-183.02 sec  9.63 MBytes  80.8 Mbits/sec    0    523 KBytes
[  5] 183.02-184.02 sec  10.7 MBytes  89.7 Mbits/sec    0    525 KBytes
[  5] 184.02-185.01 sec  10.0 MBytes  84.6 Mbits/sec    3    380 KBytes
[  5] 185.01-186.02 sec  9.51 MBytes  79.1 Mbits/sec    0    440 KBytes
[  5] 186.02-187.02 sec  9.57 MBytes  80.3 Mbits/sec    0    482 KBytes
[  5] 187.02-188.02 sec  10.2 MBytes  85.5 Mbits/sec    0    509 KBytes
[  5] 188.02-189.02 sec  8.95 MBytes  75.1 Mbits/sec    5    380 KBytes
[  5] 189.02-190.02 sec  9.76 MBytes  81.8 Mbits/sec    0    411 KBytes
[  5] 190.02-191.02 sec  8.95 MBytes  75.1 Mbits/sec    0    430 KBytes
[  5] 191.02-192.01 sec  10.3 MBytes  87.0 Mbits/sec    0    437 KBytes
[  5] 192.01-193.02 sec  9.13 MBytes  76.2 Mbits/sec    0    440 KBytes
[  5] 193.02-194.02 sec  9.07 MBytes  76.1 Mbits/sec    0    440 KBytes
[  5] 194.02-195.02 sec  9.01 MBytes  75.6 Mbits/sec    1    313 KBytes
[  5] 195.02-196.02 sec  9.88 MBytes  82.9 Mbits/sec    0    334 KBytes
[  5] 196.02-197.02 sec  8.39 MBytes  70.4 Mbits/sec    0    345 KBytes
[  5] 197.02-198.01 sec  10.3 MBytes  86.7 Mbits/sec    0    349 KBytes
[  5] 198.01-199.02 sec  8.08 MBytes  67.6 Mbits/sec    0    349 KBytes
[  5] 199.02-200.02 sec  10.2 MBytes  85.5 Mbits/sec    0    349 KBytes
[  5] 200.02-201.02 sec  10.0 MBytes  83.9 Mbits/sec    0    354 KBytes
[  5] 201.02-202.00 sec  8.26 MBytes  70.3 Mbits/sec    0    362 KBytes
[  5] 202.00-203.02 sec  9.69 MBytes  80.2 Mbits/sec    0    383 KBytes
[  5] 203.02-204.02 sec  9.82 MBytes  82.4 Mbits/sec    0    416 KBytes
[  5] 204.02-205.02 sec  7.77 MBytes  65.2 Mbits/sec    0    465 KBytes
[  5] 205.02-206.02 sec  8.76 MBytes  73.5 Mbits/sec    0    536 KBytes
[  5] 206.02-207.01 sec  10.8 MBytes  90.8 Mbits/sec   12    393 KBytes
[  5] 207.01-208.02 sec  9.13 MBytes  76.1 Mbits/sec    0    441 KBytes
[  5] 208.02-209.01 sec  10.9 MBytes  91.5 Mbits/sec    0    472 KBytes
[  5] 209.01-210.02 sec  11.4 MBytes  95.6 Mbits/sec    0    491 KBytes
[  5] 210.02-211.02 sec  10.4 MBytes  87.6 Mbits/sec    0    499 KBytes
[  5] 211.02-212.01 sec  10.8 MBytes  90.6 Mbits/sec    0    502 KBytes
[  5] 212.01-213.02 sec  9.82 MBytes  82.0 Mbits/sec    0    502 KBytes
[  5] 213.02-214.02 sec  11.0 MBytes  92.3 Mbits/sec    0    502 KBytes
[  5] 214.02-215.02 sec  10.8 MBytes  90.2 Mbits/sec    0    508 KBytes
[  5] 215.02-216.02 sec  11.4 MBytes  95.4 Mbits/sec    0    520 KBytes
[  5] 216.02-217.02 sec  10.7 MBytes  89.7 Mbits/sec    0    544 KBytes
[  5] 217.02-218.02 sec  11.0 MBytes  92.3 Mbits/sec    9    411 KBytes
[  5] 218.02-219.02 sec  10.7 MBytes  89.7 Mbits/sec    0    474 KBytes
[  5] 219.02-220.02 sec  10.6 MBytes  88.6 Mbits/sec    0    518 KBytes
[  5] 220.02-221.02 sec  9.82 MBytes  82.4 Mbits/sec    0    546 KBytes
[  5] 221.02-222.02 sec  10.6 MBytes  88.6 Mbits/sec    3    399 KBytes
[  5] 222.02-223.01 sec  11.4 MBytes  96.7 Mbits/sec    0    437 KBytes
[  5] 223.01-224.01 sec  10.3 MBytes  85.8 Mbits/sec    0    458 KBytes
[  5] 224.01-225.02 sec  10.3 MBytes  86.0 Mbits/sec    0    471 KBytes
[  5] 225.02-226.02 sec  10.5 MBytes  88.1 Mbits/sec    0    475 KBytes
[  5] 226.02-227.01 sec  11.6 MBytes  97.3 Mbits/sec    0    475 KBytes
[  5] 227.01-228.00 sec  10.6 MBytes  89.5 Mbits/sec    0    475 KBytes
[  5] 228.00-229.01 sec  11.1 MBytes  92.5 Mbits/sec    0    478 KBytes
[  5] 229.01-230.02 sec  10.3 MBytes  86.1 Mbits/sec    0    488 KBytes
[  5] 230.02-231.02 sec  10.8 MBytes  90.2 Mbits/sec    0    508 KBytes
[  5] 231.02-232.01 sec  11.7 MBytes  99.0 Mbits/sec    0    539 KBytes
[  5] 232.01-233.00 sec  10.5 MBytes  88.2 Mbits/sec    8    430 KBytes
[  5] 233.00-234.02 sec  10.6 MBytes  88.1 Mbits/sec    0    479 KBytes
[  5] 234.02-235.02 sec  10.8 MBytes  90.2 Mbits/sec    0    515 KBytes
[  5] 235.02-236.01 sec  10.6 MBytes  89.1 Mbits/sec    0    533 KBytes
[  5] 236.01-237.02 sec  8.64 MBytes  72.1 Mbits/sec    4    403 KBytes
[  5] 237.02-238.02 sec  10.5 MBytes  88.1 Mbits/sec    0    433 KBytes
[  5] 238.02-239.02 sec  10.6 MBytes  88.6 Mbits/sec    0    448 KBytes
[  5] 239.02-240.02 sec  10.9 MBytes  91.7 Mbits/sec    0    455 KBytes
[  5] 240.02-241.01 sec  11.0 MBytes  93.2 Mbits/sec    0    457 KBytes
[  5] 241.01-242.00 sec  10.4 MBytes  88.0 Mbits/sec    0    457 KBytes
[  5] 242.00-243.02 sec  10.1 MBytes  83.7 Mbits/sec    0    458 KBytes
[  5] 243.02-244.02 sec  9.57 MBytes  80.3 Mbits/sec    0    464 KBytes
[  5] 244.02-245.02 sec  10.9 MBytes  91.2 Mbits/sec    0    479 KBytes
[  5] 245.02-246.02 sec  9.76 MBytes  81.8 Mbits/sec    0    506 KBytes
[  5] 246.02-247.02 sec  9.76 MBytes  81.8 Mbits/sec   11    383 KBytes
[  5] 247.02-248.02 sec  9.07 MBytes  76.1 Mbits/sec    0    444 KBytes
[  5] 248.02-249.02 sec  9.57 MBytes  80.3 Mbits/sec    0    486 KBytes
[  5] 249.02-250.01 sec  10.1 MBytes  85.3 Mbits/sec    0    515 KBytes
[  5] 250.01-251.02 sec  9.94 MBytes  82.6 Mbits/sec    0    529 KBytes
[  5] 251.02-252.02 sec  9.69 MBytes  81.3 Mbits/sec    0    536 KBytes
[  5] 252.02-253.02 sec  9.94 MBytes  83.4 Mbits/sec    6    404 KBytes
[  5] 253.02-254.02 sec  10.1 MBytes  84.4 Mbits/sec    0    458 KBytes
[  5] 254.02-255.02 sec  9.82 MBytes  82.4 Mbits/sec    0    496 KBytes
[  5] 255.02-256.02 sec  10.3 MBytes  86.5 Mbits/sec    0    519 KBytes
[  5] 256.02-257.02 sec  10.3 MBytes  86.5 Mbits/sec    0    532 KBytes
[  5] 257.02-258.02 sec  11.1 MBytes  92.8 Mbits/sec    0    537 KBytes
[  5] 258.02-259.02 sec  10.4 MBytes  87.0 Mbits/sec    4    430 KBytes
[  5] 259.02-260.02 sec  11.0 MBytes  92.3 Mbits/sec    0    477 KBytes
[  5] 260.02-261.02 sec  10.4 MBytes  87.6 Mbits/sec    0    509 KBytes
[  5] 261.02-262.02 sec  11.1 MBytes  93.3 Mbits/sec    0    526 KBytes
[  5] 262.02-263.02 sec  10.1 MBytes  84.5 Mbits/sec    4    390 KBytes
[  5] 263.02-264.01 sec  10.0 MBytes  84.8 Mbits/sec    0    421 KBytes
[  5] 264.01-265.02 sec  10.8 MBytes  89.3 Mbits/sec    0    440 KBytes
[  5] 265.02-266.02 sec  10.1 MBytes  85.0 Mbits/sec    0    448 KBytes
[  5] 266.02-267.01 sec  11.2 MBytes  94.4 Mbits/sec    0    451 KBytes
[  5] 267.01-268.02 sec  10.3 MBytes  85.5 Mbits/sec    0    451 KBytes
[  5] 268.02-269.02 sec  11.2 MBytes  93.8 Mbits/sec    0    451 KBytes
[  5] 269.02-270.02 sec  11.1 MBytes  92.8 Mbits/sec    0    457 KBytes
[  5] 270.02-271.02 sec  10.0 MBytes  83.9 Mbits/sec    0    471 KBytes
[  5] 271.02-272.02 sec  10.1 MBytes  84.4 Mbits/sec    0    495 KBytes
[  5] 272.02-273.02 sec  10.4 MBytes  87.6 Mbits/sec    0    532 KBytes
[  5] 273.02-274.02 sec  9.57 MBytes  80.3 Mbits/sec   24    407 KBytes
[  5] 274.02-275.00 sec  11.0 MBytes  93.4 Mbits/sec    0    472 KBytes
[  5] 275.00-276.02 sec  10.3 MBytes  85.5 Mbits/sec    0    518 KBytes
[  5] 276.02-277.02 sec  10.2 MBytes  85.5 Mbits/sec    4    396 KBytes
[  5] 277.02-278.02 sec  9.69 MBytes  81.3 Mbits/sec    0    426 KBytes
[  5] 278.02-279.02 sec  11.1 MBytes  93.3 Mbits/sec    0    441 KBytes
[  5] 279.02-280.02 sec  10.9 MBytes  91.2 Mbits/sec    0    448 KBytes
[  5] 280.02-281.01 sec  11.2 MBytes  94.7 Mbits/sec    0    450 KBytes
[  5] 281.01-282.01 sec  10.7 MBytes  89.6 Mbits/sec    0    450 KBytes
[  5] 282.01-283.02 sec  9.26 MBytes  77.0 Mbits/sec    0    451 KBytes
[  5] 283.02-284.01 sec  11.6 MBytes  97.7 Mbits/sec    0    457 KBytes
[  5] 284.01-285.02 sec  10.4 MBytes  87.0 Mbits/sec    0    472 KBytes
[  5] 285.02-286.02 sec  11.7 MBytes  98.5 Mbits/sec    0    498 KBytes
[  5] 286.02-287.02 sec  9.76 MBytes  81.9 Mbits/sec    0    539 KBytes
[  5] 287.02-288.02 sec  10.3 MBytes  86.0 Mbits/sec    2    390 KBytes
[  5] 288.02-289.02 sec  9.26 MBytes  77.6 Mbits/sec    0    437 KBytes
[  5] 289.02-290.02 sec  10.1 MBytes  84.5 Mbits/sec    0    471 KBytes
[  5] 290.02-291.02 sec  10.1 MBytes  85.0 Mbits/sec    0    491 KBytes
[  5] 291.02-292.02 sec  10.4 MBytes  87.6 Mbits/sec    0    499 KBytes
[  5] 292.02-293.02 sec  10.3 MBytes  86.5 Mbits/sec    0    502 KBytes
[  5] 293.02-294.01 sec  10.5 MBytes  88.2 Mbits/sec    0    502 KBytes
[  5] 294.01-295.02 sec  9.20 MBytes  77.1 Mbits/sec    0    502 KBytes
[  5] 295.02-296.01 sec  9.94 MBytes  84.0 Mbits/sec    0    508 KBytes
[  5] 296.01-297.02 sec  10.4 MBytes  86.4 Mbits/sec    0    520 KBytes
[  5] 297.02-298.02 sec  10.3 MBytes  86.0 Mbits/sec    1    375 KBytes
[  5] 298.02-299.02 sec  9.51 MBytes  79.8 Mbits/sec    0    402 KBytes
[  5] 299.02-300.01 sec  10.3 MBytes  86.5 Mbits/sec    0    417 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-300.01 sec  2.84 GBytes  81.3 Mbits/sec  526             sender

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G (not yet for 2.4GHz) and 5G WiFi

Posted: Sat Apr 28, 2018 7:54 am
by vecernik87
I am still having the following problems in 2.4GHz on hAP ac^2.

1. Ping time fluctuates a lot and sometime is very long.
2. The transfer rate is around 50Mbps, never go beyond 100Mbps.
...
It is definitely not "best that mikrotik can achieve". I have tested my hAP ac^2 running ROS 6.42 and on 2.4GHz dual-chain 20MHz channel without interference, I was able to achieve 100-130Mbit with iperf2 tcp connection from Intel 7260 (https://ark.intel.com/products/75440/In ... ess-N-7260).
So technically, it is possible. Question which i can't answer is - why you cannot achieve this. It can be incompatibility with your device, it can be interference or just bad settings... I am sorry I cannot give you solution for this.
On monday morning, once I get to work, I can do the same test as you described in your last listing. (I have few hAP at home but due to neighbours, it is impossible to get non-interference channel on 2GHz band.)

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G (not yet for 2.4GHz) and 5G WiFi

Posted: Sat Apr 28, 2018 9:40 am
by Traveller
How about yours in these figures (ping time and transfer rate)?
2.4 GHz band is very dirty. I can not do a clean experiment. My hap ac^2 is receiving a signal from 46 stations near. Best results on channel 13, average 49 Mbit/sec. On channel 6 average 24 Mbit/sec and very unstable. Therefore, 40 MHz can not be used with hi speed. Maybe a mikrotik can improve noise immunity. But such tests as at 5 GHz, at 2.4 GHz in the house can not be carried out.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G (not yet for 2.4GHz) and 5G WiFi

Posted: Sat Apr 28, 2018 11:59 am
by Nefraim
How about yours in these figures (ping time and transfer rate)?
2.4 GHz band is very dirty. I can not do a clean experiment. My hap ac^2 is receiving a signal from 46 stations near. Best results on channel 13, average 49 Mbit/sec. On channel 6 average 24 Mbit/sec and very unstable. Therefore, 40 MHz can not be used with hi speed. Maybe a mikrotik can improve noise immunity. But such tests as at 5 GHz, at 2.4 GHz in the house can not be carried out.
If you experience different speed when changing 2.4 GHz channels from 1 to 6 or 13 is pointing to another emitter in your area. Mikrotik can try to improve transfer rates but usually in crowded scenarios, changing the channel will be the best solution afaik. This is why you get better result when you changed the channel.

You might want to try to see if another electric equipment isn't messing the 2.4 Ghz channel. My worst experience was when a stupid 2.4 GHz wireless mouse was interfering with my signal. I was blaming the router turns out it was the stupid mouse wireless receiver that was hampering may connection. If I had my wireless mouse on my connection was garbage unplugging the thing everything was fine. Try to see if you don't have any other emiters neear by.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G (not yet for 2.4GHz) and 5G WiFi

Posted: Sun Apr 29, 2018 11:12 am
by Traveller
If you experience different speed when changing 2.4 GHz channels from 1 to 6 or 13 is pointing to another emitter in your area. Mikrotik can try to improve transfer rates but usually in crowded scenarios, changing the channel will be the best solution afaik. This is why you get better result when you changed the channel.
Yes. But, for 40 MHz bandwidth i must use two channels with a distance 4 channel: 1 and 5, 6 and 2, 6 and 10 or 9 and 13. I do not have two free channels. I have free only 13 channel. On free channel hAP ac^2 transmits data without failures.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Mon Apr 30, 2018 6:21 am
by squeeze
After some testing this weekend with a Realtek USB AC adapter and a single client device, I found the following trying to get the best I could from the router without heavy tweaking of the Wireless settings:

  • 2.4 GHz: no significant performance difference from RouterOS 6.42.1 to 6.43rc5. Approx. 130 Mbit/sec download, 85 Mbit/sec upload on average.
  • 5 GHz: up to a 15% performance improvement from RouterOS 6.42.1 to 6.43rc5 (includes running the routerboard firmware upgrade). Approx. 400 Mbit/sec download, 350 Mbit/sec upload.
  • very low 10 Mbit/s UDP stream losses (<0.5%), low to very low jitter (<10ms), zero standard 1s ping packet losses, few large pings (<2%)

Test conditions:

  • low interference, according to spectral scans
  • 1m distant from the wireless client to test router
  • all tests were through the router interfaces (WAN-WLAN) using PC endpoints
  • regulatory domain TX power for 2.4 GHz, default manual-tx-power for 5 GHz

More details on the 6.43rc5 2.4 GHz band status:

  • TX/RX Signal Strength: -25 to -35 dBm
  • Signal to Noise: 70 to 80 db
  • Tx/Rx CCQ: 85% to 100%
  • Tx Rate: 300 Mbps @ 40 MHz
  • Rx Rate: jumps around a lot, anywhere from 6 Mbps to 216 Mbps@40 MHz

So, overall it appears the Mikrotik hAP ac^2 is very good at 5 GHz now for a 2x2 device, especially its upload throughput.

The 2.4 GHz performance could be more symmetrical. That upload could perhaps be improved by another 15%, if the Netgear Orbi is anything to go by.

I'm still intrigued by the 2.4 GHz latency and stability. There seem a lot of conflicting reports. But from my short (<10 minute) tests, I could not find any significant flaws.

I guess there could also be compatibility issues remaining with certain client WiFi chips, given what's happened in the last two patches.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Mon Apr 30, 2018 11:53 am
by DanielJB
1. where there is spectral congestion (eg 2.4GHz networks), I suggest using hw-protection-mode=cts-to-self and hw-protection-threshold=200 (to keep overhead low on TCP ack packets)
2. hw-protection-mode=rts-cts has higher overhead but may give better client->AP throughput if the AP transmit power is significantly higher than the client (100mW vs 30mW) as nearby APs will be able to hear the AP's 'client about to transmit' message
3. conduct spectral scanning to identify low-energy/interference bands (5GHz possible on older Mikrotik 802.11n 5GHz radios)
4. you will see better throughput if SSIDs overlap fully (eg on 2.4GHz, all are on channel 1, 6 and 11) as the collision probability would be lower
5. where there is significant congestion, reduce channel width to minimise retransmissions due to collisions. I feel Mikrotik should make channel width 20MHz default @ 2.4GHz, no?

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Mon Apr 30, 2018 2:11 pm
by alengrosevic
@squeeze: Colud you please explain to me how did you, based on your test on distance of 1m, concluded that wireless part is good? On distance of 1m, I would use cable, this is not the type of test that is used for wireless. Put distance of 5m, then 10m, and even if you can 15m between devices. Then put on wall between them. Then you will get real scenarios. Distance of 1m is maybe to see max throughtput od wireless, but if you want to see if this device is good for home/office use, then please test it diferently. In my case, RC5 did improve 5GHz performance, but this is still not finished. After using several AC devices before HAP AC2, I can tell that performance of Wireless part is still behind other competitors.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Mon Apr 30, 2018 2:30 pm
by squeeze
@squeeze: Colud you please explain to me how did you, based on your test on distance of 1m, concluded that wireless part is good? On distance of 1m, I would use cable, this is not the type of test that is used for wireless. Put distance of 5m, then 10m, and even if you can 15m between devices. Then put on wall between them. Then you will get real scenarios. Distance of 1m is maybe to see max throughtput od wireless, but if you want to see if this device is good for home/office use, then please test it diferently. In my case, RC5 did improve 5GHz performance, but this is still not finished. After using several AC devices before HAP AC2, I can tell that performance of Wireless part is still behind other competitors.

I did these basic tests because even such had awful performance in multiple aspects before. Note the thread title and past posts ...

Nor was I interested in doing any broader tests of the wireless of this device until such basics worked. There was little point wasting time on it if even the simplest context I could create produced no improvement. Now since it appears worth it, I can test further at my leisure with my use cases, which would be more difficult to compare with others anyway.

If you would like to contribute with your own "real scenarios" tests or explain what you mean by "performance of Wireless part is still behind other competitors", feel free.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Tue May 01, 2018 2:32 am
by Davis
I have noticed that (at least in my specific setup) hAP ac² together with Intel 7260 wifi card has issues with action=set-priority mangle rules.
I had used this mangle rule (rule comes from this MUM presentation) and disabling it in some cases drastically improved performance (e.g. SFTP file download improved from 1-2 MB/s to 9-10 MB/s limited by internet speed):
/ip firewall mangle
add action=set-priority chain=postrouting comment="DSCP to 802.11 WMM" \
    new-priority=from-dscp out-interface=bridge passthrough=yes
Also I have noticed that different versions of Intel drivers behave differently (e.g. 16.5.3.6 seem to offer better and more stable speeds than 18.33.12.2).

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Tue May 01, 2018 8:10 am
by pepek
To anyone (yhfung, strods?) who marked this topic as SOLVED - could you un-mark it please? This problem is not so bad as before, but it is not solved.

Today, I made another test and it showed same speeds as last time (even slightly slower) - but this time, I've disconnected all other wireless devices in office (Access points, phones, wireless mouse...). Also updated Intel WiFi driver to latest one (20.40.0.4 from February 2018 for Dual Band AC 8265). 5G is all clear, 2G gets few networks with RSSI -80dBm, my is -15dbm (in inSSIDer, registration list shows -30dBm for my client)

During this test, I've been disconnected from hAP ac^2 few times, ping is unstable and 802.11ac download is barely faster than 802.11n upload - this is not OK.
2G download speed is half of 2G upload.

SMB server I used is able to feed 1gbps ethernet.
AP setup - all interfaces in bridge, DHCP client on Bridge, band set to only-N (40mhz Ce) and only-AC (80mhz Ceee), protocol 802.11, WPS off, country Czech Republic, WPA2-PSK AES

Ping without any wireless traffic:
Reply from 192.168.7.7: bytes=32 time=12ms TTL=128
Reply from 192.168.7.7: bytes=32 time=19ms TTL=128
Reply from 192.168.7.7: bytes=32 time=16ms TTL=128
Reply from 192.168.7.7: bytes=32 time=2ms TTL=128
Reply from 192.168.7.7: bytes=32 time=2ms TTL=128
Reply from 192.168.7.7: bytes=32 time=2ms TTL=128
Reply from 192.168.7.7: bytes=32 time=2ms TTL=128
Reply from 192.168.7.7: bytes=32 time=2ms TTL=128
Reply from 192.168.7.7: bytes=32 time=2ms TTL=128
Reply from 192.168.7.7: bytes=32 time=2ms TTL=128
Reply from 192.168.7.7: bytes=32 time=2ms TTL=128
Reply from 192.168.7.7: bytes=32 time=21ms TTL=128
Reply from 192.168.7.7: bytes=32 time=24ms TTL=128
Reply from 192.168.7.7: bytes=32 time=2ms TTL=128
Reply from 192.168.7.7: bytes=32 time=283ms TTL=128
Reply from 192.168.7.7: bytes=32 time=2ms TTL=128
Reply from 192.168.7.7: bytes=32 time=2ms TTL=128
Reply from 192.168.7.7: bytes=32 time=2ms TTL=128
Reply from 192.168.7.7: bytes=32 time=2ms TTL=128
Reply from 192.168.7.7: bytes=32 time=2ms TTL=128
Reply from 192.168.7.7: bytes=32 time=2ms TTL=128
Reply from 192.168.7.7: bytes=32 time=2ms TTL=128
Reply from 192.168.7.7: bytes=32 time=2ms TTL=128
Reply from 192.168.7.7: bytes=32 time=3ms TTL=128
Reply from 192.168.7.7: bytes=32 time=18ms TTL=128
Reply from 192.168.7.7: bytes=32 time=18ms TTL=128
Going to send this info to support mail.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Tue May 01, 2018 8:28 am
by yhfung
This was not marked by me. I am not sure who marked it resolved.

By the way, have you updated your RouterOS and firmware of hAP ac^2 to at least v6.43rc5?

Now I am able to connect my remote AP station formed by an hAP ac^2 (R1) by another hAP ac^2 (R2) with two layers of concrete walls in between and both R1 and R2 are at a distance of around 10 meters. R2 was connected to AP of R1 using bridge mode. I used my MacBook Pro Retina to connect ether3 of R2. The download speed that I can achieve 168Mbps.
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-300.01 sec  5.86 GBytes   168 Mbits/sec  648             sender

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Tue May 01, 2018 8:44 am
by pepek
Yes, I have updated both - ROS and firmware to 6.43rc5

Can you rename the topic? Add "[NOT-" to the end of topic name? :)

I believe Mikrotik has their test setup with good speeds, but they have serious problems with some clients. I suspect all Intel cards. I'm able to reach 100mbps on single chain 802.11n Airlive AP with Intel client, but i have problems reaching this speed on dual-band Mikrotik. This is something Mikrotik has to work on. Probably cooperate with Intel?

Your test is 2G or 5G?

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi [Not]

Posted: Tue May 01, 2018 9:03 am
by yhfung
Already done as per your request. They were connected via 5G ac link. If you find something strange, besides putting information here, you can also sent it to the Support for help.

YH

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi [Not]

Posted: Tue May 01, 2018 9:07 am
by pepek
Mail already sent to support, received automatic reply and waiting...

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi [Not]

Posted: Tue May 01, 2018 10:07 am
by yhfung
It is very strange that I got very good results with my CHUWI notebook, in which Intel ac chip is used. However I forgot the model number. The download speed can reach over 200Mbps. Now I can get only 20Mbps. I have to find out the method to replicate the problem such that the Support Team is able to locate where gives the problem. My MacBook Pro Retina could give me 380Mbps without any difficulties.

YH

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi [Not]

Posted: Tue May 01, 2018 12:31 pm
by yhfung
Since I have four hAP ac^2, I can very whether it could happen only one of them or all of them. Based on the results obtained below, it shows clearly that the issue of download issue has not been resolved. The maximum download rate (File server (iperf3 server) -> WAN -> WLAN -> Laptop PC (MacBook Pro Retina 2015, CHUWI notebook 2017).

As seen in Listing 1, the download speed is only 25Mbps, which is much below 380Mbps of my MacBook Pro Retina 2015. MikroTik Team has to adjust system code to cater for Intel-basd AC adapters.

YH

Listing 1: Download Test on 5G hAP ac^2 with v6.43rc5 RouterOS uisng CHUWI ac interface (Intel Dual-Band Wireless-AC 3165)
Accepted connection from 192.168.55.172, port 51338
[  5] local 192.168.55.203 port 5201 connected to 192.168.55.172 port 51339
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.01   sec  3.25 MBytes  27.1 Mbits/sec    0    170 KBytes
[  5]   1.01-2.01   sec  3.00 MBytes  25.2 Mbits/sec    0    268 KBytes
[  5]   2.01-3.00   sec  3.06 MBytes  25.8 Mbits/sec    0    271 KBytes
[  5]   3.00-4.01   sec  2.76 MBytes  23.0 Mbits/sec    0    271 KBytes
[  5]   4.01-5.01   sec  2.76 MBytes  23.1 Mbits/sec    0    271 KBytes
[  5]   5.01-6.01   sec  2.76 MBytes  23.1 Mbits/sec    0    271 KBytes
[  5]   6.01-7.00   sec  3.06 MBytes  25.8 Mbits/sec    0    271 KBytes
[  5]   7.00-8.01   sec  2.76 MBytes  23.1 Mbits/sec    0    271 KBytes
[  5]   8.01-9.01   sec  2.76 MBytes  23.1 Mbits/sec    0    271 KBytes
[  5]   9.01-10.01  sec  2.76 MBytes  23.1 Mbits/sec    0    271 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.02  sec  28.9 MBytes  24.2 Mbits/sec    0             sender

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi [Not]

Posted: Tue May 01, 2018 2:27 pm
by squeeze
Listing 1: Download Test on 5G hAP ac^2 with v6.43rc5 RouterOS uisng CHUWI ac interface (Intel Dual-Band Wireless-AC 3165)
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.02  sec  28.9 MBytes  24.2 Mbits/sec    0             sender

You get no "Retr" from your TCP reverse tests? Or are you not using the "-R" iperf3 option?

Maybe you have an MTU problem. Try the following in a command or Powershell:

ping myserver –f –l 1472
ping myserver –f –l 1470
ping myserver –f –l 1460
etc.

Keep reducing the buffer size until you find one that does not bring up an error. Then set the highest you get on that specific client device with:

netsh interface ipv4 set subinterface “wi-fi” mtu=xxxx store=persistent

where xxxx = number you found.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi [Not]

Posted: Tue May 01, 2018 2:38 pm
by vecernik87
My speed grealty improved after enabling "throughput booster" in Intel's wireless settings:
device manager -> network adapters -> [your wireless card] -> advanced -> troughput booster -> enabled
I am not certain what does it do but it may have something to do with timing and colission handling. It is said, that enabling will improve your speed if equal speed for all clients is not required.
Maybe Intel simply waits too much in order to let everyone around communicate equally?

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi [Not]

Posted: Tue May 01, 2018 2:43 pm
by pepek
No, this setting was not useful for me. (maybe a little, but not significantly)

I had the same speed problems with my previous notebook - Latitude with Intel 7265. I had to replace wlan card to bcm model to get better speed with mikrotik. There was no other speed problem than with mikrotik AP. And I don't want to start changing internal devices on brand new precision...

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi [Not]

Posted: Tue May 01, 2018 4:05 pm
by yhfung
My speed grealty improved after enabling "throughput booster" in Intel's wireless settings:
device manager -> network adapters -> [your wireless card] -> advanced -> troughput booster -> enabled
I am not certain what does it do but it may have something to do with timing and colission handling. It is said, that enabling will improve your speed if equal speed for all clients is not required.
Maybe Intel simply waits too much in order to let everyone around communicate equally?
Thank you for your suggestion, I did follow your idea to adjust the settings. It turned out that the speed boosted to 220Mbps. When I disabled the settings, it still gave me 220Mbps download. It is really strange and not able to be explained. If you found it did not work, try to reboot your PC.

YH

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi [Not]

Posted: Tue May 01, 2018 4:11 pm
by yhfung
Listing 1: Download Test on 5G hAP ac^2 with v6.43rc5 RouterOS uisng CHUWI ac interface (Intel Dual-Band Wireless-AC 3165)
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.02  sec  28.9 MBytes  24.2 Mbits/sec    0             sender
You get no "Retr" from your TCP reverse tests? Or are you not using the "-R" iperf3 option?
I did use the -R option when carry out the iperf3 test. Since the test only ran for a few seconds, it did not have any packets retry for a very short period of time. In the another post, I mentioned that I could obtain higher throughput (220Mbps on Intel-based AC) by applying the suggestion given by other member.

If I have time, I shall follow your mentioned to adjust the MTU to see whether it has any improvement when the speed drops to 2xMbps.

YH

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi [Not]

Posted: Wed May 02, 2018 12:36 am
by alengrosevic
I have managed to get some improvements with AC2. I use AC2 on his stand to be installed vertically on the table (5m away from computer). Antennas (X99A Titanium MSI) of my AC wireless card were until now verticaly mounted. Today i have tried to mount them horizontally, just for testing. Signal quality has jumped instantly from 70-75% to 90-95%. Transfer is faster and more stabile (even). Connection speed between computer and router has arised from 520 mbit to 780 mbit. Maybe this information can help someone with this problem.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi [Not]

Posted: Wed May 02, 2018 2:29 am
by yottabit
The internal antennas in the hAP ac2 are 90-degrees offset. Try aligning your wireless adapter antennas the same way (1 horizontal, 1 vertical, 0/90 degrees; then +45/-45 degrees), and see if this can make further difference.

Sent from my Pixel XL using Tapatalk



Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi [Not]

Posted: Wed May 02, 2018 11:36 am
by morph1
i think you should hold your horses. You guys did improve the situation, no doubt. But wouldn't call this issue to be resolved:
photo_2018-05-02_10-35-29.jpg
We are getting somewhere, but as you can see in comparison with other products there is still some room to get even better.
Are we expecting more work on this side or is this the best that can be done?

P.S.: still using the same settings/methods as in my previous post

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Wed May 02, 2018 2:40 pm
by yhfung
morph1,

Many thanks for showing your revised chart including the firmware upgrade on hAP ac^2.

Based on your chart figures, it shows clearly that the ping time is much larger than others. Because of the poor performance in wireless section (not only on hAP ac^2 prodcuts but all MikrotiK WiFi products), there is a shift of products from MikroTik to Ubiquiti. As for me, I of course want MikroTik to improve their WiFi products as quick and as soon as possible.

In the beginning of this thread and other threads, only few people found satisfactory with their hAP ac^2 but majority of us found big problems on hAP ac^2. Why? How comes? I do believe that the WiFi testing on hAP ac^2 in MikroTik was not complete thoroughly. Nevertheless, the major issue was over but minor tuning has to be continued as some members still founds problems in their WiFi adapters.

YH

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi [Not]

Posted: Wed May 02, 2018 2:58 pm
by squeeze
P.S.: still using the same settings/methods as in my previous post

Thanks for the tests. I don't understand the new bottom scale, compared to your previous ones. Is it still 10ms pings and 60k ping count?

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi [Not]

Posted: Wed May 02, 2018 6:08 pm
by morph1
P.S.: still using the same settings/methods as in my previous post

Thanks for the tests. I don't understand the new bottom scale, compared to your previous ones. Is it still 10ms pings and 60k ping count?
uhh my bad. totally overseen that we changed the plots :) still using 10ms interval on the pings, 60k of them. so the scale is in [ms]!
The new plot style includes ALL packets.
Since we found out that there is a huge difference in the distribution of the ping responses, we decided to adapt the scale to have all of them included - instead of just the number >10ms.
Hope this helps.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi [Not]

Posted: Fri May 04, 2018 12:10 pm
by alengrosevic
The internal antennas in the hAP ac2 are 90-degrees offset. Try aligning your wireless adapter antennas the same way (1 horizontal, 1 vertical, 0/90 degrees; then +45/-45 degrees), and see if this can make further difference.

Sent from my Pixel XL using Tapatalk
I have tried all the combination but the best result was with the antennas positioned horizontally.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Sun May 06, 2018 2:58 am
by squeeze
I decided to adapt morph1's low latency testing approach, but for best case scenario, relative stability tests. These were my results.

TL;DR. Mikrotik hAP ac2 has a stability issue with 5 GHz band at 40 MHz channel width (visible also on morph1's results), but all other widths and bands performed well. The original Mikrotik hAP ac has a surprisingly disappointing 2.4 GHz band stability at 20 MHz channel width (often required for those in high interference environment and still using 2.4 GHz devices). Asus are better than I thought, almost a decade ago. :D

Box-and-Whisker Plot of 56-byte data, 10 ms interval, 60k count ICMP pings with three different devices: Mikrotik hAP ac2, Mikrotik hAP ac and Asus RT-N56U as a basic comparison.

I tested 2.4 GHz (default and 20 MHz), and 5 GHz (default, 40 Mhz and 20 MHz) with hAP ac2's wired LAN-to-WAN performance as reference. Default 5 GHz channel width on Mikrotik devices was 80 MHz.

Lower is better:
Image


Standard Box and Whisker parameters used. I don't think morph1 uses the default parameters or has a very different test environment, so cannot compare directly. Analysis tool is Matlab.

The blue box represents the traffic jitter, i.e. non-outlier traffic variation on the connection. Large box = large jitter which is worse for low latency applications.

The red crosses represent outliers that fall so far outside of the total range of the normal traffic, that they can be statistically rejected as random with a 99.3% confidence when the underlying distribution is or tends to the Normal distribution.

The ping range is carefully chosen. A maximum of 40 ms variation is normally desired for streaming applications like VoIP. A maximum of 250 ms delay for other applications like gaming. I zoomed in to 250 ms instead of 500 ms RTT because the worst offenders look the same. The actual maximums observed were sometimes much higher than that, e.g. 2000 ms (2s) for the "ac2 5GHz @ 20/40MHz" configuration and 525 ms for the "ac 2.4GHz @ 20MHz" configuration.

I could have zoomed in to show the jitter more closely for low latency differences, but given the number and distribution of outliers, that is far less important for stability.

Due to the significantly poorer performance of the "ac2 5GHz @ 20/40MHz" and "ac 2.4GHz @ 20MHz" configurations, I actually did them twice to check and took the best run of each. There was no significant difference in either standard deviation or outlier count between these alternate runs.

Test setup is the same as before:
  • PC (client) -> WLAN -> NAT -> WAN (single hop) -> PC (server). No load on WAN or its router
  • RTL8814AU WiFi chip USB 3.0 adapter connected to client PC via USB 3.0 ports
  • Mikrotik devices: regulatory domain TX power for 2.4 GHz, default manual-tx-power for 5 GHz
  • Default configuration for all devices: 2.4 GHz N-only, 5 GHz (auto)
  • Testing generated only 8.4 kB/s traffic
  • Stable link rates
  • No walls separating devices and test client
  • None of the test devices are Internet facing
  • Low interference environment, see spectral scan below. Scan not taken from test device but from the hAP ac outside of testing
  • Firmware: hAP ac2 (RouterOS + firmware: 6.43rc5), hAP ac (RouterOS + firmware: 6.41.3), Asus RT-N56U (30043807378)

Image

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Sun May 06, 2018 8:22 am
by Sheriff1972
Amazing detective work! I hope that this gives a focus to the engineering team at MT.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Sun May 06, 2018 12:45 pm
by hapi
in 5GHz with "Intel Dual Band Wireless-AC 7265" is tx rate only 54Mbit. In 2.4GHz is full speed.

Image

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Sun May 06, 2018 3:43 pm
by yhfung
in 5GHz with "Intel Dual Band Wireless-AC 7265" is tx rate only 54Mbit. In 2.4GHz is full speed.

Image
Please consider to use the actual data transfer test tool, for instance iperf3.

Regarding to your Intel AC adapter, please select something link "boost performance" under the advanced tap of your wireless adapter in the device manage of the Windows PC.

YH

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Mon May 07, 2018 4:17 am
by yhfung
squeeze,

Reading your post in this thread gives more information about the current status of MikroTik WiFi products. As per my memory in other forum, that forum members concluded that MikroTik WiFi routers or APs would not their choices due to extremely poor performance. MikroTik products are good at routing and switching but WiFi. They will choose Ubiquiti APs to work with MikroTik routers or Ubiquiti routers. If we combine their comments and the results presented by you and morph1, it shows a very clear message that the overall performance of general MikroTik WiFi routers and APs is not satisfactory. I do not know whether the MikroTik Management Team knows this WiFi weakness. In order to resolve this poor Wifi performance, MikroTik have to form a good quality plan for their WiFi router and AP products by specifying the specifications for 1) ping test, 2) throughput test, and others against several brands of WiFi devices before they are released for production and sales.

Based on my past embedded firmware development's experience, it seems the interface between WiFi routines and RouterOS is not very good. It seems that the RouterOS do not have time to respond the request from the WiFi routine due to unknown reasons. Although the WiFi performance of hAP ac^2 has already been improved significantly as compared to the very beginning when the products launched to the market, it is still not enough as compared to the other WiFi brands.

I hope MikroTik has to review the interface between the RouterOS and WiFi routines throughly. If they can shorten the ping time, I do believe that the sales of MikroTik WiFi products will be increased tremendously.

YH

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu May 10, 2018 6:08 pm
by pepek
It seems, that there will be no speed improvement in near future because of other 6.42.1 problems being fixed in current RCs...
I think that Improving this problem to "somehow usable, not totally crappy" lowered it's priority

Still no response from support on my speed issues from last week...

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu May 10, 2018 11:21 pm
by startus
hi everyone. I am sorry if this is not the right place to ask for an opinion, but I`ve decided to give a try once I`ve checked all the professional feedbacks about MK here and I felt it worths a try due to my outdated knowledge of MK products. My last and current version of RB is the 433AH that I use at home, but I want upgrade for a Giga + dual (2.4 and 5) wireless solution.

I almost bought the hAP ac^2, however after a quick search I`ve found this topic and basically I would like to have an idea if I should give a try and buy the hAP ac^2 (and wait for later improvements) or
buy the hAP AC RB962UiGS-5HacT2HnT model (I did not find a topic with problems for this model, is there any I don`t know?).

Both have the basic requirements I need and money is not a problem. Therefore I would like to know why not buy the hAP AC RB962UiGS-5HacT2HnT instead of the hAP ac^2

P.S. I just installed NAS with gigabit interface at home and I will upgrade the speed of my internet for something around 120mbs if that helps.

Thanks for the help.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Fri May 11, 2018 8:21 am
by Bivvy
Anyone know the first version of the firmware that suffered the poor WiFi problems?
We have >130 clients using HAP ac's and recently started getting complaints about poor speeds.
Bandwidth tests from the router and from PC's plugged straight into the router are all fine - it's just the WiFi that is letting us down.
As the problems started fairly recently and we've just gone through a process of upgrading all firmware to the latest stable release it seems like too much of a coincidence.
Now considering downgrading all firmware to a previous release - just need to know which one to go for...
Thanks

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Fri May 11, 2018 1:25 pm
by yhfung
Bivvy,

First of all, I guess you are talking about hAP ac^2 instead of hAP ac. They are two different models. Please note that the stable version of RouterOS on hAP ac^2 can not resolve the WiFi issues, you have to upgrade to the release candidate version of v6.43rc5 or above. Please update it to the current firmware of v6.43rc11 and you will find the speed improved significantly.

If you are not talking baout hAP ac^2, there will be other issues associated with the poor performance.

YH

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Fri May 11, 2018 2:32 pm
by yottabit
Startus: the hAP ac model has superior wireless over the hAP ac2, with higher radio power and 3 antenna chains per radio instead of only 2.

But the hAP ac2 has a much more powerful CPU, quad-core ARM v. single-core MIPS.

I am using the ac2 for my router as the ac maxes CPU for me with my QoS rules. If you're going to use QoS and need NAT routing throughput greater than 100 Mbps, I suggest you use the ac2 for routing. And I do have three ac models that I use for wireless coverage and speed (I have the wireless function disabled on my ac2).

Sent from my Pixel XL using Tapatalk



Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Fri May 11, 2018 4:36 pm
by startus
yottabit: Thank you.

Just to clarify my scenario. Most of the time I will be using my desktop + NAS in the LAN side (gigabit) alongside with 5 wireless devices (2 cell phones, 1 tablet, 1 chromecast, and 1 raspberry pi).

From time to time (maybe once in a month) I may use the LAN to make backup`s of my NAS and local video streaming from the NAS, but not constantly.

I will use in the wan side (120mbs down and 20mbs up) with few rules, portforwarding and one VPN session. I also will enable some services in the NAS to be used from the internet, like audio streaming and file sharing (cloud) etc behind the NAT.

I don`t believe I will upgrade my internet in the next 3 years, being said, If I understood correctly, the hAP would do the job right? I think the hAP ac2 can help me as well even with less wireless power. I am afraid the problem with hAP ac2 may not be solved.

Anybody else could share any thoughts?
Thank you in advance.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Fri May 11, 2018 6:24 pm
by yottabit
Since your upstream speed is so low, you'll be just fine using the hAP ac as a router, even if you implement QoS in the future.

If you ever get 100M+ upstream, *and* want QoS, you can buy a more powerful router for that when you need it (e.g., hAP ac2, or whatever its successor may be).

Sent from my Pixel XL using Tapatalk


Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Mon May 14, 2018 3:51 am
by yhfung
startus,

Both hAP ac and hAP ac^2 can fit your requirements. As the member "yottabit" has mentioned that the main benefits of using hAP ac are the higher WiFi transmission power and throughput. The downside of hAP ac is the routing power.

Since both models can fit your requirement, you may consider to choose the lowest-priced one, that is hAP ac^2.

YH

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Mon May 14, 2018 2:05 pm
by squeeze
@startus

With release candidate RouterOS software (6.43rc5+) the hAP ac2 WiFi is good enough for anything for a typical consumer - though I would not recommend its WiFi for low latency applications at the moment, e.g. gaming, but you should be using wired for that anyway in most situations.

Since your main use case is less WiFi than strong routing, this actually makes the hAP ac2 absolutely preferable over the hAP ac or any other Mikrotik SOHO device.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Mon May 14, 2018 6:50 pm
by Bivvy
@yottabit - Thanks for your reply.
We're using HAP ac's (RB962UiGS-5HacT2HnT) - until you pointed out the difference I had not realised there were two versions. Sorry if I posted in the wrong place,
In the past fortnight we've had lots of complaints
a) slow WiFi performance
b) unable to connect over the WiFi

Downgrading from 6.42.1 to 6.40.4 seemed to fix the problems, but now I'm not so convinced as one of our customers is still struggling to connect to the WiFi even after the downgrade.
I appreciate that these issues may not be directly related to the original subject of this thread.

I like Mikrotik but can't afford to spend so much effort supporting the client routers...
Ticket raised with Mikrotik tech support but no response yet (although we're still inside the 3 day SLA)

Should I try the latest release candidate?

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Mon May 14, 2018 6:57 pm
by squeeze
Release candidates are not for production in any form of business environment. Nor are they intended as a substitute for basic troubleshooting.

Since your posts have nothing whatsover to do with the hAP ac2 (it is not even similar architecture, let alone radios), please refrain from bumping this topic. Many people are monitoring this thread for updates and information exclusive to the hAP ac2 and also receive notifications via email. Please respect them and start your own separate thread.

Thank you.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Mon May 21, 2018 3:19 pm
by aidan
Early reports mentioned that the hAP ac^2 and cAP AC have a 10 dBm weaker signal than a wAP AC. Can anyone comment whether 6.43rc has also resolved this problem? Thank you.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Wed May 23, 2018 11:34 pm
by alengrosevic
RC17 is out.
*) wireless - increased stability on hAP ac^2 and cAP ac with legacy data rates;

But after upgrade I cant login thru winbox anymore. It keeps saying wrong username password. Over Web page I can login, but over winbox I cant. Strange...

EDIT: Log from device:

Time May/23/2018 22:30:04
Buffer memory
Topics
system
error
critical
Message login failure for user admin from A4:**:**:**:**:B1 via winbox

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Wed May 23, 2018 11:48 pm
by mistry7
RC17 is out.
*) wireless - increased stability on hAP ac^2 and cAP ac with legacy data rates;

But after upgrade I cant login thru winbox anymore. It keeps saying wrong username password. Over Web page I can login, but over winbox I cant. Strange...

EDIT: Log from device:

Time May/23/2018 22:30:04
Buffer memory
Topics
system
error
critical
Message login failure for user admin from A4:**:**:**:**:B1 via winbox
Could be this

winbox - improved authentication process excluding man-in-the-middle possibility (Winbox v3.14 required);

Or this:

user - all passwords are now hashed and encrypted, plaintext passwords are kept for downgrade (will be removed in later upgrades);

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu May 24, 2018 4:52 am
by squeeze
*) wireless - increased stability on hAP ac^2 and cAP ac with legacy data rates;

I am going to wait until something as fundamental as logging in works, then I'll rerun the stability tests. How exciting, I didn't expect Mikrotik to update so fast on these ARM devices!

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu May 24, 2018 6:29 am
by yhfung
I have the same login problem as the others have. However I could login the router using the old version WinBox 2.2.18.

Based on my initial test, the ping time for 5GHz seems better than the previous versions.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu May 24, 2018 8:31 am
by alengrosevic
latest available winbox for download is 3.13. I cant find 3.14.

EDIT: Thank you guys for the link! :)

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu May 24, 2018 8:41 am
by Zulu
latest available winbox for download is 3.13. I cant find 3.14.
new beta winbox https://www.mikrotik.com/download/share/winbox.exe

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu May 24, 2018 8:54 am
by yhfung
The line is at the bottom of the release announcement of v6.43rc17.

viewtopic.php?f=21&t=133420&start=100#p663507

In order to access router running this version by Winbox, please download v3.14rc Winbox loader from here:
https://www.mikrotik.com/download/share/winbox.exe

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Sun Jun 03, 2018 9:51 am
by squeeze
After some weekend performance testing of Release build 6.42.3 wrt. Mikrotik hAP ac2, I found multiple significant improvements.

TL;DR. Apart from a slight worsening in legacy 2.4 GHz @ 20 MHz wireless stability, I believe Mikrotik have largely solved the worst of the hAP ac2 wireless issues.

Using the same exact process and equipment as my Release Candidate 6.43rc5 testing (principally a RTL8814AU WiFi chip USB 3.0 adapter connected to client PC via USB 3.0 ports), here are the peak throughput results for Release 6.42.3:

  • 2.4 GHz peak download throughput: 161 Mbit/s from 135 Mbit/s = +19% improvement
  • 2.4 GHz peak upload throughput: 117 Mbit/s from 86 Mbit/s = +36% improvement (*)
  • 5.0 GHz peak download throughput: 399 Mbit/s from 396 Mbit/s = no change
  • 5.0 GHz peak upload throughput: 417 Mbit/s from 347 Mbit/s = +20% improvement

All results confirmed with three 60 second runs. Peak throughput commands used: iperf3 -N -P10 -t 60 -R (download) and iperf3 -N -P10 -t 60 (upload).

Here is a summary of the results from the stability tests for 6.42rc3:

Image

The stability test results are shown next visually in Box-and-Whisker plots of 56-byte data, 10 ms interval, 60k count ICMP pings for 6.43rc5 compared to 6.42.3. Again, I have included tests of an old Asus RT-N56U for comparison.

Lower is better:

Image

(*) Changing router orientation from horizontal to vertical caused a leap from what appeared to be a decline to 69 Mbit/s, instead to an improvement of 117 Mbit/s in 2.4 GHz upload! Changing orientation for other peak throughput tests did not significantly impact performance.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Fri Jun 08, 2018 4:22 pm
by raceboy
Hello. Maybe stupid question :) Does Device need to be upgraded also if in managed by Capsman ? Must be server with Capsman upgraded ? Thanks

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Fri Jun 29, 2018 1:34 pm
by seventh
Снимок.PNG
Clients - Roborock vacuum cleaner
Laptop Dell
Samsung Galaxy S4

Me best perfomance early, before I view the problem, about 2 months ago:
Полгига по Wi-Fi.PNG

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Sat Jun 30, 2018 4:52 am
by Dolphnmike
I manage a municipal ISP, we have had a steady flow of wifi issues. Many CX complain of doing and disconnecting wifi as well as slow speeds,
I'm already regretting or purchase of 500 hAC2 units. The pending "Broadcom compatibility firmware fix" had better be the silver bullet or we are going to look elsewhere for the next 1000 units in our Network build.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Sun Jul 01, 2018 3:49 pm
by anuser
So you're a CAPSMAN user? I also fighted against group key timeout disconnects. On the access points try:




/interface wireless set adaptive-noise-immunity=ap-and-client-mode wlan2

/interface wireless set adaptive-noise-immunity=ap-and-client-mode wlan1

/interface wireless set amsdu-limit=4096 amsdu-threshold=4096 mode=ap-bridge wps-mode=disabled wlan2

/interface wireless set amsdu-limit=4096 amsdu-threshold=4096 mode=ap-bridge wps-mode=disabled wlan1

/interface wireless set wireless-protocol=802.11 wlan2

/interface wireless set wireless-protocol=802.11 wlan1

/interface wireless set wmm-support=enabled wlan2

/interface wireless set wmm-support=enabled wlan1

After that enable CAPSMAN Mode with group key Timer Set to 5 minutes

What do you use for CAPSMAN controller? CHR or some CCR?

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Fri Jul 06, 2018 10:07 pm
by Faceless
/interface wireless
set [ find default-name=wlan1 ] band=2ghz-b/g/n channel-width=20/40mhz-Ce \
disabled=no frequency=auto guard-interval=long mode=ap-bridge \
security-profile=foxy ssid=home tx-power=5 tx-power-mode=all-rates-fixed \
wireless-protocol=802.11 wmm-support=enabled
set [ find default-name=wlan2 ] band=5ghz-a/n/ac channel-width=20/40/80mhz-eeeC
disabled=no frequency=auto mode=ap-bridge security-profile=foxy ssid=\
home_5gh wireless-protocol=802.11
add disabled=no keepalive-frames=disabled mac-address=CE:2D:E0:F5:46:75 \
master-interface=wlan1 multicast-buffering=disabled name=FreeWifi_2Ghz \
ssid=FreeWifi_2ghz wds-cost-range=0 wds-default-cost=0 wps-mode=disabled
add disabled=no keepalive-frames=disabled mac-address=CE:2D:E0:F5:46:75 \
master-interface=wlan2 multicast-buffering=disabled name=FreeWifi_5Ghz \
ssid=FreeWifi_5ghz wds-cost-range=0 wds-default-cost=0 wps-mode=disabled
Using 2 or 5ghz Wifi Samsung s6 getting low dowload speed 10-15mbit/s upload 80-100mbit/s RouterOS 6.42.5.Speed does not differ using 2 or 5 G Frequency. Also I can't see TX power Winbox 3.15
on RB941-2nD everything was OK even speed on 2g was better.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Sat Jul 07, 2018 1:00 pm
by Faceless
When connected to 5G Hapac2 Samsung S6 using speed test before downloading or viewing youtube video I got speedtest.com 14/90 mb/sec but after viewing youtube I get 80/90 mbit/s speed test.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Mon Jul 09, 2018 10:01 pm
by gotsprings
The current RouterOS and firmware have gotten a consistent 300/300M over wireless on my hAP AC2. (MUCH IMPROVED ON WHERE IT STARTED.)

This is in WAP mode... Not CAP. I have around 25 devices onnected across the 2 radios.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Fri Jul 13, 2018 7:12 am
by radenli
So Is the problem fixed ?

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Sun Jul 15, 2018 5:04 am
by abcde
By far no. I get very unstable and slow connection using my laptop with Intel 7260 on RouterOS v6.43rc44. It really frustrates me.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Wed Jul 18, 2018 4:07 am
by trevevs
hi guys
considering buying one of these for general home use.. want to use it for wifi & VPN. Would wifi be ok using latest stock f/w for general home use?
whats best speed anyones got using VPN single tunnel 256bit?
cheers

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Fri Jul 20, 2018 3:32 am
by Eugnis
Hello. Have anyone faced this problem?
For example, to same wifi connected >1 devices. When some of these devices started some light internet activity (browsing, youtube etc), all another devices experience some issues from very high ping to router >800ms up to disconnects. (without activity ping 1-2ms).
When 2 devices connected to different bands, all is ok on both.
That's strange, another routers (Asus or cheap Tp-link) handles same load perfectly with many devices.
Tried many different settings, also tried latest 6.43rc44 - still no positive changes.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Fri Jul 20, 2018 3:07 pm
by gotsprings
Hello. Have anyone faced this problem?
For example, to same wifi connected >1 devices. When some of these devices started some light internet activity (browsing, youtube etc), all another devices experience some issues from very high ping to router >800ms up to disconnects. (without activity ping 1-2ms).
When 2 devices connected to different bands, all is ok on both.
That's strange, another routers (Asus or cheap Tp-link) handles same load perfectly with many devices.
Tried many different settings, also tried latest 6.43rc44 - still no positive changes.
I have been running the hAP AC2 at my house for a few weeks now.

It has 17-40 devices across both radios ALL THE TIME. (Depends on how many people are home.)

Right now... I am watching "The Americans" from Amazon Prime on my LG OLED.
My son is downstairs playing FortNight on his Xbox.
He also has a Samsung tablet playing youtube on his lap.
I am typing on my Acer Laptop.
Ryan's Google Home is playing some sort of music he asked for.
And my Pixel XL is next to me.

They are all on the same 5.8 radio.

Running 6.42.5

I was very critical of the cAP AC when I first got it. But somewhere in the 6.42 firmwares... I went from getting throughput in the mid 50M to consistent 300M. By the time I tested a hAP AC2... the firmwares were already up to the 6.42 range.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Fri Jul 20, 2018 5:31 pm
by kobuki
hi guys
considering buying one of these for general home use.. want to use it for wifi & VPN. Would wifi be ok using latest stock f/w for general home use?
whats best speed anyones got using VPN single tunnel 256bit?
cheers
See here. I was able to saturate my 110 Mb downstream using AES-128+SHA256, CPU <10%.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Tue Aug 14, 2018 6:48 pm
by shcherban
Hi, all
Recently bought hAP ac2, it turned out a nightmare to get stable fast link on 2.4 radio.
Options tried:
manual channel select
security (aes/tkip/none)
channel widths with different options (Ce/cE/XX)
updating to RC firmware/OS
leaving only N/a/b/g mode
setting transmit power
power source change
There are few APs from neighbours, however there are 2-3 usable channels, where speed seems to be better, but its still slower than cheap tp-link.
I've got only 15-35 mbps on torrent download comparing to 45-55 mbps on tp-link.
Local share is even worse, transfering file from PC to android and vice versa is only 12-18 mbps vs 22-28 mbps on tp-link.
MikroTik's btest shows 100mbps on 'clean' channels in both directions (separate tests, duplex going 100 for download, 3.5-4 for upload), but internet speed and actual transfer speed is much lower.
Wired im able to get 100 mbps, so its not ISP issue.
My network is laptop (some realtek card), desktop (tp-link wl-721N usb adapter), both are capable of 300 mbps (at least it is indicated in connection properties and in other router status) and 40 MHz wifth, and Redmi3S (20 MHz width)
Am i missing something important?

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Tue Aug 14, 2018 9:12 pm
by Nefraim
Make sure you update your wireless card drivers. Check your hardware provider for newer drivers.
I had issues with an intel 7260 card, with slow speed and connectivity issues. After updating drivers to the latest version my issues are gone..

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Tue Aug 14, 2018 11:04 pm
by Swordforthelord
Hi, all
Recently bought hAP ac2, it turned out a nightmare to get stable fast link on 2.4 radio.
Options tried:
manual channel select
security (aes/tkip/none)
channel widths with different options (Ce/cE/XX)
updating to RC firmware/OS
leaving only N/a/b/g mode
setting transmit power
power source change
There are few APs from neighbours, however there are 2-3 usable channels, where speed seems to be better, but its still slower than cheap tp-link.
I've got only 15-35 mbps on torrent download comparing to 45-55 mbps on tp-link.
Local share is even worse, transfering file from PC to android and vice versa is only 12-18 mbps vs 22-28 mbps on tp-link.
MikroTik's btest shows 100mbps on 'clean' channels in both directions (separate tests, duplex going 100 for download, 3.5-4 for upload), but internet speed and actual transfer speed is much lower.
Wired im able to get 100 mbps, so its not ISP issue.
My network is laptop (some realtek card), desktop (tp-link wl-721N usb adapter), both are capable of 300 mbps (at least it is indicated in connection properties and in other router status) and 40 MHz wifth, and Redmi3S (20 MHz width)
Am i missing something important?
Did you upgrade both the packages and the firmware to the latest current versions?

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Tue Aug 14, 2018 11:29 pm
by shcherban
yep, i've upgraded to latest stable first, then to 6.43rc51 both OS and firmware

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Wed Aug 15, 2018 10:47 pm
by anuser
yep, i've upgraded to latest stable first, then to 6.43rc51 both OS and firmware
Try:
/interface wireless set adaptive-noise-immunity=ap-and-client-mode wlan2
/interface wireless set adaptive-noise-immunity=ap-and-client-mode wlan1

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Mon Aug 20, 2018 10:36 am
by shcherban
anuser thanks, now i have 90-100 mbps lan-to-wan
file share still slow (22-25 mbps), will try to figure out why

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Mon Aug 20, 2018 10:47 am
by PashaT
Please retest with latest 6.42.7.
Performance may be different.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Wed Sep 26, 2018 2:03 pm
by Lotar
Hi,

I just installed os 6.44beta9 (with firmware update)
The wifi performance is very poor.

Currently I use CAPsMAN . I tried anuse suggestion. No luck.
Whatever I try, I get on 5.8 ac about 21mbps download and 46mbps upload. (tested on nexus 6p, and intel wifi 7265 ac laptop) I must be doing something wrong... (that's 802.11g speed)

My capsman settings (for the onboard 5.8 radio) are:

provisioning:
;;; provisioning for local 5.8 radio
radio-mac=(my mac) hw-supported-modes=ac identity-regexp="" common-name-regexp="" ip-address-ranges="" action=create-enabled
master-configuration=AP_main_main_lan_ch36 slave-configurations="" name-format=cap name-prefix=""

channel:
name="5.8_channel036" frequency=5180 control-channel-width=20mhz band=5ghz-n/ac extension-channel=Ceee tx-power=10

configuration:
name="AP_main_lan_ch36" mode=ap ssid="(my ssid)" security=security2_local_lan datapath=datapath_vlan20 channel=5.8_channel036

data path:
name="datapath_vlan20" bridge=bridge20_vlan20

security:
name="security2_local_lan" authentication-types=wpa2-psk encryption=aes-ccm group-encryption=aes-ccm passphrase="(my key)"

This magnificent speed is on all (4) HAP ac2s connected to the capsman.
If anybody has any suggestion, I'm grateful.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Wed Sep 26, 2018 2:56 pm
by nescafe2002
Tx-power=10 seems quite low. Try unsetting that value.
You might also unset control-channel-width, band and extension-channel=Ceee.
I would even unset the fixed channel so the AP can find the least used frequency.
You have no country set, some devices perform better with correct country set.
Not visible, but with CAPsMAN forwarding you don't need to trunk this vlan to APs directly.

It seems you have copy/pasted printed output, next time you can just do a /caps-man export hide-sensitive for copy/paste ready config.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Wed Sep 26, 2018 10:23 pm
by Lotar
Thank you for the reply nescafe2002 !!

Removing the control-channel-width and extension-channel=Ceee did the trick. Now I get solid 220mbps download and about 100mbps upload. Still not great ac speeds but better then before. (Removing the band and setting the country did not impact the transfer speed).
now the channel looks like this:
name="5.8_channel036" frequency=5180 tx-power=17

Thank you for your help !

p.s.
The tx power is low because the ap is right next to my laptop (testing purposes). I'll increase it when I'll set it up properly.
The trunk/vlans are there for the other Ethernet ports, especially an access port so a directly connected computer can access the network's management vlan.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Sep 27, 2018 12:07 pm
by whatever
Try local forwarding (datapath) for even faster speed.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Fri Sep 28, 2018 10:56 am
by anuser
Did you enable those locally on the access point?
/interface wireless set adaptive-noise-immunity=ap-and-client-mode wlan2
/interface wireless set adaptive-noise-immunity=ap-and-client-mode wlan1

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Fri Sep 28, 2018 12:58 pm
by Lotar
Hi,
I'll try local forwarding (datapath) soon.
Yes anuser, enabled locally on all access points.

Will do more testing before deployment...

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Sun Sep 30, 2018 12:36 am
by 2mail
Not sure what u are struggling with ( Poor Performance ) that's why u never get response form Mikrotik support do the correct setup with the routers and believe me u will get mush better performance
i am running between 40 and 60 clients per sector ( Netmetal 5 with AR Elements sector) getting very good throughput with a very stable ping providing my clients from 4Mb to 12Mb
no prob

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Oct 11, 2018 9:04 pm
by anuser
Hi, could you please test with latest 6.44 release candidate? For me it seems performance decreased

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Oct 11, 2018 9:50 pm
by Lotar
Hi anuser,

For me, the speed is up with this patch. I get solid 250/125mbps on 5.8ghz (witch is my current internet speed from the ISP) and about 150/100mbps on 2.4ghz.
My current config is this (with blanked macs/radio names):

# oct/11/2018 21:34:46 by RouterOS 6.44beta17
# software id = 1239-VPQ9
#
# model = RBD52G-5HacD2HnD
# serial number =
/caps-man channel
add band=2ghz-g/n frequency=2412 name=2.4_channel001 tx-power=17
add band=2ghz-g/n frequency=2437 name=2.4_channel006 tx-power=17
add band=2ghz-g/n frequency=2462 name=2.4_channel011 tx-power=17
add band=5ghz-n/ac frequency=5180 name=5.8_channel036 tx-power=17
add band=5ghz-n/ac frequency=5260 name=5.8_channel056 tx-power=17
/caps-man security
add authentication-types=wpa-psk,wpa2-psk encryption=aes-ccm,tkip group-encryption=aes-ccm group-key-update=5m name=security1_management
add authentication-types=wpa-psk,wpa2-psk encryption=aes-ccm,tkip group-encryption=aes-ccm group-key-update=5m name=security2_local_lan
add authentication-types=wpa-psk,wpa2-psk encryption=aes-ccm,tkip group-encryption=aes-ccm group-key-update=5m name=security3_guest
/caps-man access-list
add action=accept allow-signal-out-of-range=10s comment="signal ok" disabled=no interface=any signal-range=-80..120 ssid-regexp=""
add action=reject allow-signal-out-of-range=10s comment="bad signal" disabled=no interface=any signal-range=-120..-81 ssid-regexp=""
/caps-man configuration
add channel=2.4_channel001 country=romania datapath=datapath_vlan10 hide-ssid=yes mode=ap name=AP_0_management_ch1 rates.vht-supported-mcs="" security=security1_management ssid=art_management
add channel=2.4_channel001 country=romania datapath=datapath_vlan20a mode=ap name=AP_0_main_lan_ch1 security=security2_local_lan ssid=art_LAN
add channel=2.4_channel001 country=romania datapath=datapath_vlan30 name=AP_0_guest_ch1 security=security3_guest ssid=art_Guest
add channel=5.8_channel036 country=romania datapath=datapath_vlan10 hide-ssid=yes mode=ap name=AP_0_management_ch36 security=security1_management ssid=art_management_5.8
add channel=5.8_channel036 country=romania datapath=datapath_vlan20a mode=ap name=AP_0_main_lan_ch36 security=security2_local_lan ssid=art_LAN_5.8
add channel=5.8_channel036 country=romania datapath=datapath_vlan30 mode=ap name=AP_0_guest_ch36 security=security3_guest ssid=art_Guest_5.8
add channel=2.4_channel006 country=romania datapath=datapath_vlan30 name=AP_1_guest_ch6 security=security3_guest ssid=art_Guest
add channel=5.8_channel036 country=romania datapath=datapath_vlan30 mode=ap name=AP_1_guest_ch36 security=security3_guest ssid=art_Guest_5.8
add channel=2.4_channel006 country=romania datapath=datapath_vlan20a mode=ap name=AP_1_main_lan_ch6 security=security2_local_lan ssid=art_LAN
add channel=2.4_channel006 country=romania datapath=datapath_vlan10 hide-ssid=yes mode=ap name=AP_1_management_ch6 rates.vht-supported-mcs="" security=security1_management ssid=art_management
add channel=5.8_channel036 country=romania datapath=datapath_vlan20a mode=ap name=AP_1_main_lan_ch36 security=security2_local_lan ssid=art_LAN_5.8
add channel=5.8_channel036 country=romania datapath=datapath_vlan10 hide-ssid=yes mode=ap name=AP_1_management_ch36 security=security1_management ssid=art_management_5.8
add channel=2.4_channel011 country=romania datapath=datapath_vlan30 name=AP_2_guest_ch11 security=security3_guest ssid=art_Guest
add channel=5.8_channel036 country=romania datapath=datapath_vlan30 mode=ap name=AP_2_guest_ch36 security=security3_guest ssid=art_Guest_5.8
add channel=5.8_channel036 country=romania datapath=datapath_vlan20a mode=ap name=AP_2_main_lan_ch36 security=security2_local_lan ssid=art_LAN_5.8
add channel=2.4_channel011 country=romania datapath=datapath_vlan20a mode=ap name=AP_2_main_lan_ch11 security=security2_local_lan ssid=art_LAN
add channel=5.8_channel036 country=romania datapath=datapath_vlan10 hide-ssid=yes mode=ap name=AP_2_management_ch36 security=security1_management ssid=art_management_5.8
add channel=2.4_channel011 country=romania datapath=datapath_vlan10 hide-ssid=yes mode=ap name=AP_2_management_ch11 rates.vht-supported-mcs="" security=security1_management ssid=art_management
add channel=2.4_channel001 country=romania datapath=datapath_vlan30 name=AP_3_guest_ch1 security=security3_guest ssid=art_Guest
add channel=5.8_channel036 country=romania datapath=datapath_vlan30 mode=ap name=AP_3_guest_ch36 security=security3_guest ssid=art_Guest_5.8
add channel=2.4_channel001 country=romania datapath=datapath_vlan20a mode=ap name=AP_3_main_lan_ch1 security=security2_local_lan ssid=art_LAN
add channel=5.8_channel036 country=romania datapath=datapath_vlan20a mode=ap name=AP_3_main_lan_ch36 security=security2_local_lan ssid=art_LAN_5.8
add channel=2.4_channel001 country=romania datapath=datapath_vlan10 hide-ssid=yes mode=ap name=AP_3_management_ch1 rates.vht-supported-mcs="" security=security1_management ssid=art_management
add channel=5.8_channel036 country=romania datapath=datapath_vlan10 hide-ssid=yes mode=ap name=AP_3_management_ch36 security=security1_management ssid=art_management_5.8
/caps-man datapath
add bridge=bridge10_vlan10 name=datapath_vlan10
add bridge=bridge30_vlan30 client-to-client-forwarding=no local-forwarding=no name=datapath_vlan30
add bridge=bridge20_vlan20a name=datapath_vlan20a
/caps-man interface
add configuration=AP_1_main_lan_ch6 disabled=no l2mtu=1600 mac-address=XX:XX:XX:XX:XX:XX master-interface=none name=cap1 radio-mac=XX:XX:XX:XX:XX:XX radio-name=XXXXXXXXXXXX
add configuration=AP_1_management_ch6 disabled=no l2mtu=1600 mac-address=XX:XX:XX:XX:XX:XX master-interface=cap1 name=cap2 radio-mac=00:00:00:00:00:00 radio-name=XXXXXXXXXXXX
add configuration=AP_1_guest_ch6 disabled=no l2mtu=1600 mac-address=XX:XX:XX:XX:XX:XX master-interface=cap1 name=cap3 radio-mac=00:00:00:00:00:00 radio-name=XXXXXXXXXXXX
add configuration=AP_1_main_lan_ch36 disabled=no l2mtu=1600 mac-address=XX:XX:XX:XX:XX:XX master-interface=none name=cap4 radio-mac=XX:XX:XX:XX:XX:XX radio-name=XXXXXXXXXXXX
add configuration=AP_1_management_ch36 disabled=no l2mtu=1600 mac-address=XX:XX:XX:XX:XX:XX master-interface=cap4 name=cap5 radio-mac=00:00:00:00:00:00 radio-name=XXXXXXXXXXXX
add configuration=AP_1_guest_ch36 disabled=no l2mtu=1600 mac-address=XX:XX:XX:XX:XX:XX master-interface=cap4 name=cap6 radio-mac=00:00:00:00:00:00 radio-name=XXXXXXXXXXXX
add configuration=AP_2_main_lan_ch11 disabled=no l2mtu=1600 mac-address=XX:XX:XX:XX:XX:XX master-interface=none name=cap7 radio-mac=XX:XX:XX:XX:XX:XX radio-name=XXXXXXXXXXXX
add configuration=AP_2_management_ch11 disabled=no l2mtu=1600 mac-address=XX:XX:XX:XX:XX:XX master-interface=cap7 name=cap8 radio-mac=00:00:00:00:00:00 radio-name=XXXXXXXXXXXX
add configuration=AP_2_guest_ch11 disabled=no l2mtu=1600 mac-address=XX:XX:XX:XX:XX:XX master-interface=cap7 name=cap9 radio-mac=00:00:00:00:00:00 radio-name=XXXXXXXXXXXX
add configuration=AP_2_main_lan_ch36 disabled=no l2mtu=1600 mac-address=XX:XX:XX:XX:XX:XX master-interface=none name=cap10 radio-mac=XX:XX:XX:XX:XX:XX radio-name=XXXXXXXXXXXX
add configuration=AP_0_main_lan_ch1 disabled=no l2mtu=1600 mac-address=XX:XX:XX:XX:XX:XX master-interface=none name=cap11 radio-mac=XX:XX:XX:XX:XX:XX radio-name=XXXXXXXXXXXX
add configuration=AP_0_management_ch1 disabled=no l2mtu=1600 mac-address=XX:XX:XX:XX:XX:XX master-interface=cap11 name=cap12 radio-mac=00:00:00:00:00:00 radio-name=XXXXXXXXXXXX
add configuration=AP_0_guest_ch1 disabled=no l2mtu=1600 mac-address=XX:XX:XX:XX:XX:XX master-interface=cap11 name=cap13 radio-mac=00:00:00:00:00:00 radio-name=XXXXXXXXXXXX
add configuration=AP_0_main_lan_ch36 disabled=no l2mtu=1600 mac-address=XX:XX:XX:XX:XX:XX master-interface=none name=cap14 radio-mac=XX:XX:XX:XX:XX:XX radio-name=XXXXXXXXXXXX
add configuration=AP_0_management_ch36 disabled=no l2mtu=1600 mac-address=XX:XX:XX:XX:XX:XX master-interface=cap14 name=cap15 radio-mac=00:00:00:00:00:00 radio-name=XXXXXXXXXXXX
add configuration=AP_0_guest_ch36 disabled=no l2mtu=1600 mac-address=XX:XX:XX:XX:XX:XX master-interface=cap14 name=cap16 radio-mac=00:00:00:00:00:00 radio-name=XXXXXXXXXXXX
add configuration=AP_2_management_ch36 disabled=no l2mtu=1600 mac-address=XX:XX:XX:XX:XX:XX master-interface=cap10 name=cap17 radio-mac=00:00:00:00:00:00 radio-name=XXXXXXXXXXXX
add configuration=AP_2_guest_ch36 disabled=no l2mtu=1600 mac-address=XX:XX:XX:XX:XX:XX master-interface=cap10 name=cap18 radio-mac=00:00:00:00:00:00 radio-name=BXXXXXXXXXXXX
/caps-man manager
set ca-certificate=auto certificate=auto enabled=yes
/caps-man provisioning
add action=create-enabled comment="provisioning for local 2.4 radio" hw-supported-modes=gn master-configuration=AP_0_main_lan_ch1 radio-mac=XX:XX:XX:XX:XX:XX slave-configurations=AP_0_management_ch1,AP_0_guest_ch1
add action=create-enabled comment="provisioning for local 5.8 radio" master-configuration=AP_0_main_lan_ch36 radio-mac=XX:XX:XX:XX:XX:XX slave-configurations=AP_0_management_ch36
add action=create-enabled comment="provisioning for AP1 2.4" master-configuration=AP_1_main_lan_ch6 radio-mac=XX:XX:XX:XX:XX:XX slave-configurations=AP_1_management_ch6,AP_1_guest_ch6
add action=create-enabled comment="provisioning for AP1 5.8" master-configuration=AP_1_main_lan_ch36 radio-mac=XX:XX:XX:XX:XX:XX slave-configurations=AP_1_management_ch36
add action=create-enabled comment="provisioning for AP2 2.4" master-configuration=AP_2_main_lan_ch11 radio-mac=XX:XX:XX:XX:XX:XX slave-configurations=AP_2_management_ch11,AP_2_guest_ch11
add action=create-enabled comment="provisioning for AP2 5.8" master-configuration=AP_2_main_lan_ch36 radio-mac=XX:XX:XX:XX:XX:XX slave-configurations=AP_2_management_ch36
add action=create-enabled comment="provisioning for AP3 5.8" master-configuration=AP_3_main_lan_ch36 radio-mac=XX:XX:XX:XX:XX:XX slave-configurations=AP_3_management_ch36
add action=create-enabled comment="provisioning for AP3 2.4" master-configuration=AP_3_main_lan_ch1 radio-mac=XX:XX:XX:XX:XX:XX slave-configurations=AP_3_management_ch1,AP_3_guest_ch1

p.s. I know there are a lot of redundant 5.8 configurations (are there to play around with the 5.8 channels...)

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Sat Jun 15, 2019 9:46 am
by psychodracon
Hello all,
Any changes on this? I`m new Mikrotik hAP ac^2 user and i`m struggling with poor WiFi performance. My connection from ISP is 300/20 Mbps and i`m getting around 290/20 Mbps using ethernet. But using WiFi 2.4G i`m getting around 90/20 Mbps (1m from router) same for 5G (around 110/20 Mbps). My settings are default only changes that i have made is that i have enabled secruity (WPA2-PSK with AES only).

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Fri Jun 28, 2019 10:17 pm
by sirotkaslo
I'm also still having issues with wireless performance, haven't touched it much, only setup a bridge and a dhcp client on it

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Tue Aug 13, 2019 4:15 pm
by szhura
i have another problem with wifi. it seemes to drop speed tenfold after several days of working without reboot. reboot solves wifi speed problem but again only for several days. help needed :(

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Tue Aug 20, 2019 1:28 pm
by gotsprings
i have another problem with wifi. it seemes to drop speed tenfold after several days of working without reboot. reboot solves wifi speed problem but again only for several days. help needed :(
Write a simple scheduler and and script to reboot it every 48 hours.

Professionally... We put a stop on Mikrotik wireless deployments. We kept hitting the same issue. We documented it and Mikrotik reproduced it. They stated they don't have a fix... As pros... That meant no more in the field.

I was incredibly disappointed in Mikrotik about this. I wrote a lot of cool stuff based on Caps-man and can't use any of it now.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Tue Aug 20, 2019 9:48 pm
by heidarren
My experience with this hAP AC2 with 6.46b28 firmware after fine tune can gets 470mbps with my iPhone XS Max, and 440mbps with my iPad Pro 10'5, upload both 206mbps (My ISP max speed), really nice result even though the speed is not stable, sometimes will drop to sub 300mbps.

The problem is when I switch to CAPsMAN mode it will limit to 380mbps, no matter how I change setting, it caps there, and I noticed one of my CAP's 5GHz Wi-Fi disappear after 2 days of running, it just gone and I can't seems to find it on my phone but CAPsMAN got nothing special and no log was logged, it only works again by removing it from CAPsMAN and reconnect, will monitor few more days to see if this happen again.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Wed Aug 21, 2019 5:19 pm
by anuser
My experience with this hAP AC2 with 6.46b28 firmware after fine tune
Can you please post your "fine tuned" configuration?

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Wed Aug 21, 2019 11:20 pm
by szhura
i have another problem with wifi. it seemes to drop speed tenfold after several days of working without reboot. reboot solves wifi speed problem but again only for several days. help needed :(
Write a simple scheduler and and script to reboot it every 48 hours.

Professionally... We put a stop on Mikrotik wireless deployments. We kept hitting the same issue. We documented it and Mikrotik reproduced it. They stated they don't have a fix... As pros... That meant no more in the field.

I was incredibly disappointed in Mikrotik about this. I wrote a lot of cool stuff based on Caps-man and can't use any of it now.
it seemes that after updating to 6.45.3 problem has gone. but it needs more testing

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Wed Aug 21, 2019 11:29 pm
by heidarren
My experience with this hAP AC2 with 6.46b28 firmware after fine tune can gets 470mbps with my iPhone XS Max, and 440mbps with my iPad Pro 10'5, upload both 206mbps (My ISP max speed), really nice result even though the speed is not stable, sometimes will drop to sub 300mbps.

The problem is when I switch to CAPsMAN mode it will limit to 380mbps, no matter how I change setting, it caps there, and I noticed one of my CAP's 5GHz Wi-Fi disappear after 2 days of running, it just gone and I can't seems to find it on my phone but CAPsMAN got nothing special and no log was logged, it only works again by removing it from CAPsMAN and reconnect, will monitor few more days to see if this happen again.
It happened again today, about 24 hours of running it, seems it's not accident, something wrong on CAPsMAN in 6.46b28, anyway I'm done with this CAPsMAN, just run it as AP bridge and bye bye CAPsMAN.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Aug 22, 2019 9:20 am
by heidarren
My experience with this hAP AC2 with 6.46b28 firmware after fine tune
Can you please post your "fine tuned" configuration?
authentication-types=wpa2-psk eap-methods="" group-key-update=1h mode=dynamic-keys name=Darren supplicant-identity="" wpa-pre-shared-key=\
xxxxxxxx wpa2-pre-shared-key=xxxxxxxx
/interface wireless
set [ find default-name=wlan2 ] adaptive-noise-immunity=ap-and-client-mode antenna-gain=2 band=5ghz-onlyac basic-rates-a/g=12Mbps channel-width=\
20/40/80mhz-eeCe country="united states" disabled=no distance=indoors frequency=5220 frequency-mode=regulatory-domain \
hw-fragmentation-threshold=2346 hw-protection-mode=rts-cts hw-protection-threshold=2347 keepalive-frames=disabled mode=ap-bridge \
multicast-buffering=disabled multicast-helper=disabled name=W5G rate-set=configured security-profile=Darren ssid=ChengFamily5G \
supported-rates-a/g=12Mbps,18Mbps,24Mbps,36Mbps,48Mbps,54Mbps vht-supported-mcs=mcs0-9,mcs0-9 wireless-protocol=802.11 wmm-support=enabled \
wps-mode=disabled
/interface wireless nstreme
set W5G disable-csma=yes

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Tue Nov 12, 2019 3:54 am
by santyx32
I manage a municipal ISP, we have had a steady flow of wifi issues. Many CX complain of doing and disconnecting wifi as well as slow speeds,
I'm already regretting or purchase of 500 hAC2 units. The pending "Broadcom compatibility firmware fix" had better be the silver bullet or we are going to look elsewhere for the next 1000 units in our Network build.
It's going to be 2020 and the hAP ac2 is still not fully compatible with Broadcom clients like Exynos S10 phones.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Wed Nov 13, 2019 8:02 am
by anuser
RouterOS v6.46beta59 has fixes for wireless. Do they fix your performance problems with hap ac2?
(Not with CAPSMAN, this is full of bugs)

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Wed Nov 13, 2019 8:38 pm
by gotsprings
RouterOS v6.46beta59 has fixes for wireless. Do they fix your performance problems with hap ac2?
(Not with CAPSMAN, this is full of bugs)
Which Bugs exactly in caps-man?

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Thu Nov 14, 2019 7:41 am
by anuser
The pending "Broadcom compatibility firmware fix"
Where did you hear about that special Broadcom compatibiliy firmware fix?

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Fri Nov 15, 2019 3:18 am
by santyx32
6.46 beta 59 fixes nothing for me, setting AMSDU Limit to 2048 improves the overall stability but there's still 1-2 disconnections per day vs 1 disconnection every 5 minutes.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Fri Nov 15, 2019 1:56 pm
by Znevna
Thanks for the "AMSDU Limit to 2048" tip. It makes my Huawei Mate 20 Lite like the router a little bit more (atleast I get ~20mbps and even more somewhat stable download on 5GHz, instead of, well, less.)

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Sun Aug 30, 2020 9:15 am
by anuser
RouterOS v6.46beta59 has fixes for wireless. Do they fix your performance problems with hap ac2?
(Not with CAPSMAN, this is full of bugs)
Which Bugs exactly in caps-man?
viewtopic.php?f=7&t=153735&p=760146&hil ... an#p760146

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Sun Aug 30, 2020 9:10 pm
by bpwl
Interesting config setting: "hw-fragmentation-threshold=2346 hw-protection-mode=rts-cts hw-protection-threshold=2347", will never activate RTS/CTS, so why should you set it then?
Max packet size = 2346, RTS/CTS is activated if packet size is 2347 or larger.

Many of the settings in RouterOS are from b/a/g/n , but we use 802.11ac and there the numbers are different. e.g. A-MSDU size is now not set but dependent on the PMDU size, and that is either 3895,7991 or 11454 in 802.11 ac. What happens if the n version of a-MSDU size is set (typically one chooses between 8192 and 2048) in RouterOS?

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Mon Dec 27, 2021 7:50 am
by dazford
Sorry to bring up an old thread but I have just purchased a Hap AC3 with the external antennas and it still has all the same problems that existed from 3-4 years ago.

I have also upgraded to the be all and end all of fixes which is ROS 7. Guess what???? It doesn't work. I read that people are having wireless issues with 7.1.1 which is the latest stable release as the time of writing this (Dec 27th 2021) so I went back to the latest stable release of ROS 6 which is 6.49.2 and it makes no difference.

I have WLAN1 (2.4Ghz) and WLAN2 (5Ghz) and even though both are enabled, only 1 can be connected to or even seen, depending on the how the stars are lined up and where every planet is situated and if the moon is visible or not, and the other comes up with an error saying it cannot connect. There is no choice of which one works unless you manually disable 1 of the radios. I cannot even get into room 2 without losing signal. The Hap AC3 is in room 1.

Support files have been sent off to the suppliers and they have said there is nothing wrong but they are seeing the wireless hit -95db and dropouts. Its a very simple base config with stock standard rules and a basic masq NAT to the internet. That's it. No special routing, firewalling, VPN's, nothing.......... Again a very simple wireless config with a separate SSID for each WLAN and uses the same same security for both WLAN's. Any more than 5M away from the Hap AC3 and the wireless connections are so poor that they drop.

I find it very frustrating and am extremely p1$$3d off right now that even after all these years, Mikrotik still has the same god damn issues that they had 3-4 years ago with the new equipment and they great ROS version 7 that was meant to be the saviour doesn't fix anything with the well known wireless issues.

I then come across this thread that dates way back with the same issues I am facing now and even more issues than what was listed all those years ago now with radios not even showing up or being able to connect to them. I honestly feel like taking this POS device and bashing Mikrotik over their moronic heads right now as they clearly are selling SMB grade devices that don't work and never will and as a business, you are better off buying crappy d-link or tp-link as they are more stable and out perform expensive business grade products that are sold by Mikrotik. I don't own a single Mikrotik product that does what it says its going to do and have had enough. This includes AP's, Routers, switches, All in one devices, etc and not one of them does or works as they should and it doesn't matter how many times you contact support, there is no answer.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Mon Dec 27, 2021 3:07 pm
by r00t
Well, best solution for you is to return Mikrotik hAP while you still can and buy something else. While Mikrotik is doing some baby steps towards better WIFI, it's all still years behind even the cheapest competition. It will take years before situation improves at this pace, so if you need good WIFI now, you have to look somewhere else...

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Mon Dec 27, 2021 3:31 pm
by bpwl
I have WLAN1 (2.4Ghz) and WLAN2 (5Ghz) and even though both are enabled, only 1 can be connected to or even seen, depending on the how the stars are lined up and where every planet is situated and if the moon is visible or not, and the other comes up with an error saying it cannot connect.
I bet you can see 2.4GHz , not the 5 GHZ. And that is because of the settings (out of the box) that are a mismatch with your needs.
5 GHz need the correct country to be set (channels differ greatly per regulatory domain), the freq selection must be done (auto freq has no clue and is unpredictable), be aware of DFS rules requiring 1 minute and for some channels 10 minutes of total silence , be aware of the channel limitations of the client device (some only support the 4 lower channels), some devices still insist on using TKIP and to pass to adjacent rooms the default 80MHz channel width is the weakest choice possible.

Yes other brands are auto-adjusting the parameters and are preconfigured for the regulatory domain of the destination. Their auto freq selection is better, and they have DFS prescan avoiding radio silence, WMM is enabled , they use airtime fairness, have better roaming support (QBSS info, band steering), do not use the smallest buffers of the802.11ac standard, they may even have beam forming .... . But besides that the MT AP can be used if manually set correctly. Test in standalone mode. Adding CAPsMAN is adding another layer of complexity with new functions but also new limitations.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Tue Dec 28, 2021 12:38 am
by gotsprings
My Audience with WAVE 2 drivers on it is performing almost as well as other manufactures did with ACv2... in 2016.

It can't work with caps-man. So its configured standalone and it lights up the whole house with all 3 radios taking clients.

For the first time ever... 2.4Ghz clients are staying connected in this noisy environment. The time outs are under 20 seconds now. So I stopped getting alerts every couple hours.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Tue Dec 28, 2021 4:01 am
by dazford
I have WLAN1 (2.4Ghz) and WLAN2 (5Ghz) and even though both are enabled, only 1 can be connected to or even seen, depending on the how the stars are lined up and where every planet is situated and if the moon is visible or not, and the other comes up with an error saying it cannot connect.
I bet you can see 2.4GHz , not the 5 GHZ. And that is because of the settings (out of the box) that are a mismatch with your needs.
5 GHz need the correct country to be set (channels differ greatly per regulatory domain), the freq selection must be done (auto freq has no clue and is unpredictable), be aware of DFS rules requiring 1 minute and for some channels 10 minutes of total silence , be aware of the channel limitations of the client device (some only support the 4 lower channels), some devices still insist on using TKIP and to pass to adjacent rooms the default 80MHz channel width is the weakest choice possible.

Yes other brands are auto-adjusting the parameters and are preconfigured for the regulatory domain of the destination. Their auto freq selection is better, and they have DFS prescan avoiding radio silence, WMM is enabled , they use airtime fairness, have better roaming support (QBSS info, band steering), do not use the smallest buffers of the802.11ac standard, they may even have beam forming .... . But besides that the MT AP can be used if manually set correctly. Test in standalone mode. Adding CAPsMAN is adding another layer of complexity with new functions but also new limitations.
Sadly I do have the correct country set and tried auto and manual frequencies and all tests were done in standalone mode. Many settings were tried with multiple security types and even multiple security policies for each WLAN. Bands, channel widths, DFS on/off, Alternate countries, indoor/outdoor, WMM on/off, TX Power, etc etc but nothing made a difference and I am waiting for support to get back to me but that won't be until mid January at this point due to the Christmas holidays.

This was purchased as a test device that I wanted to have the configuration correct to setup VPN's with other sites and setting their current devices, whatever they may be, to be in bridge mode only which would then render the wireless on there existing devices to be turned off. With all the different types of internet connections we have here and different modem interfaces, this would be the easiest way to connect the sites together but WiFi is a must and having to buy now a 3rd device just for WiFi is ridiculous when it should work with just the device I purchased.

I ended up purchasing Cisco gear for home as previous tests with so called SMB products such as Mikrotik, Ubiquiti and even Edimax that are meant to be the cheaper SMB products were all worse than basic home grade products. However some of the home grade products have issues with handoff in larger areas where multiple devices are needed, which was also the case with the SMB products funnily enough, so I went Cisco for my house and have good speeds and flawless handoff. It would be nice for a product that claims to be great and have all these features to actually work when it comes to the simple things these devices are meant to be capable of.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Tue Dec 28, 2021 10:22 am
by bpwl
I have WLAN1 (2.4Ghz) and WLAN2 (5Ghz) and even though both are enabled, only 1 can be connected to or even seen, depending on the how the stars are lined up and where every planet is situated and if the moon is visible or not, and the other comes up with an error saying it cannot connect.
Very unlikely combination with this ....
Sadly I do have the correct country set and tried auto and manual frequencies and all tests were done in standalone mode. Many settings were tried with multiple security types and even multiple security policies for each WLAN. Bands, channel widths, DFS on/off, Alternate countries, indoor/outdoor, WMM on/off, TX Power, etc etc but nothing made a difference
DFS cannot be turned OFF, installation should be "any" not indoor or outdoor,
.... and don't copy "tuned configs" from others. They work excellent for that environment, buy every tuning setting has a negative impact and should not be set if it was not absolutly needed.
You might share your "non working" config (/export hide-sensitive file=anyfilename) , and the info in the log (with Logging Topics=wireless enabled) and what is in the registration table.

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Tue Apr 19, 2022 7:50 pm
by anav
Sorry to bring up an old thread but I have just purchased a Hap AC3 with the external antennas and it still has all the same problems that existed from 3-4 years ago.
Sorry you only have yourself to blame, especially because you have prior experience. Most first time users tend to buy blindly and although they do they talk to friends, check out youtube, check out reviews we tend NOT TO CHECK OUT the biggie, the most IMPORTANT SOURCE, and by that I mean visit support forums to get a lay of the land --> well until they have bought the product and run into problem. So yes, the first time user gets a break but not afterwards.

No one here I know of with their head screwed on straight is recommending FOR A WIFI focussed requirement, wifi5 from MT. Granted their newer products hapac3, audience etc seem to be a less proprietary product and have better functionality (speed and stability) then the older wifi5 devices, but they do still have some issues.
BPWL is best suited, tracks this stuff closely, to state whether the hacac3/audience are indeed as good as other vendor wifi5 products and if better than older mt wifi5.

In any case, any moron that buys WIFI5, when there are now cost effective wifi6 options out there, is beyond help. The only reason to stick with MT wifi is twofold.
a. un paralleled flexibility of the RoS firmware
b. amazing capsman controller for those with many many wifi device.

Hence there are many here begging MT to provide some wifi6/6E etc RoS capsman capable devices!!!! ASAP!!!

Re: hAP ac^2 Problems---Extremely Poor Performance found in 2.4G and 5G WiFi

Posted: Wed Apr 20, 2022 7:49 pm
by gotsprings
Sorry to bring up an old thread but I have just purchased a Hap AC3 with the external antennas and it still has all the same problems that existed from 3-4 years ago.
Sorry you only have yourself to blame, especially because you have prior experience. Most first time users tend to buy blindly and although they do they talk to friends, check out youtube, check out reviews we tend NOT TO CHECK OUT the biggie, the most IMPORTANT SOURCE, and by that I mean visit support forums to get a lay of the land --> well until they have bought the product and run into problem. So yes, the first time user gets a break but not afterwards.

No one here I know of with their head screwed on straight is recommending FOR A WIFI focussed requirement, wifi5 from MT. Granted their newer products hapac3, audience etc seem to be a less proprietary product and have better functionality (speed and stability) then the older wifi5 devices, but they do still have some issues.
BPWL is best suited, tracks this stuff closely, to state whether the hacac3/audience are indeed as good as other vendor wifi5 products and if better than older mt wifi5.

In any case, any moron that buys WIFI5, when there are now cost effective wifi6 options out there, is beyond help. The only reason to stick with MT wifi is twofold.
a. un paralleled flexibility of the RoS firmware
b. amazing capsman controller for those with many many wifi device.

Hence there are many here begging MT to provide some wifi6/6E etc RoS capsman capable devices!!!! ASAP!!!
Begging is getting me nowhere...