I've had the hAP ax3 for half a year. It came with RouterOS v7.14.2. After getting a bit familiar with the Winbox interface, I went on and upgraded to v7.15.3 and after a few days I noticed that wifi signal was dropping from time to time - this wasn't too good, especially since I work at home and I'm in calls during the day. So, I read the forums and people were saying (at the time) that v7.14.3 should work fine, so I downgraded to that.
It's been about four months since the downgrade, so I wanted to try a new upgrade, to see if I would face the same problem(s). Today I upgraded to v7.18.1 and after merely one hour my wifi dropped again - all wifi devices in the house get disconnected. I also noticed that the 5GHz connection is dropping more often, but 2.4GHz is also dropping.
So I would like to troubleshoot this, but I have no idea how (I'm not a network specialist) or maybe a hint on where to look for some ideas.
Re: hAP ax3 issues with wireless after upgrade
You might want to read this topic:
viewtopic.php?t=208199
Can you share your config, just to make sure there are no strange settings in there?
Remove serial and any other private info, post between code tags by using the </> button.
viewtopic.php?t=208199
Can you share your config, just to make sure there are no strange settings in there?
Code: Select all
/export file=anynameyoulikeRe: hAP ax3 issues with wireless after upgrade
Yes, here's my config:Can you share your config, just to make sure there are no strange settings in there?
Remove serial and any other private info, post between code tags by using the </> button.Code: Select all/export file=anynameyoulike
Code: Select all
# 2025-03-10 18:35:03 by RouterOS 7.14.3
# software id = XQ6L-0KNT
#
# model = C53UiG+5HPaxD2HPaxD
/interface bridge
add admin-mac=D4:01:C3:BE:DA:66 auto-mac=no comment=defconf name=Local
/interface wifi
set [ find default-name=wifi1 ] channel.band=5ghz-ax .frequency=5250-5330 \
.skip-dfs-channels=10min-cac .width=20/40/80mhz configuration.country=\
Romania .mode=ap .ssid=Family disabled=no mtu=1500 \
security.authentication-types=wpa2-psk .ft=yes .ft-over-ds=yes
set [ find default-name=wifi2 ] channel.skip-dfs-channels=10min-cac \
configuration.country=Romania .mode=ap .ssid=Family24 disabled=no \
security.authentication-types=wpa2-psk .ft=yes .ft-over-ds=yes
/interface wireguard
add listen-port=13231 mtu=1420 name=wireguard1
/interface pppoe-client
add add-default-route=yes disabled=no interface=ether1 name=Internet \
use-peer-dns=yes user=XYZ123
/interface list
add comment=defconf name=WAN
add comment=defconf name=LAN
/ip pool
add name=default-dhcp ranges=192.168.88.10-192.168.88.254
add name=dhcp_pool1 ranges=10.11.12.100-10.11.12.254
/ip dhcp-server
add address-pool=default-dhcp disabled=yes interface=Local name=defconf
add address-pool=dhcp_pool1 always-broadcast=yes interface=Local name=dhcp1
/interface bridge port
add bridge=Local comment=defconf interface=ether2
add bridge=Local comment=defconf interface=ether3
add bridge=Local comment=defconf interface=ether4
add bridge=Local comment=defconf interface=ether5
add bridge=Local comment=defconf interface=wifi1
add bridge=Local comment=defconf interface=wifi2
/ip neighbor discovery-settings
set discover-interface-list=LAN
/interface detect-internet
set detect-interface-list=all
/interface list member
add comment=defconf interface=Local list=LAN
add comment=defconf interface=ether1 list=WAN
add interface=Internet list=WAN
/interface wireguard peers
add allowed-address=10.11.13.5/32 interface=wireguard1 public-key=\
"3/"
/ip address
add address=10.11.12.1/24 comment=defconf interface=Local network=10.11.12.0
add address=10.11.13.1/24 interface=wireguard1 network=10.11.13.0
/ip dhcp-client
add comment=defconf disabled=yes interface=ether1
/ip dhcp-server lease
add address=10.11.12.77 mac-address=70:85:C2:41:6A:2B
add address=10.11.12.2 client-id=1:d8:3a:dd:59:c3:19 mac-address=\
D8:3A:DD:59:C3:19 server=dhcp1
/ip dhcp-server network
add address=10.11.12.0/24 dns-server=10.11.12.2 gateway=10.11.12.1
/ip dns
set allow-remote-requests=yes
/ip dns static
add address=192.168.88.1 comment=defconf name=router.lan
add address=10.11.12.77 regexp=".*\\te"
/ip firewall filter
add action=accept chain=input src-address=10.11.13.0/24
add action=accept chain=input comment="Allow Wireguard" dst-port=13231 \
protocol=udp
add action=accept chain=input comment=\
"defconf: accept established,related,untracked" connection-state=\
established,related,untracked
add action=drop chain=input comment="defconf: drop invalid" connection-state=\
invalid
add action=accept chain=input comment="defconf: accept ICMP" protocol=icmp
add action=accept chain=input comment=\
"defconf: accept to local loopback (for CAPsMAN)" dst-address=127.0.0.1
add action=drop chain=input comment="defconf: drop all not coming from LAN" \
in-interface-list=!LAN
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 hw-offload=yes
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
/ip firewall nat
add action=masquerade chain=srcnat comment="defconf: masquerade" \
ipsec-policy=out,none out-interface-list=WAN
add action=masquerade chain=srcnat out-interface-list=WAN
add action=dst-nat chain=dstnat dst-port=11111 in-interface=Internet \
protocol=udp to-addresses=10.11.12.77 to-ports=11111
add action=dst-nat chain=dstnat comment=ttt dst-port=5111 \
in-interface=Internet protocol=udp to-addresses=10.11.12.77 to-ports=\
5111
add action=dst-nat chain=dstnat dst-port=5111 in-interface=Internet \
protocol=tcp to-addresses=10.11.12.77 to-ports=5111
add action=dst-nat chain=dstnat comment="HTTP viz" dst-port=80 \
in-interface=Internet protocol=tcp to-addresses=10.11.12.77 to-ports=80
add action=dst-nat chain=dstnat dst-port=443 in-interface=Internet protocol=\
tcp to-addresses=10.11.12.77 to-ports=443
/ipv6 firewall address-list
add address=::/128 comment="defconf: unspecified address" list=bad_ipv6
add address=::1/128 comment="defconf: lo" list=bad_ipv6
add address=fec0::/10 comment="defconf: site-local" list=bad_ipv6
add address=::ffff:0.0.0.0/96 comment="defconf: ipv4-mapped" list=bad_ipv6
add address=::/96 comment="defconf: ipv4 compat" list=bad_ipv6
add address=100::/64 comment="defconf: discard only " list=bad_ipv6
add address=2001:db8::/32 comment="defconf: documentation" list=bad_ipv6
add address=2001:10::/28 comment="defconf: ORCHID" list=bad_ipv6
add address=3ffe::/16 comment="defconf: 6bone" list=bad_ipv6
/ipv6 firewall filter
add action=accept chain=input comment=\
"defconf: accept established,related,untracked" connection-state=\
established,related,untracked
add action=drop chain=input comment="defconf: drop invalid" connection-state=\
invalid
add action=accept chain=input comment="defconf: accept ICMPv6" protocol=\
icmpv6
add action=accept chain=input comment="defconf: accept UDP traceroute" \
dst-port=33434-33534 protocol=udp
add action=accept chain=input comment=\
"defconf: accept DHCPv6-Client prefix delegation." dst-port=546 protocol=\
udp src-address=fe80::/10
add action=accept chain=input comment="defconf: accept IKE" dst-port=500,4500 \
protocol=udp
add action=accept chain=input comment="defconf: accept ipsec AH" protocol=\
ipsec-ah
add action=accept chain=input comment="defconf: accept ipsec ESP" protocol=\
ipsec-esp
add action=accept chain=input comment=\
"defconf: accept all that matches ipsec policy" ipsec-policy=in,ipsec
add action=drop chain=input comment=\
"defconf: drop everything else not coming from LAN" in-interface-list=\
!LAN
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 packets with bad src ipv6" src-address-list=bad_ipv6
add action=drop chain=forward comment=\
"defconf: drop packets with bad dst ipv6" dst-address-list=bad_ipv6
add action=drop chain=forward comment="defconf: rfc4890 drop hop-limit=1" \
hop-limit=equal:1 protocol=icmpv6
add action=accept chain=forward comment="defconf: accept ICMPv6" protocol=\
icmpv6
add action=accept chain=forward comment="defconf: accept HIP" protocol=139
add action=accept chain=forward comment="defconf: accept IKE" dst-port=\
500,4500 protocol=udp
add action=accept chain=forward comment="defconf: accept ipsec AH" protocol=\
ipsec-ah
add action=accept chain=forward comment="defconf: accept ipsec ESP" protocol=\
ipsec-esp
add action=accept chain=forward comment=\
"defconf: accept all that matches ipsec policy" ipsec-policy=in,ipsec
add action=drop chain=forward comment=\
"defconf: drop everything else not coming from LAN" in-interface-list=\
!LAN
/system clock
set time-zone-autodetect=no time-zone-name=Europe/Bucharest
/system note
set show-at-login=no
/system ntp client
set enabled=yes
/system ntp client servers
add address=1.europe.pool.ntp.org
add address=0.europe.pool.ntp.org
add address=2.europe.pool.ntp.org
/tool mac-server
set allowed-interface-list=LAN
/tool mac-server mac-winbox
set allowed-interface-list=LAN
Re: hAP ax3 issues with wireless after upgrade
Try setting DTIM = 3. That's a recommended setting years ago to keep Apple Devices connected to Wi-Fi. Not sure if It's actually still the case, but it *could* help with saving battery.
And if still problems can you try disabling FT? You are using different SSIDs so it doesnt even work
Also check the log output maybe there is a reason given.
But 7.18 has a lot of fixes for Wi-Fi.
And if still problems can you try disabling FT? You are using different SSIDs so it doesnt even work
Also check the log output maybe there is a reason given.
But 7.18 has a lot of fixes for Wi-Fi.
Re: hAP ax3 issues with wireless after upgrade
Nothing really interesting, apart from frequency choice and FT.
Frequencies for 80MHz bandwidth is from 5170-5250 or 5250 - 5330 (assuming Ceee this would be channel 36 or 52).
I have very good experience with:
The RB will choose by scanning the frequency usage and perform this (background) scan every 6 to 8 hours.
Remove this (twice) as there is nothing to transition to (as you are using separate SSID's for 2.4 and 5 GHz:
You can give it a try to find out if this improves anything.
[Update]
Frequencies for 80MHz bandwidth is from 5170-5250 or 5250 - 5330 (assuming Ceee this would be channel 36 or 52).
I have very good experience with:
Code: Select all
/interface wifi channel
add disabled=no name=CHAN-5G reselect-interval=6h..8h skip-dfs-channels=10min-cac width=20/40/80mhzRemove this (twice) as there is nothing to transition to (as you are using separate SSID's for 2.4 and 5 GHz:
Code: Select all
.ft=yes .ft-over-ds=yes [Update]
Nope, also Apple recoomends setting it to 1 (default).Try setting DTIM = 3. That's a recommended setting years ago to keep Apple Devices connected to Wi-Fi. Not sure if It's actually still the case, but it *could* help with saving battery.
You might want to add wireless debug logging (add it in /system/log).Also check the log output maybe there is a reason given.
Indeed!But 7.18 has a lot of fixes for Wi-Fi.
Re: hAP ax3 issues with wireless after upgrade
Is there an official source for this urban legend? When googling for "apple dtim" I can only find results from several forums/communities/private blogs (10 years ago) claiming something like this. But I cant find any official Apple resource for thisTry setting DTIM = 3. That's a recommended setting years ago to keep Apple Devices connected to Wi-Fi. Not sure if It's actually still the case, but it *could* help with saving battery.
And if still problems can you try disabling FT? You are using different SSIDs so it doesnt even work
Also check the log output maybe there is a reason given.
But 7.18 has a lot of fixes for Wi-Fi.
Re: hAP ax3 issues with wireless after upgrade
Likewise also seeing problems, I've managed to narrow it down to if there is a device streaming video on the network the 5Ghz interface will crash out every so often and drop all 5Ghz devices.
Re: hAP ax3 issues with wireless after upgrade
Nah i dont know anything other than that it all appears to come from some random persons twitter post that is long deleted.Is there an official source for this urban legend? When googling for "apple dtim" I can only find results from several forums/communities/private blogs (10 years ago) claiming something like this. But I cant find any official Apple resource for thisTry setting DTIM = 3. That's a recommended setting years ago to keep Apple Devices connected to Wi-Fi. Not sure if It's actually still the case, but it *could* help with saving battery.
And if still problems can you try disabling FT? You are using different SSIDs so it doesnt even work
Also check the log output maybe there is a reason given.
But 7.18 has a lot of fixes for Wi-Fi.
When I was running Unifi AC APs i heard a lot about that recommendation, and it (seemed to) fix some connection issues with iPhones.
Most things about this I now find on ubis subreddit.
Maybe it's an Ubiquiti thing?
But then again theres people complaining about mail delivery issues with DTIM 3 on the Apple Forum:
https://discussions.apple.com/thread/250342880
Re: hAP ax3 issues with wireless after upgrade
If you can recreate it, then it's definitely worth shooting a ticket to support@mikrotik.comLikewise also seeing problems, I've managed to narrow it down to if there is a device streaming video on the network the 5Ghz interface will crash out every so often and drop all 5Ghz devices.
Re: hAP ax3 issues with wireless after upgrade
It used to be mentioned on the Apple website, and indeed...it is gone.Is there an official source for this urban legend? When googling for "apple dtim" I can only find results from several forums/communities/private blogs (10 years ago) claiming something like this. But I cant find any official Apple resource for this
Re: hAP ax3 issues with wireless after upgrade
Thank you all for the suggestions. I upgraded back to 7.18.1 and changed some things.
For the 5GHz interface:
I didn't touch DTIM as I don't have any apple devices in my home.
I'll be monitoring to see how this works. I will check, as @RedOrion said, to see if streaming has anything to do with my problems.
For the 5GHz interface:
Code: Select all
.frequency=5170-5250 .ft=no .ft-over-ds=no reselect-interval=6h..8h
I'll be monitoring to see how this works. I will check, as @RedOrion said, to see if streaming has anything to do with my problems.
Re: hAP ax3 issues with wireless after upgrade
Hope it helps. As you are using the exact range of channel 36, no need to do a reselect.
Re: hAP ax3 issues with wireless after upgrade
Can you explain a bit? Or point me to some documentation about this?Hope it helps. As you are using the exact range of channel 36, no need to do a reselect.
Re: hAP ax3 issues with wireless after upgrade
https://en.wikipedia.org/wiki/List_of_W ... /ac/ax/be)
https://help.mikrotik.com/docs/spaces/R ... properties
https://help.mikrotik.com/docs/spaces/R ... properties
Specifies when the interface should rescan channel availability and select the most appropriate one to use. Specifying interval will allow the system to select this interval dynamically and randomly. This helps to avoid a situation when many APs at the same time scan the network, select the same channel, and prefer to use it at the same time. reselect-interval uses a background scan.
The reselect process will choose the most suitable channel considering the number of networks in the channel, channel usage, and overlap with networks in adjacent channels. It can be used with a list of frequencies defined, or with frequency not set - using all supported frequencies.
Re: hAP ax3 issues with wireless after upgrade
As you are using the exact range of channel 36, no need to do a reselect.
Since width property doesn't define channel layout any more (in old times that would be equivalent to setting XXXX), AP could reselect e.g. from 5180-Ceee to e.g. 5200-eCee. It does seem that MT jumped (or was, by using chipset vendor's reference drivers, forced to jump) to the common practice of using Ce(ee(eeee)) channel layout, the probability of changing channel is not big.
BTW, if driver fails to follow standard channels, then using frequency=5170-5250 might cause settling on unusable radio configuration. Better would be setting of frequency=5180-5240:20 (which is the same as setting frequency=5180,5200,5220,5240) ... which constrains automagic to probe only channels with standard center frequencies.
Re: hAP ax3 issues with wireless after upgrade
Coming back to this: it's already three days since I changed my config and I didn't get any drop. I'm working from home today and besides the laptop connection, I tried with Netflix and Youtube streaming on my Android TV at the same time and it all seems to work.
Re: hAP ax3 issues with wireless after upgrade
Do we think that it is the following config that improved functionality under 7.18.1:
I see the explanation and usage in the docs:
https://help.mikrotik.com/docs/spaces/R ... properties
"Specifies when the interface should rescan channel availability and select the most appropriate one to use. Specifying interval will allow the system to select this interval dynamically and randomly. This helps to avoid a situation when many APs at the same time scan the network, select the same channel, and prefer to use it at the same time. reselect-interval uses a background scan.
The reselect process will choose the most suitable channel considering the number of networks in the channel, channel usage, and overlap with networks in adjacent channels. It can be used with a list of frequencies defined, or with frequency not set - using all supported frequencies."
Can someone elaborate on the behavior caused in this case? The frequency range selected is 80mhz wide. So, I don't understand how a reselection would work? Unless this config limits the channel width to 40mhz, and the reselection is some 40mhz range within the 80 that is 5170-5250.
Or do we feel that the ".ft=no .ft-over-ds=no" is the relevant portion with respect to the improvement?
Code: Select all
.frequency=5170-5250 .ft=no .ft-over-ds=no reselect-interval=6h..8hhttps://help.mikrotik.com/docs/spaces/R ... properties
"Specifies when the interface should rescan channel availability and select the most appropriate one to use. Specifying interval will allow the system to select this interval dynamically and randomly. This helps to avoid a situation when many APs at the same time scan the network, select the same channel, and prefer to use it at the same time. reselect-interval uses a background scan.
The reselect process will choose the most suitable channel considering the number of networks in the channel, channel usage, and overlap with networks in adjacent channels. It can be used with a list of frequencies defined, or with frequency not set - using all supported frequencies."
Can someone elaborate on the behavior caused in this case? The frequency range selected is 80mhz wide. So, I don't understand how a reselection would work? Unless this config limits the channel width to 40mhz, and the reselection is some 40mhz range within the 80 that is 5170-5250.
Or do we feel that the ".ft=no .ft-over-ds=no" is the relevant portion with respect to the improvement?
Re: hAP ax3 issues with wireless after upgrade
Reselect might choose a different Control channel, still the same frequencies.
I think disabling FT is of most influence.
I think disabling FT is of most influence.
Re: hAP ax3 issues with wireless after upgrade
Thanks.Reselect might choose a different Control channel, still the same frequencies.
I think disabling FT is of most influence.
If reselect chooses a different control channel, and the width is 80mhz, and the frequency range is 5170-5250, then by doing so it changes between ceee, ecee, eece, and eeec, right?
That way, the frequency range remains 5170-5250, the width remains 80mhz, and the control frequency changed between the first and fourth position of that 80mhz range.
Did I get that right?
Re: hAP ax3 issues with wireless after upgrade
That's correct. I prefer to specify a wider frequency range so the accesspoint has a wider bandwidth to choose from (instead of 80MHz).
Re: hAP ax3 issues with wireless after upgrade
Great approach!That's correct. I prefer to specify a wider frequency range so the accesspoint has a wider bandwidth to choose from (instead of 80MHz).
Thank you (as always)!
Re: hAP ax3 issues with wireless after upgrade
Reselect might choose a different Control channel, still the same frequencies.
Technically 80MHz channel on e.g. AX is one 20MHz "full featured" channel (marked with C in ROS) plus supplemental channels (adjacent, which side depends on actual channel layout; marked with e in ROS). And the point of it is that older gen clients might only support 20MHz channels (802.11a, using only C channel) or 40MHz channels (802.11g, using C and single adjacent e, whether it's eC or Ce depends on actual layout used by AP and how it fits into raster of standard channels).
So when AP reselects from e.g. 5200/eCee to e.g. 5220/eeCe ... some devices might see reselect from 5200 to 5220 (which is definitely different channel) and some devices might see reselect from 5200/eC to 5220/Ce (which translates to reselect from 5170-5210 to 5210-5250; again different channels used). And only newer gen devices (AC and newer) will see reselect from 5170-5250 to 5170-5250 (but with C moving from 5190-5210 to 5210-5230), so same frequency range.
Re: hAP ax3 issues with wireless after upgrade
Meh... after a few days of working, I'm back to being disconnected at random... I don't have the time and energy to start checking logs and troubleshooting this. I'll go back to 7.14.3.
Re: hAP ax3 issues with wireless after upgrade
7.14.3 is the only one that works properly on my AX3, I've stopped bothering trying to upgrade and I have no problems. I've wasted countless hours trying to get it stable.
Short or a major security issue, or a confirmed acknowledgement and resolution, I won't be upgrading again.
Short or a major security issue, or a confirmed acknowledgement and resolution, I won't be upgrading again.