Pings tend to be flaky too:
Usually low pings around 1-2ms. Then it suddenly increases at seq 100 and leads to a loss of 104-107.
Infabo: that is whay I mean and what I encounter as well, you need to set a longer testing time in that app to always catch it.
ping 192.168.88.1
PING 192.168.88.1 (192.168.88.1) 56(84) bytes of data.
64 bytes from 192.168.88.1: icmp_seq=1 ttl=64 time=1.30 ms
64 bytes from 192.168.88.1: icmp_seq=2 ttl=64 time=21.7 ms
64 bytes from 192.168.88.1: icmp_seq=3 ttl=64 time=33.3 ms
64 bytes from 192.168.88.1: icmp_seq=4 ttl=64 time=48.8 ms
64 bytes from 192.168.88.1: icmp_seq=5 ttl=64 time=92.9 ms
64 bytes from 192.168.88.1: icmp_seq=6 ttl=64 time=1.36 ms
64 bytes from 192.168.88.1: icmp_seq=7 ttl=64 time=1.34 ms
64 bytes from 192.168.88.1: icmp_seq=8 ttl=64 time=1.32 ms
64 bytes from 192.168.88.1: icmp_seq=9 ttl=64 time=0.981 ms
64 bytes from 192.168.88.1: icmp_seq=10 ttl=64 time=1.30 ms
64 bytes from 192.168.88.1: icmp_seq=11 ttl=64 time=1.35 ms
64 bytes from 192.168.88.1: icmp_seq=12 ttl=64 time=2.10 ms
64 bytes from 192.168.88.1: icmp_seq=13 ttl=64 time=1.28 ms
64 bytes from 192.168.88.1: icmp_seq=14 ttl=64 time=34.3 ms
64 bytes from 192.168.88.1: icmp_seq=15 ttl=64 time=62.7 ms
64 bytes from 192.168.88.1: icmp_seq=16 ttl=64 time=4.20 ms
64 bytes from 192.168.88.1: icmp_seq=17 ttl=64 time=13.0 ms
64 bytes from 192.168.88.1: icmp_seq=18 ttl=64 time=6.95 ms
64 bytes from 192.168.88.1: icmp_seq=19 ttl=64 time=19.9 ms
64 bytes from 192.168.88.1: icmp_seq=20 ttl=64 time=1.29 ms
64 bytes from 192.168.88.1: icmp_seq=21 ttl=64 time=1.45 ms
64 bytes from 192.168.88.1: icmp_seq=22 ttl=64 time=0.918 ms
64 bytes from 192.168.88.1: icmp_seq=23 ttl=64 time=1.33 ms
64 bytes from 192.168.88.1: icmp_seq=24 ttl=64 time=3.33 ms
64 bytes from 192.168.88.1: icmp_seq=25 ttl=64 time=4.88 ms
64 bytes from 192.168.88.1: icmp_seq=26 ttl=64 time=2.10 ms
64 bytes from 192.168.88.1: icmp_seq=27 ttl=64 time=9.75 ms
64 bytes from 192.168.88.1: icmp_seq=28 ttl=64 time=8.58 ms
64 bytes from 192.168.88.1: icmp_seq=29 ttl=64 time=1.29 ms
64 bytes from 192.168.88.1: icmp_seq=30 ttl=64 time=1.30 ms
64 bytes from 192.168.88.1: icmp_seq=31 ttl=64 time=29.7 ms
64 bytes from 192.168.88.1: icmp_seq=32 ttl=64 time=1.23 ms
64 bytes from 192.168.88.1: icmp_seq=33 ttl=64 time=11.3 ms
64 bytes from 192.168.88.1: icmp_seq=34 ttl=64 time=61.0 ms
64 bytes from 192.168.88.1: icmp_seq=35 ttl=64 time=30.0 ms
64 bytes from 192.168.88.1: icmp_seq=36 ttl=64 time=0.851 ms
64 bytes from 192.168.88.1: icmp_seq=37 ttl=64 time=1.31 ms
64 bytes from 192.168.88.1: icmp_seq=38 ttl=64 time=0.888 ms
64 bytes from 192.168.88.1: icmp_seq=39 ttl=64 time=1.32 ms
64 bytes from 192.168.88.1: icmp_seq=40 ttl=64 time=3.28 ms
64 bytes from 192.168.88.1: icmp_seq=41 ttl=64 time=104 ms
64 bytes from 192.168.88.1: icmp_seq=42 ttl=64 time=104 ms
64 bytes from 192.168.88.1: icmp_seq=43 ttl=64 time=1011 ms
64 bytes from 192.168.88.1: icmp_seq=44 ttl=64 time=1001 ms
64 bytes from 192.168.88.1: icmp_seq=45 ttl=64 time=603 ms
64 bytes from 192.168.88.1: icmp_seq=46 ttl=64 time=195 ms
64 bytes from 192.168.88.1: icmp_seq=47 ttl=64 time=14.6 ms
64 bytes from 192.168.88.1: icmp_seq=48 ttl=64 time=15.2 ms
64 bytes from 192.168.88.1: icmp_seq=49 ttl=64 time=1.36 ms
64 bytes from 192.168.88.1: icmp_seq=50 ttl=64 time=1.29 ms
64 bytes from 192.168.88.1: icmp_seq=51 ttl=64 time=1.35 ms
64 bytes from 192.168.88.1: icmp_seq=52 ttl=64 time=1.35 ms
64 bytes from 192.168.88.1: icmp_seq=53 ttl=64 time=0.884 ms
64 bytes from 192.168.88.1: icmp_seq=54 ttl=64 time=1.32 ms
64 bytes from 192.168.88.1: icmp_seq=55 ttl=64 time=1.30 ms
64 bytes from 192.168.88.1: icmp_seq=56 ttl=64 time=1.29 ms
64 bytes from 192.168.88.1: icmp_seq=57 ttl=64 time=1.28 ms
64 bytes from 192.168.88.1: icmp_seq=61 ttl=64 time=12.9 ms
64 bytes from 192.168.88.1: icmp_seq=62 ttl=64 time=35.6 ms
64 bytes from 192.168.88.1: icmp_seq=63 ttl=64 time=0.851 ms
64 bytes from 192.168.88.1: icmp_seq=64 ttl=64 time=47.0 ms
64 bytes from 192.168.88.1: icmp_seq=65 ttl=64 time=20.2 ms
64 bytes from 192.168.88.1: icmp_seq=66 ttl=64 time=1.48 ms
64 bytes from 192.168.88.1: icmp_seq=67 ttl=64 time=1.31 ms
64 bytes from 192.168.88.1: icmp_seq=68 ttl=64 time=0.864 ms
64 bytes from 192.168.88.1: icmp_seq=72 ttl=64 time=1.41 ms
64 bytes from 192.168.88.1: icmp_seq=73 ttl=64 time=0.869 ms
64 bytes from 192.168.88.1: icmp_seq=74 ttl=64 time=4.44 ms
64 bytes from 192.168.88.1: icmp_seq=75 ttl=64 time=22.9 ms
64 bytes from 192.168.88.1: icmp_seq=76 ttl=64 time=21.5 ms
64 bytes from 192.168.88.1: icmp_seq=77 ttl=64 time=1.28 ms
64 bytes from 192.168.88.1: icmp_seq=78 ttl=64 time=1.30 ms
64 bytes from 192.168.88.1: icmp_seq=79 ttl=64 time=1.36 ms
64 bytes from 192.168.88.1: icmp_seq=80 ttl=64 time=1.36 ms
64 bytes from 192.168.88.1: icmp_seq=81 ttl=64 time=1.61 ms
64 bytes from 192.168.88.1: icmp_seq=82 ttl=64 time=1.38 ms
64 bytes from 192.168.88.1: icmp_seq=83 ttl=64 time=6.85 ms
64 bytes from 192.168.88.1: icmp_seq=84 ttl=64 time=1.05 ms
64 bytes from 192.168.88.1: icmp_seq=85 ttl=64 time=1.24 ms
64 bytes from 192.168.88.1: icmp_seq=86 ttl=64 time=1.37 ms
64 bytes from 192.168.88.1: icmp_seq=87 ttl=64 time=2.08 ms
64 bytes from 192.168.88.1: icmp_seq=88 ttl=64 time=1.31 ms
64 bytes from 192.168.88.1: icmp_seq=89 ttl=64 time=33.6 ms
64 bytes from 192.168.88.1: icmp_seq=90 ttl=64 time=20.1 ms
64 bytes from 192.168.88.1: icmp_seq=91 ttl=64 time=43.3 ms
64 bytes from 192.168.88.1: icmp_seq=92 ttl=64 time=51.9 ms
64 bytes from 192.168.88.1: icmp_seq=93 ttl=64 time=0.956 ms
64 bytes from 192.168.88.1: icmp_seq=94 ttl=64 time=1.27 ms
64 bytes from 192.168.88.1: icmp_seq=95 ttl=64 time=25.7 ms
64 bytes from 192.168.88.1: icmp_seq=99 ttl=64 time=1.65 ms
64 bytes from 192.168.88.1: icmp_seq=100 ttl=64 time=4.76 ms
^C
--- 192.168.88.1 ping statistics ---
100 packets transmitted, 91 received, 9% packet loss, time 99335ms
rtt min/avg/max/mdev = 0.851/43.558/1010.933/159.414 ms, pipe 2
My client is just idling and sending pings. But despite this, there are these weird packet losses.
For things to test, I “downgraded” the AP channel-width from first floor to 20mhz. The same I did for my hap lite (channel: 2452/20/gn(18dBm)). Channel 1 and channel 9 - both on 20mhz. No chance to have any overlapping channels. Just not possible.
Now watching how things are going
Uff, that didnt take long to find out - does not help anything.
inf ~ ping 192.168.88.1
PING 192.168.88.1 (192.168.88.1) 56(84) bytes of data.
64 bytes from 192.168.88.1: icmp_seq=1 ttl=64 time=16.3 ms
64 bytes from 192.168.88.1: icmp_seq=2 ttl=64 time=39.2 ms
64 bytes from 192.168.88.1: icmp_seq=3 ttl=64 time=1.21 ms
64 bytes from 192.168.88.1: icmp_seq=4 ttl=64 time=14.0 ms
64 bytes from 192.168.88.1: icmp_seq=5 ttl=64 time=1.20 ms
64 bytes from 192.168.88.1: icmp_seq=6 ttl=64 time=3.91 ms
64 bytes from 192.168.88.1: icmp_seq=7 ttl=64 time=1.20 ms
64 bytes from 192.168.88.1: icmp_seq=8 ttl=64 time=13.1 ms
64 bytes from 192.168.88.1: icmp_seq=9 ttl=64 time=1.23 ms
64 bytes from 192.168.88.1: icmp_seq=14 ttl=64 time=267 ms
64 bytes from 192.168.88.1: icmp_seq=15 ttl=64 time=85.2 ms
64 bytes from 192.168.88.1: icmp_seq=16 ttl=64 time=48.6 ms
64 bytes from 192.168.88.1: icmp_seq=23 ttl=64 time=22.1 ms
64 bytes from 192.168.88.1: icmp_seq=24 ttl=64 time=84.0 ms
64 bytes from 192.168.88.1: icmp_seq=25 ttl=64 time=1.99 ms
64 bytes from 192.168.88.1: icmp_seq=26 ttl=64 time=1.81 ms
64 bytes from 192.168.88.1: icmp_seq=27 ttl=64 time=21.1 ms
64 bytes from 192.168.88.1: icmp_seq=28 ttl=64 time=26.6 ms
64 bytes from 192.168.88.1: icmp_seq=29 ttl=64 time=1.29 ms
64 bytes from 192.168.88.1: icmp_seq=30 ttl=64 time=1.27 ms
64 bytes from 192.168.88.1: icmp_seq=31 ttl=64 time=15.1 ms
64 bytes from 192.168.88.1: icmp_seq=32 ttl=64 time=1.26 ms
64 bytes from 192.168.88.1: icmp_seq=33 ttl=64 time=1.19 ms
64 bytes from 192.168.88.1: icmp_seq=34 ttl=64 time=53.2 ms
64 bytes from 192.168.88.1: icmp_seq=35 ttl=64 time=1.31 ms
64 bytes from 192.168.88.1: icmp_seq=36 ttl=64 time=74.3 ms
64 bytes from 192.168.88.1: icmp_seq=37 ttl=64 time=18.9 ms
^C
--- 192.168.88.1 ping statistics ---
37 packets transmitted, 27 received, 27.027% packet loss, time 36166ms
rtt min/avg/max/mdev = 1.194/30.272/266.800/53.018 ms
While I am pinging and seing the losses, all other clients seem to be idling.
[admin@MikroTik] /interface wireless> registration-table print interval=1
# INTERFACE RADIO-NAME MAC-ADDRESS AP SIGNAL-STRENGTH TX-RATE UPTIME
0 wlan1 A8:7E:EA:55:9F:10 no -71dBm@HT20-5 24Mbps 8m19s
1 wlan1 2CC81B432764 2C:C8:1B:43:27:64 no -86dBm@1Mbps 26Mb... 8m18s
2 wlan1 FC:49:2D:10:BE:1A no -72dBm@1Mbps 72.2... 8m17s
3 wlan1 68:A4:0E:23:A9:69 no -70dBm@1Mbps 5.5Mbps 8m16s
4 wlan1 76:6E:4F:6A:81:57 no -73dBm@1Mbps 26Mb... 8m2s
5 wlan1 B8:C3:85:AA:5E:2E no -56dBm@1Mbps 11Mbps 5m45s
I assume, the hap is taking a deep breath. Because of all the work he has to get done. Limited hardware.
Have you tried configuring it as an accesspoint instead of a router? Might take some workload away from the device.
Could you set encryption to wpa2-aes only?
37 packets transmitted, 27 received, 27.027% packet loss, time 36166ms
rtt min/avg/max/mdev = 1.194/30.272/266.800/53.018 ms
Where is the loss (I would expect to see it in one of the 37 lines as well…)?
That is the kind of pattern I saw as well. Not a problem when just browsing, but very irritating when doing audio chat and conferencing.
As my hAP mini was a freebie from the MUM and I did not want to spend too much time on this, I just ordered a hAP ac2 and it was fixed.
Of course I am now on 5 GHz but I think it works OK on 2 GHz as well, will try to test that later.
Just for reference, the other AP rocking the wifi.
sequence 10, 11, 12, 13 is missing.
Indeed…now I see, and more is missing.
Did you read my other remarks as well?
Doing video conferencing or even just audio calls, this is hardly possible with such a) lost packets and b) packets arriving out of order.
How can I set it as AP instead of router? I unchecked the "Firewall Router" checkbox on Quickset. That apparently removed all firewall filter rules. Did you mean that?
I just disabled WPA and left only WPA2. Lets see.
/interface wireless security-profiles
set [ find default=yes ] authentication-types=wpa2-psk eap-methods="" mode=dynamic-keys supplicant-identity=MikroTik
In my case the AP was operating in bridge mode (no NAT or routing) on a VLAN on the ethernet link to the main router.
This did not influence the behavior I think, which appears to be in the WLAN interface. I will try this evening if the 2GHz WLAN interface of the hAP ac2 (which is at the same location) exhibits this same behavior. The 2 GHz WLAN on my RB2011 did not have this problem.
Quickset is not the proper way to make changes to your config, either use CLI, Webfig or Winbox.
In case of accesspoint, it is sufficient to have a bridge, add all interfaces to it and that’s it.
I just disabled WPA and left only WPA2. Lets see.
/interface wireless security-profiles
set [ find default=yes ] authentication-types=wpa2-psk eap-methods=“” mode=dynamic-keys supplicant-identity=MikroTik
>
This will do goodIn my humble eyes this is a quite OK signal. It has a a good SNR and OK signal strength as well. So why do I see all these issues then?
Disabling Firewall router MAYBE not the best idea in my case. Someone already trying to login from outside. ROFL
Despite all adjustments, packet loss is still unchanged.
# jan/25/2022 13:36:52 by RouterOS 6.48.6
#
# model = RB941-2nD
/interface bridge
add admin-mac=08:55:31:E4:E4:C5 auto-mac=no comment=defconf name=bridge
/interface wireless
set [ find default-name=wlan1 ] band=2ghz-onlyn country=austria disabled=no distance=indoors frequency=2452 installation=indoor mode=\
ap-bridge ssid=jupiter wireless-protocol=802.11
/interface list
add comment=defconf name=WAN
add comment=defconf name=LAN
/interface wireless security-profiles
set [ find default=yes ] authentication-types=wpa2-psk eap-methods="" mode=dynamic-keys supplicant-identity=MikroTik
/ip pool
add name=dhcp ranges=192.168.88.10-192.168.88.254
/ip dhcp-server
add address-pool=dhcp disabled=no interface=bridge name=defconf
/interface bridge port
add bridge=bridge comment=defconf interface=ether2
add bridge=bridge comment=defconf interface=ether3
add bridge=bridge comment=defconf interface=ether4
add bridge=bridge comment=defconf interface=pwr-line1
add bridge=bridge comment=defconf interface=wlan1
/ip neighbor discovery-settings
set discover-interface-list=LAN
/interface list member
add comment=defconf interface=bridge list=LAN
add comment=defconf interface=ether1 list=WAN
/ip address
add address=192.168.88.1/24 comment=defconf interface=bridge network=192.168.88.0
/ip dhcp-client
add comment=defconf disabled=no interface=ether1
/ip dhcp-server network
add address=192.168.88.0/24 comment=defconf gateway=192.168.88.1
/ip dns
set allow-remote-requests=yes
/ip dns static
add address=192.168.88.1 comment=defconf name=router.lan
add address=192.168.88.244 name=zelenka.home.arpa
/ip firewall filter
add action=accept chain=forward comment="defconf: accept in ipsec policy" ipsec-policy=in,ipsec
add action=accept chain=forward comment="defconf: accept out ipsec policy" ipsec-policy=out,ipsec
add action=fasttrack-connection chain=forward comment="defconf: fasttrack" connection-state=established,related
add action=accept chain=forward comment="defconf: accept established,related, untracked" connection-state=\
established,related,untracked
add action=drop chain=forward comment="defconf: drop invalid" connection-state=invalid
add action=drop chain=forward comment="defconf: drop all from WAN not DSTNATed" connection-nat-state=!dstnat connection-state=new \
in-interface-list=WAN
add action=accept chain=input protocol=icmp
add action=accept chain=input connection-state=established
add action=accept chain=input connection-state=related
add action=drop chain=input in-interface-list=!LAN
/ip firewall nat
add action=masquerade chain=srcnat comment="defconf: masquerade" ipsec-policy=out,none out-interface-list=WAN
/system clock
set time-zone-name=Europe/Vienna
/system package update
set channel=long-term
/system routerboard settings
set auto-upgrade=yes
/tool mac-server
set allowed-interface-list=LAN
/tool mac-server mac-winbox
set allowed-interface-list=LAN
Lol…so you want it to behave as router, and not as access-point (which you mentioned in the title).
Reset config and start configuring again…sorry for my advise.