"not responding" - f.k.a. SA Query timeout

martinii · Thu Aug 17, 2023 10:53 pm

Hi all,

I have problem with my father's phone (Samsung A3 2016, stock OS) in my wifi network. I had Mikrotik hAP lite before and there was absolutely no problems! Now I have Mikrotik hAP ax2 and my Dad can't connect to my wifi because of SA Query timeout error. I have few devices (phones, laptops and TV) in my wireless network and there is problem ONLY with this one device... I upgraded router os few times and now i'm on 7.11 stable. I tried Disable PMKID = YES but without success either. Look:

This is part of my configuration:

# 2023-08-17 21:35:25 by RouterOS 7.11
# software id = **ELIDED**
#
# model = C52iG-5HaxD2HaxD
# serial number = XXXXXXXXXXXX
/interface bridge
add name=bridge-LAN
/interface ethernet
set [ find default-name=ether1 ] mac-address=XX:XX:XX:XX:XX:XX
/interface wifiwave2 channel
add band=2ghz-n disabled=no frequency=2447 name=channel-2.4GHz \
    skip-dfs-channels=all width=20mhz
add band=5ghz-ax disabled=no frequency=5280 name=channel-5GHz width=20/40mhz-eC
/interface wifiwave2 security
add authentication-types=wpa2-psk disable-pmkid=yes disabled=no encryption="" \
    name=sec-profile
/interface wifiwave2 configuration
add channel=channel-2.4GHz country=Poland disabled=no mode=ap name=cfg-2.4GHz \
    security=sec-profile ssid=KMPM_nomap
add channel=channel-5GHz country=Poland disabled=no mode=ap name=cfg-5GHz \
    security=sec-profile ssid=KMPM_nomap
/interface wifiwave2
set [ find default-name=wifi2 ] channel=channel-2.4GHz channel.frequency=2447 \
    configuration=cfg-2.4GHz configuration.mode=ap disabled=no name=2.4GHZ
set [ find default-name=wifi1 ] channel=channel-5GHz configuration=cfg-5GHz \
    configuration.mode=ap disabled=no name=5GHz
/ip pool
add name=pool-dhcp ranges=192.168.44.10-192.168.44.35
add name=dhcp_pool1 ranges=192.168.44.2-192.168.44.254
/ip dhcp-server
add address-pool=pool-dhcp insert-queue-before=bottom interface=bridge-LAN \
    lease-time=3d name=dhcp1
/interface bridge port
add bridge=bridge-LAN interface=ether2
add bridge=bridge-LAN interface=ether3
add bridge=bridge-LAN interface=ether4
add bridge=bridge-LAN interface=ether5
add bridge=bridge-LAN interface=5GHz
add bridge=bridge-LAN interface=2.4GHZ
/ip dhcp-server lease
add address=192.168.44.24 client-id=1:a8:9c:ed:4e:b3:ad mac-address=\
    XX:XX:XX:XX:XX:XX server=dhcp1
add address=192.168.44.23 client-id=1:94:be:46:cf:1:76 comment="Tablet Matika" \
    mac-address=XX:XX:XX:XX:XX:XX server=dhcp1
add address=192.168.44.21 client-id=1:78:af:8:80:97:b5 mac-address=\
    XX:XX:XX:XX:XX:XX server=dhcp1
add address=192.168.44.20 client-id=1:20:34:fb:cb:e2:f8 mac-address=\
    XX:XX:XX:XX:XX:XX server=dhcp1
add address=192.168.44.19 client-id=1:8c:c8:cd:59:a2:99 comment="TV SAMSUNG" \
    mac-address=XX:XX:XX:XX:XX:XX server=dhcp1
add address=192.168.44.18 client-id=1:bc:60:a7:cd:db:c5 comment=PS4 \
    mac-address=XX:XX:XX:XX:XX:XX server=dhcp1
/ip dhcp-server network
add address=192.168.44.0/24 gateway=192.168.44.1

Help needed....

Fri Aug 18, 2023 12:22 am

I'm terrible at RouterOS WiFi, but a few things in your config raised questions:

1. Why disable PMKID? According to the docs, "Disabling PMKID can cause compatibility issues with client devices which make use of it."

2. encryption=""? Is that just you being over-zealous with the config sanitization, or do you really have all encryption methods disabled?

gigabyte091 · Fri Aug 18, 2023 6:29 am

I suggest you to send supout file and log to the support. I had similar problem and i sent them file and log but my AC but problem fixed itself...

Fri Aug 18, 2023 8:24 am

Quick response before leaving for the road trip to France...

2. encryption=""? Is that just you being over-zealous with the config sanitization, or do you really have all encryption methods disabled?

If you use WInbox, make sure that section is folded in.
NOT opened and nothing selected. Is not the same.

nescafe2002 · Fri Aug 18, 2023 12:15 pm

Try disabling band steering. I noticed these SA Query Timeout messages just before re-associating with another radio.

https://help.mikrotik.com/docs/display/ ... properties

/interface wifiwave2 configuration set [find] rrm=no wnm=no

martinii · Fri Aug 18, 2023 10:54 pm

I'm terrible at RouterOS WiFi, but a few things in your config raised questions:

1. Why disable PMKID? According to the docs, "Disabling PMKID can cause compatibility issues with client devices which make use of it."

2. encryption=""? Is that just you being over-zealous with the config sanitization, or do you really have all encryption methods disabled?

1. It was only for testing. But without success so returned to default.
2. I missed it out! I had nothing checked indeed... Now i have CCMP and GCMP.

Try disabling band steering. I noticed these SA Query Timeout messages just before re-associating with another radio.

https://help.mikrotik.com/docs/display/ ... properties
Code: Select all
/interface wifiwave2 configuration set [find] rrm=no wnm=no

So you suggest to leave only frequencies?

İmposss · Sat Aug 19, 2023 1:01 am

An issue that came with version 7.11. I reverted to version 7.10.2

nescafe2002 · Sat Aug 19, 2023 3:16 pm

Try disabling band steering. I noticed these SA Query Timeout messages just before re-associating with another radio.
So you suggest to leave only frequencies?

I suggested to disable band steering, as this was introduced in 7.11:

*) wifiwave2 - added "steering" parameters and menu to set up and monitor AP neighbor groups (CLI only)

An issue that came with version 7.11. I reverted to version 7.10.2

Again, band steering is introduced in 7.11, therefore may be related to these issues.

İmposss · Mon Aug 21, 2023 3:20 am

Try disabling band steering. I noticed these SA Query Timeout messages just before re-associating with another radio.

https://help.mikrotik.com/docs/display/ ... properties
Code: Select all
/interface wifiwave2 configuration set [find] rrm=no wnm=no

Hi i tried it doesn't work

/interface wifiwave2 configuration set [find] steering.rrm=no steering.wnm=no

gigabyte091 · Mon Aug 21, 2023 6:41 am

Did you try to contact Mikrotik support ? At this point they maybe can help you more.

martinii · Mon Aug 28, 2023 6:47 pm

I tried disable steering but no luck... Well I feel it doesn't matter what I do - it always doesn't work... On hAP ac lite no problems, on ax2 it still doesn't work...

Mon Aug 28, 2023 7:31 pm

Did you try to contact Mikrotik support ? At this point they maybe can help you more.

Best recommendation to get... create supout.rif, contact support.

İmposss · Mon Aug 28, 2023 7:34 pm

Did you try to contact Mikrotik support ? At this point they maybe can help you more.
Best recommendation to get... create supout.rif, contact support.

I did, waiting for support

maigonis · Tue Aug 29, 2023 1:44 am

Try WPA2 only to isolate issue to security settings.

martinii · Tue Aug 29, 2023 10:47 am

I tried WPA2 only. As well as firmware upgrading, disabling band steering, disabling PMKID, turning off encription, disabling 5GHz radio and rebooting donzens times....

Rox169 · Tue Aug 29, 2023 11:04 am

did you tried to delete/forget the network in mobile and do new connect???

martinii · Tue Aug 29, 2023 2:00 pm

Every time when I made some changes in router settings.

İmposss · Fri Sep 01, 2023 4:02 pm

solution for me:

/interface/wifiwave2/configuration> set [find] security.connect-priority=0/1

alibloke · Mon Sep 25, 2023 10:12 am

This appears to work, my laptop has been able to fast roam for the first time and the dreaded SA Query Timeout message is gone. I must admit I don't understand why and I'm concerned that it's working at the cost of security, specifically MacStealer attacks as per this post:
viewtopic.php?t=198228#p1016424

Can anyone elaborate on what this setting actually does?

ToTheFull · Mon Sep 25, 2023 1:01 pm

solution for me:

/interface/wifiwave2/configuration> set [find] security.connect-priority=0/1

This appears to work, my laptop has been able to fast roam for the first time and the dreaded SA Query Timeout message is gone. I must admit I don't understand why and I'm concerned that it's working at the cost of security, specifically MacStealer attacks as per this post:
viewtopic.php?t=198228#p1016424

Can anyone elaborate on what this setting actually does?

Yes please do, tired of this in my logs all the time when someone walks into the kitchen.

/log print where message~"C6"
 09-22 12:24:54 wireless,info C6:6B:0C@wifi1 connected, signal strength -61
 09-22 12:26:44 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -73
 09-22 12:26:44 wireless,info C6:6B:0C@wifi1 connected, signal strength -75
 09-22 12:27:26 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -68
 09-22 12:27:27 wireless,info C6:6B:0C@wifi1 connected, signal strength -71
 09-22 12:27:55 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -69
 09-22 12:27:55 wireless,info C6:6B:0C@wifi1 connected, signal strength -71
 09-22 12:29:58 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -68
 09-22 12:30:22 wireless,info C6:6B:0C@wifi1 connected, signal strength -68
 09-22 12:31:44 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -71
 09-22 12:31:55 dhcp,info defconf deassigned 192.168.0.106 for C6:6B:0C
 09-22 12:31:56 dhcp,info defconf assigned 192.168.0.106 for C6:6B:0C 
 09-22 12:31:58 wireless,info C6:6B:0C@wifi1 connected, signal strength -71
 09-22 12:32:24 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -73
 09-22 12:32:24 wireless,info C6:6B:0C@wifi1 connected, signal strength -75
 09-22 12:32:33 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -72
 09-22 12:32:34 wireless,info C6:6B:0C@wifi1 connected, signal strength -75
 09-22 12:32:38 dhcp,info defconf deassigned 192.168.0.106 for C6:6B:0C 
 09-22 12:32:39 dhcp,info defconf assigned 192.168.0.106 for C6:6B:0C 
 09-22 12:32:49 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -70
 09-22 12:32:50 wireless,info C6:6B:0C@wifi1 connected, signal strength -73
 09-22 12:34:18 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -77
 09-22 12:34:19 wireless,info C6:6B:0C@wifi1 connected, signal strength -76
 09-22 12:38:17 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -71
 09-22 12:38:17 wireless,info C6:6B:0C@wifi1 connected, signal strength -70
 09-22 12:42:13 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -70
 09-22 12:42:20 wireless,info C6:6B:0C@wifi1 connected, signal strength -65
 09-22 12:47:26 wireless,info C6:6B:0C@wifi1 disconnected, connection lost, signal strength -64
 09-22 14:48:23 wireless,info C6:6B:0C@wifi1 connected, signal strength -62
 09-22 14:55:07 wireless,info C6:6B:0C@wifi1 disconnected, connection lost, signal strength -68
 09-22 16:47:44 wireless,info C6:6B:0C@wifi1 connected, signal strength -62
 09-22 16:52:48 wireless,info C6:6B:0C@wifi1 disconnected, connection lost, signal strength -72
 09-22 17:00:05 wireless,info C6:6B:0C@wifi1 connected, signal strength -68
 09-22 17:01:09 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -58
 09-22 17:01:10 wireless,info C6:6B:0C@wifi1 connected, signal strength -66
 09-22 17:01:36 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -71
 09-22 17:01:37 wireless,info C6:6B:0C@wifi1 connected, signal strength -67
 09-22 17:01:53 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -70
 09-22 17:01:59 wireless,info C6:6B:0C@wifi1 connected, signal strength -66
 09-22 17:45:29 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -67
 09-22 17:45:29 wireless,info C6:6B:0C@wifi1 connected, signal strength -68
 09-22 17:51:25 wireless,info C6:6B:0C@wifi1 disconnected, connection lost, signal strength -70
 09-22 19:00:20 wireless,info C6:6B:0C@wifi1 connected, signal strength -63
 09-22 19:06:08 wireless,info C6:6B:0C@wifi1 disconnected, connection lost, signal strength -85
 09-22 22:43:48 wireless,info C6:6B:0C@wifi1 connected, signal strength -52
 09-22 22:44:39 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -66
 09-22 22:44:40 wireless,info C6:6B:0C@wifi1 connected, signal strength -65
 09-22 22:45:01 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -62
 09-22 22:45:01 wireless,info C6:6B:0C@wifi1 connected, signal strength -68
 09-22 22:45:11 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -68
 09-22 22:45:12 wireless,info C6:6B:0C@wifi1 connected, signal strength -67
 09-22 22:51:14 wireless,info C6:6B:0C@wifi1 disconnected, connection lost, signal strength -78
 09-23 11:06:06 wireless,info C6:6B:0C@wifi1 connected, signal strength -70
 09-23 11:09:13 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -66
 09-23 11:09:14 wireless,info C6:6B:0C@wifi1 connected, signal strength -70
 09-23 11:12:12 wireless,info C6:6B:0C@wifi1 disconnected, group key timeout, signal strength -74
 09-23 11:14:23 wireless,info C6:6B:0C@wifi1 connected, signal strength -73
 09-23 11:21:47 wireless,info C6:6B:0C@wifi1 disconnected, connection lost, signal strength -87
 09-23 11:42:52 wireless,info C6:6B:0C@wifi1 connected, signal strength -59
 09-23 11:48:11 wireless,info C6:6B:0C@wifi1 disconnected, connection lost, signal strength -79
 09-23 15:59:09 wireless,info C6:6B:0C@wifi1 connected, signal strength -66
 09-23 16:08:07 wireless,info C6:6B:0C@wifi1 disconnected, connection lost, signal strength -74
 09-23 19:31:54 wireless,info C6:6B:0C@wifi1 connected, signal strength -60
 09-23 19:37:45 wireless,info C6:6B:0C@wifi1 disconnected, connection lost, signal strength -72
 09-23 23:46:56 wireless,info C6:6B:0C@wifi1 connected, signal strength -68
 09-23 23:51:58 wireless,info C6:6B:0C@wifi1 disconnected, connection lost, signal strength -69
 09-24 10:49:40 wireless,info C6:6B:0C@wifi1 connected, signal strength -67
 09-24 10:55:48 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -73
 09-24 10:56:45 wireless,info C6:6B:0C@wifi1 connected, signal strength -68
 09-24 11:07:30 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -73
 09-24 11:07:30 wireless,info C6:6B:0C@wifi1 connected, signal strength -74
 09-24 11:12:18 wireless,info C6:6B:0C@wifi1 disconnected, group key timeout, signal strength -72
 09-24 11:49:45 wireless,info C6:6B:0C@wifi1 connected, signal strength -70
 09-24 11:51:22 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -72
 09-24 11:51:22 wireless,info C6:6B:0C@wifi1 connected, signal strength -70
 09-24 11:52:27 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -65
 09-24 11:52:27 wireless,info C6:6B:0C@wifi1 connected, signal strength -55
 09-24 11:58:33 wireless,info C6:6B:0C@wifi1 disconnected, connection lost, signal strength -86
 09-24 12:23:19 wireless,info C6:6B:0C@wifi1 connected, signal strength -67
 09-24 12:23:54 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -69
 09-24 12:23:54 wireless,info C6:6B:0C@wifi1 connected, signal strength -71
 09-24 12:23:58 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -71
 09-24 12:23:59 wireless,info C6:6B:0C@wifi1 connected, signal strength -69
 09-24 12:26:16 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -69
 09-24 12:26:17 wireless,info C6:6B:0C@wifi1 connected, signal strength -71
 09-24 12:29:21 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -71
 09-24 12:29:22 wireless,info C6:6B:0C@wifi1 connected, signal strength -72
 09-24 12:36:25 wireless,info C6:6B:0C@wifi1 disconnected, connection lost, signal strength -70
 09-24 14:46:34 wireless,info C6:6B:0C@wifi1 connected, signal strength -57
 09-24 14:52:05 wireless,info C6:6B:0C@wifi1 disconnected, connection lost, signal strength -71
 09-24 17:37:33 wireless,info C6:6B:0C@wifi1 connected, signal strength -67
 09-24 17:37:37 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -70
 09-24 17:37:37 wireless,info C6:6B:0C@wifi1 connected, signal strength -75
 09-24 18:05:15 wireless,info C6:6B:0C@wifi1 disconnected, connection lost, signal strength -82
 09-24 18:28:54 wireless,info C6:6B:0C@wifi1 connected, signal strength -56
 09-24 18:34:35 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -72
 09-24 18:34:35 wireless,info C6:6B:0C@wifi1 connected, signal strength -74
 09-24 18:36:03 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -74
 09-24 18:36:03 wireless,info C6:6B:0C@wifi1 connected, signal strength -71
 09-24 18:40:44 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -68
 09-24 18:40:44 wireless,info C6:6B:0C@wifi1 connected, signal strength -69
 09-24 18:41:10 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -73
 09-24 18:41:10 wireless,info C6:6B:0C@wifi1 connected, signal strength -70
 09-24 18:41:13 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -69
 09-24 18:41:14 wireless,info C6:6B:0C@wifi1 connected, signal strength -71
 09-24 18:42:59 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -69
 09-24 18:42:59 wireless,info C6:6B:0C@wifi1 connected, signal strength -69
 09-24 18:45:31 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -68
 09-24 18:45:32 wireless,info C6:6B:0C@wifi1 connected, signal strength -71
 09-24 18:47:16 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -74
 09-24 18:47:17 wireless,info C6:6B:0C@wifi1 connected, signal strength -68
 09-24 18:48:03 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -76
 09-24 18:48:03 wireless,info C6:6B:0C@wifi1 connected, signal strength -72
 09-24 18:50:56 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -69
 09-24 18:50:56 wireless,info C6:6B:0C@wifi1 connected, signal strength -68
 09-24 18:57:22 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -67
 09-24 18:57:23 wireless,info C6:6B:0C@wifi1 connected, signal strength -68
 09-24 18:58:50 wireless,info C6:6B:0Cwifi1 disconnected, SA Query timeout, signal strength -69
 09-24 18:58:51 wireless,info C6:6B:0C@wifi1 connected, signal strength -69
 09-24 19:04:56 wireless,info C6:6B:0C@wifi1 disconnected, connection lost, signal strength -70
 09:20:40 wireless,info C6:6B:0C@wifi1 connected, signal strength -66
 09:23:00 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -71
 09:23:00 wireless,info C6:6B:0C@wifi1 connected, signal strength -69
 09:25:21 wireless,info C6:6B:0C@wifi1 disconnected, SA Query timeout, signal strength -72
 09:25:21 wireless,info C6:6B:0C@wifi1 connected, signal strength -72

brg3466 · Thu Sep 28, 2023 5:17 am

anyone has solution ?

It is weird that in our house, only iPhone14 pro has this "SA query timeout" issue. All other apple devices ( macbook, macbook air, ipad or iphone 12) don't behave like this.

martinii · Mon Oct 02, 2023 4:38 pm

In my case it still doesn't work... The only solution I can see is to give my Dad a new phone.

Santi70 · Fri Nov 17, 2023 2:10 pm

I also have that problem, but only with an iPhone 13, all other devices work fine

jugernautas · Thu Dec 07, 2023 4:18 pm

Hello,
First time here. I have upgraded my cAP ax device from v7.8 to v7.12 and one "Lenovo" laptop started disconnecting often.
Looking at the log I have determined that the problem could be that laptop changes wifi frequencies from 5Ghz to 2Ghz and therefore cAP device waits until it can no longer determine that laptop is connected. After then it lets connect to AP. The duration time offline was about 1 minute.
I could not find any sophisticated information, so I tried changing these 2 values on each frequency radio interface:

connect-group ( string )

APs within the same connect group do not allow more than 1 client device with the same MAC address. This is to prevent malicious authorized users from intercepting traffic intended to other users ('MacStealer' attack) or performing a denial of service attack by spoofing the MAC address of a victim.

Handling of new connections with duplicate MAC addresses depends on the connect-priority of AP interfaces involved.

By default, all APs are assigned the same connect-group.

connect-priority (accept-priority/hold-priority (integers))

Theese parameters determine, how a connection is handled if the MAC address of the client device is the same as that of another active connection to another AP.
If (accept-priority of AP2) < (hold-priority of AP1), a connection to AP2 wil cause the client to be dropped from AP1.
If (accept-priority of AP2) = (hold-priority of AP1), a connection to AP2 will be allowed only if the MAC address can no longer be reached via AP1.
If (accept-priority of AP2) > (hold-priority of AP1), a connection to AP2 will not be accepted.

If omitted, hold-priority is the same as accept-priority.
By default, APs, which perform user authentication, have higher priority (lower integer value), than open APs.

On 2Ghz - Security - Connect Group ("Grupe2") and Connect Priority (0/1)
On 5Ghz - Security - Connect Group ("Grupe5") and Connect Priority (0/1)

For now the laptop works ok, no long disconnections from Wifi. It would be great if someone can explain if this is right way to configure it.

tinodj · Tue Jan 16, 2024 9:28 am

Hit this problem after upgrading from 6 to 7. Was very stable with 6, now on ROS7 is frustrating with this. Happens on iPhone and Mac. Happens on cAP ax and Audience. Solutions here didn’t help

Have anyone found something else?

kurio · Fri Jan 19, 2024 11:05 am

Hit this problem after upgrading from 6 to 7. Was very stable with 6, now on ROS7 is frustrating with this. Happens on iPhone and Mac. Happens on cAP ax and Audience. Solutions here didn’t help Have anyone found something else?

Hello,
Started having this problem with i don't know which version of ROS 7.xx, now running the latest 7.13.2.
Impossible to roam from independent AX2 to AX3: simple connects/disconnects, SA timeouts, no IPv4 DHCP replies, all kinds of crap.
I have tried all the suggestions here and there, but they do not work. All smartphones are android, most of them have issues staying connected when moving from floor to floor (from one hap ax to another).
However, i have noticed a workaround which works on some phones: instead of static phone MAC address switch to randomized MAS addresses.
Is this whole issue is related to the client MAC addresses?
Do i need to configure and run capsman to overcome this critical connectivity problem?

ToTheFull · Fri Jan 19, 2024 12:31 pm

CAPsMAN wont help, also the same on 7.14Beta7 maybe slightly worse than 7.14Beta6.
Anyway, I'm sure someone will be along soon to say it's your config etc...........

erlinden · Fri Jan 19, 2024 2:52 pm

Anyway, I'm sure someone will be along soon to say it's your config etc...........

How do you know his config is correct. There are not a lot of topics where, after sharing the config, there are no improvements to make on the config.

@kurio: As far as I know the client will always use the same MAC address (per SSID), even if it is randomized. No clue why you think it is helping...

In regards to the SA Query timeout problem, it has been solved for me (using CAPsMAN) by setting the connect-priority.

masseselsev · Fri Jan 19, 2024 2:54 pm

Same here on Chateau 18 (7.13.2) with all my AX diveces that are trying to connect to 2Ghz, 5Ghz connections are fine though.
No CAPsMAN, just a single(dual actually) raido.
The devices namely are a couple of Google pixel (6&7) phones, and a pair of laptops with AX211 wifis'.
Also, the devices that are not capable of AX seem to de working just fine,
And it happens randomly -- not all the devices at once.

Maybe the matter does deserve some comment from the staff?

edit. persuaded a part of the devices to connect to 5g only, now this happens both with 2 and 5 ghz (((

Fri Jan 19, 2024 2:57 pm

Then it might be better to create a ticket with supout right after you see it happening.
Because staff does not frequent these forums that often (they sometimes do).

ToTheFull · Fri Jan 19, 2024 3:56 pm

Anyway, I'm sure someone will be along soon to say it's your config etc...........

In regards to the SA Query timeout problem, it has been solved for me (using CAPsMAN) by setting the connect-priority.

Deployed... i'll let YOU Know!

2 name="wifi1" l2mtu=1560 mac-address=18:FD arp-timeout=auto radio-mac=18:FD
   configuration.mode=ap .ssid="002" .country=United Kingdom 
   security.authentication-types=wpa2-psk .encryption=ccmp .passphrase="" 
   .management-protection=allowed .wps=disable .connect-priority=0/1 
   channel.frequency=5180 .band=5ghz-ax .width=20/40/80mhz .skip-dfs-channels=10min-cac

If that isn't correct please do share what needs to be done.

fronik · Thu Feb 29, 2024 7:27 pm

Faced the same problem

disconnected, SA Query timeout

On 5Ghz - Security - Connect Priority (0/1) It worked until firmware 7.14, but on 7.14 the network on the laptop began to fall off constantly. Connected \ Disconnected...

back to 7.13.4 (and definitely System\RouterBOARD\Upgrade firmware to 7.13.4) - good work for me

Neolo · Sat Mar 02, 2024 2:18 am

Faced the same problem
Code: Select all
disconnected, SA Query timeout
On 5Ghz - Security - Connect Priority (0/1) It worked until firmware 7.14, but on 7.14 the network on the laptop began to fall off constantly. Connected \ Disconnected...

back to 7.13.4 (and definitely System\RouterBOARD\Upgrade firmware to 7.13.4) - good work for me

Priority does not do anything, 7.14. Log is flooded with SA Query timeouts. Clients have terrible experience using wifi. What is going on??

Kanzler · Sat Mar 02, 2024 7:56 am

@Neolo,
Could you please show your configuration?

fronik · Sat Mar 02, 2024 4:54 pm

RouterOS and firmware ver <= 7.13.4 - normal work
RouterOS and firmware ver = 7.14 - clients disconnected and logs: "... disconnected, SA Query timeout ..."
My config:

/interface wifi configuration

add channel.band=2ghz-ax .frequency=2412 .skip-dfs-channels=10min-cac .width=20mhz country=Russia datapath.bridge=bridge disabled=no mode=ap name=2Ghz security.authentication-types=wpa2-psk,wpa3-psk .connect-priority=0/1 .passphrase=WiFiPass124 .wps=disable ssid=WiFiName123

add channel.band=5ghz-ax .frequency=5640-5725 .skip-dfs-channels=10min-cac .width=20/40/80mhz country=Russia datapath.bridge=bridge disabled=no mode=ap name=5Ghz security.authentication-types=wpa2-psk,wpa3-psk .connect-priority=0/1 .passphrase=WiFiPass124 .wps=disable ssid=WiFiName123-5GHz

/interface wifi cap
set caps-man-addresses=127.0.0.1 enabled=yes

/interface wifi capsman
set enabled=yes package-path="" require-peer-certificate=no upgrade-policy=none

/interface wifi provisioning
add action=create-dynamic-enabled disabled=no master-configuration=2Ghz supported-bands=2ghz-ax
add action=create-dynamic-enabled disabled=no master-configuration=5Ghz supported-bands=5ghz-ax

My clients: phones, tv, ps5, smarthome devices notebooks

MaxwellsEq · Sun Mar 03, 2024 1:02 am

I didn't see any mention of disabling Frame Protection. Did this not have any effect?

Neolo · Sun Mar 03, 2024 4:37 am

@Neolo,
Could you please show your configuration?

Which configuration are you asking about?
Everything is default except for it's an open network with OWE enabled.

Neolo · Sun Mar 03, 2024 4:38 am

I didn't see any mention of disabling Frame Protection. Did this not have any effect?

The only effect it makes is rendering WPA3 and OWE inoperable. And I don't want that.

Neolo · Sun Mar 03, 2024 4:42 am

RouterOS and firmware ver <= 7.13.4 - normal work

No it wasn't. I just upgraded from 7.13.4 to 7.14, both have the same problem. Trust me, I have a public place to test with 200 people connecting, not just own laptop and a phone.

Kanzler · Sun Mar 03, 2024 7:51 am

@Neolo
Very strange, I don't experience such an issue myself. Have you tried enabling FT? Maybe that will help?

MaxwellsEq · Sun Mar 03, 2024 9:53 am

I didn't see any mention of disabling Frame Protection. Did this not have any effect?
The only effect it makes is rendering WPA3 and OWE inoperable. And I don't want that.

Lots of non-compute devices (TVs, cameras, doorbells etc.) which don't support Frame Protection also don't seem to properly ignore its presence. If you Google SA Query Timeout, you will find this also an issue with non-Mikrotik Wireless setups. We seem to have two choices, only have very modern non-compute devices (fully WPA3 compliant) or run a Wireless radio setup which has no WPA3 elements including Frame Protection (with the small security risk this implies).

ToTheFull · Sun Mar 03, 2024 10:59 am

SNIP: Trust me, I have a public place to test with 200 people connecting, not just own laptop and a phone.

From my point of view that would look painfull on the eyes.
I have tried the "Connect Priority 0/1" trick and although it seems to help (not cure) it causes unexplained speed drops on both my AX devices.

Neolo · Sun Mar 03, 2024 10:34 pm

SNIP: Trust me, I have a public place to test with 200 people connecting, not just own laptop and a phone.
From my point of view that would look painfull on the eyes.
I have tried the "Connect Priority 0/1" trick and although it seems to help (not cure) it causes unexplained speed drops on both my AX devices.

I have that priority in place, it makes zero effect, timeouts still written in log.

Neolo · Sun Mar 03, 2024 10:35 pm

@Neolo
Very strange, I don't experience such an issue myself. Have you tried enabling FT? Maybe that will help?

What's FT?

Neolo · Sun Mar 03, 2024 10:38 pm

The only effect it makes is rendering WPA3 and OWE inoperable. And I don't want that.
Lots of non-compute devices (TVs, cameras, doorbells etc.) which don't support Frame Protection also don't seem to properly ignore its presence. If you Google SA Query Timeout, you will find this also an issue with non-Mikrotik Wireless setups. We seem to have two choices, only have very modern non-compute devices (fully WPA3 compliant) or run a Wireless radio setup which has no WPA3 elements including Frame Protection (with the small security risk this implies).

Nope, in the environment I have there is no TVs or doorbells, but phones and tablets.
Mikrotik should fix the firmware to accommodate all models properly, it's all it is.

Kanzler · Sun Mar 03, 2024 10:44 pm

set ft=yes and ft-over-ds=yes in security profile to enable 802.11r fast BSS transitions (roaming)

Mon Mar 04, 2024 12:33 am

What's FT?

Fast Transitions, a recently added feature. Disabled by default. “FT” is the tab name in WinBox.

Neolo · Tue Mar 05, 2024 9:15 pm

What's FT?

Fast Transitions, a recently added feature. Disabled by default. “FT” is the tab name in WinBox.

I have enabled it in my security template, but it doesn't do anything about SA Query timeouts alone.
However, when I have connected all APs via Capsman and enabled FT and FT over DS, that seems stopped SA Query Timeout errors.

robmaltsystems · Sun Apr 07, 2024 11:32 pm

solution for me:

/interface/wifiwave2/configuration> set [find] security.connect-priority=0/1

How do you query this setting? /interface/wifi/configuration/print doesn't show anything. It doesn't appear in /export either.

ToTheFull · Sun Apr 07, 2024 11:35 pm

I think they added it to this, if thats what you mean?

interface/wifi/monitor 0,1,2,3
                 state: running        running   running        running
               channel: 5500/ax/Ceee   2412/ax   5180/ax/Ceee   2462/ax
      registered-peers: 3              0         1              2
      authorized-peers: 3              0         1              2
              tx-power: 22             14        18             15
    channel-priorities: 0:5500/ax/Ceee 0:2412/ax 0:5180/ax/Ceee 0:2462/ax

Sun Apr 07, 2024 11:46 pm

try this security settings for compatibility

security.authentication-types=wpa2-psk .disable-pmkid=yes .encryption=ccmp .group-encryption=ccmp .group-key-update=1d .passphrase=xxxxxxxxxxxx .wps=disable

PD: i dont have any ax device for testing, this config i use it on hap-ac2 and audience, with routeros 7.13.5 and 7.14.2 working ok

robmaltsystems · Mon Apr 08, 2024 12:07 am

Thanks, will do but another time - it's late in UK and I've spent more hours than I really wanted to on this.

infabo · Mon Apr 08, 2024 12:22 am

try this security settings for compatibility
Code: Select all
security.authentication-types=wpa2-psk .disable-pmkid=yes .encryption=ccmp .group-encryption=ccmp .group-key-update=1d .passphrase=xxxxxxxxxxxx .wps=disable
PD: i dont have any ax device for testing, this config i use it on hap-ac2 and audience, with routeros 7.13.5 and 7.14.2 working ok

I'll go through docs:

.encryption=ccmp .group-encryption=ccmp .group-key-update=1d

That's already the defaults.

disable-pmkid=yes

If unsure this rather lowers compatibility.

wps=disable

Sure, good idea. But I think this not increase/decrease compatibility.

robmaltsystems · Mon Apr 08, 2024 3:45 pm

I'm going to do some more reading up on this before I start making any changes.

For the record, the device I'm having trouble with is an Lenovo V15 G2-ALC laptop, Windows 10, Realtek 882CE 802.11ac wireless chip. Using WPA2/3 authentication with defaults for everything else. Not tried the FT switches yet or any other tweaks.

Connects fine with no SA Query timeout errors in the log when sat on the coffee table about 1.5m away. Move it onto the bench about 3m away and unable to connect to 5GHz with SA Query Timeout in log. There is a partial 20m stone wall in the way and often me

When 1.5m from the hAP ax2, the router reports signal strength -54. The laptop reports a signal strength of -37. That -54 is "interesting", i.e. it being so low - suggests poor signal from the laptop? Connected to timeout errors? Never had any problem with old Virgin Media router.

I bought a cheap Wi-Fi 6 USB adapter for testing purposes. Signal strengths are -44 at router and -47 on laptop. When using this, it also works fine on the bench.

The SA query time errors occur both with WPA2 and WPA3. I thought it was a WPA3 "thing" but clearly not hence the reason for wanting to read up more.

robmaltsystems · Mon Apr 08, 2024 4:39 pm

I left the laptop on the coffee table, connected to 5GHz using the Wi-Fi 6 USB network adapter and came back about an hour later and it too had got SA Query timeout errors and had fallen back to 2.4GHz:

Something isn't right here. This is sat 1.5m from the router with very little else going on. I've restarted the adapter and it's reconnected at 5GHz...

MikrotikUser100 · Tue Apr 30, 2024 3:09 pm

Hello,

We are having hard times "enjoying" our mikrotik hardware.
Despite numerous software upgrades, we are still experiencing "SA Query Timeout" on several devices in our network.
I really don't understand, this problem has been reported like a year ago, and still Mikrotik did NOTHING to help their customers. Don't you think it's kinda wrong?
We spent 500 EUR in hardware. Obviously it's my last mikrotik, but since I cannot return it anymore, I need to fix the problem.

The same client works perfectly on another wifi from another vendor. So the problem is purely in mikrotik and their software/hardware (and mine is hAP ax^3 - which is pretty expensive and at least SOHO level, not a cheap home device)

Please PROVIDE SOLUTION ASAP. I don't understand what did I pay for.

akakua · Tue Apr 30, 2024 6:37 pm

has anyone tried to set "disabled" for management protection?

robmaltsystems · Tue Apr 30, 2024 6:43 pm

I really don't understand, this problem has been reported like a year ago, and still Mikrotik did NOTHING to help their customers. Don't you think it's kinda wrong?

I tend to agree. The Lenovo laptop I mentioned above really struggles to maintain a 5G connection and it's in the same room. I'm keeping totally away from AX range in the commercial space. This is just my home/office setup.

I wonder if Mikrotik is spread too thin on the development team? I must admit the range of devices available does seem a lot. I wonder if the development team keep going to the hardware guys "STOP!!! We need to get the existing kit working first"

robmaltsystems · Tue Apr 30, 2024 6:44 pm

has anyone tried to set "disabled" for management protection?

No but I will have a go. Doesn't that reduce security?

infabo · Tue Apr 30, 2024 6:51 pm

@MikrotikUser100
Besides the log message on your mikrotik device (SAQuery timeout...): how do you experience the problem on your client device?

MikrotikUser100 · Wed May 01, 2024 2:00 pm

@MikrotikUser100
Besides the log message on your mikrotik device (SAQuery timeout...): how do you experience the problem on your client device?

It's unusable, as we use it remotly.
It's not just a log message, it's a total disconnection from the network and hence complete instability and inability to use the device.

I have tried to disable WPA3 leaving only WPA2 on my wifi interfaces with no luck, didn't help at all. And what makes it worse, is when the laptop is close to the mikrotik (like 1-2 meters) it works.

ivicask · Wed May 01, 2024 2:31 pm

@MikrotikUser100
Besides the log message on your mikrotik device (SAQuery timeout...): how do you experience the problem on your client device?
It's unusable, as we use it remotly.
It's not just a log message, it's a total disconnection from the network and hence complete instability and inability to use the device.

I have tried to disable WPA3 leaving only WPA2 on my wifi interfaces with no luck, didn't help at all. And what makes it worse, is when the laptop is close to the mikrotik (like 1-2 meters) it works.

This fixed my query errors, try set it exactly like this.

akakua · Wed May 01, 2024 2:41 pm

No but I will have a go. Doesn't that reduce security?

sa query is part of protected management frames (802.11w), so you won't get any timeouts, if it disabled:)

robmaltsystems · Thu May 02, 2024 5:06 pm

Okay, got a few minutes spare to have a look at this. Laptop is back in the location where it gets SQ query timeouts. About to disable management protection.

Got a warning but assume that's okay. Have disabled WPS as well but assume that's unconnected.

Later... hmm maybe I'll turn off WPA3 as well as I don't seem to be able to connect at 5GHz. Keeps falling back to 2.4GHz. Maybe that warning means that 5Ghz won't work?

infabo · Thu May 02, 2024 5:33 pm

Management protection is required for WPA3. So according to the red message I assume you have configured wpa2-psk/wpa3-psk mode (or even "better": wpa3-psk alone). In a "mixed" mode you need to at least set management protection to "allowed". As WPA3 requires it. And your laptop now maybe wants to connect using WPA3 and fails terribly.

robmaltsystems · Thu May 02, 2024 6:52 pm

Okay, have turned WPA3 off and switched back to just WPA2. Devices now connected at 5G except the laptop is still preferring to fall back to 2.4GHz. I suspect we may be barking up the wrong tree here and the problem with this specific Lenovo laptop is it's transmit power. This is what the laptop reports from inSSIDer:

However, this is a log entry from the hAP ax2:

00:45:E2:81:E4:61@private-5g connected, signal strength -67

So the hAP ax2 is reporting a signal from the laptop of -67 which is borderline poor.

So maybe the SA Query Timeout log entries are because the transmit power is relatively poor. I'll split the SSID into 2 and 5GHz so I can force it to try and connect to 5GHz.

Later... when SSID is different between 2.4GHz and 5GHz, laptop will connect to 5GHz quite happily and reports connection speed of 390Mbps both directions. hAP ax2 reports a signal of -65. I'll turn WPA3 back on and reset management protection.

robmaltsystems · Thu May 02, 2024 7:07 pm

A question - in terms of deciding whether to connect at 2.4GHz or 5GHz, is it the client (Windows/laptop) that decides? Or does the access point get involved?

erlinden · Fri May 03, 2024 12:08 am

It is up to the client. I tend to lower Tx Power of the 2.4GHz radio to have clients prefer 5GHz over 2.4GHz.

Turn on wireless debug logging to get more insights of the cause.

ulysses · Wed May 15, 2024 11:07 pm

I also have this issue, also with a Lenovo laptop. Other devices, including Apple and Android phones, and a MacBook, work well.
I have twp capsman managed Cap AX with WPA2+3 and FT enabled

infabo · Thu May 16, 2024 2:18 am

You can deactivate FT. It's also not activated by default. Other manufacturers prioritize maximum compatibility, so most features that could cause issues with clients are inactive. You can only activate features like FT after clicking "yes, please, advanced settings, no auto mode, and yes, I understand it can cause problems, thanks for the heads up" five times. With Unifi, you only get WPA2 and maybe 802.11v (if at all) in "Auto" mode. Just because ROS doesn't bombard you with warnings about potential problems with WPA3 or FT doesn't mean ROS is Satan incarnate for not informing you about the consequences. And if a red warning does pop up, people freak out, open forum topics, and want to know how to get rid of those ugly red messages. They're not interested in solving the problem; they just want to hide the message because it's ugly.

robmaltsystems · Mon Aug 26, 2024 6:35 pm

Resurrecting this post so not the hijack the other post. I've just done some very unscientific testing (but arguably valid) of a hAP ac lite and my new hAP ax2. Top line - the hAP ax2 receives a signal that's 10dB worse than the hAP ac lite. During the test, only one device's Wi-Fi was enabled at once.

For the hAP ax2, it's receiving a signal strength of -70dB from the laptop - this is borderline and most likely results in the SA Query timeout situation. The hAP ac lite receives a signal of ~60dB. The laptop receives a signal of -50dB for both devices.

-10dB difference is IMO a big enough difference to raise eyebrows. The hAP ax2 is Wi-Fi 6 enabled with WPA2/WPA3 PSK encryption whereas the hAP ac lite is Wi-Fi 5 enabled with WPA/WPA2 PSK. I'll do some mores tests by changing the hAP ax2 to Wi-Fi 5 and same WPA.

jaclaz · Mon Aug 26, 2024 6:52 pm

I wonder why the Ax2 is always represented as standing ...

AFAIK it needs to be standing because of better heat dissipation, but it is possible that the internal antennas are designed to work with the device standing and having it flat on the table reduces their efficiency (or you have a lot of signal at an upper floor and in the basement

) .

You should try with the Ax2 in the recommended orientation, it may make a difference (or maybe not?).

In theory the ac lite has lower gain antennas (1.5/2 db) whilst the Ax2 has higher gain antennas (4/4.5 db) so reception should be better on the Ax2, the opposite of what you measured.

infabo · Mon Aug 26, 2024 7:07 pm

Legacy wireless driver does not support 802.11w. So you won't spot a SA query timeout in HAP AC lite logs.

robmaltsystems · Mon Aug 26, 2024 7:12 pm

Same thought crossed my mind. I put it horizontal because that's the natural orientation of the hAP ac lite. But I've also just tried vertical - no difference. Whilst vertical, tried rotating 90 degrees. No difference. Flat on it's back. No difference. Switch to AC with WPA/WPA2. No difference. Signal strength stubbornly sticks around -70dB whereas the hAP ac lite is around -60dB. The only way to get 5GHz to work is to be sat in clear sight about 2m away from the hAP ax2.

If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck. Having spent hours fiddling with this, my gut instinct is that the RX antenna/signal in the hAP ax2 is weaker than the previous hAP ac range and therefore this leads SA Query timeouts and fall-back to 2.4GHz band.

PS. Before I tried the tests today, it's been vertical since I installed it.

robmaltsystems · Mon Aug 26, 2024 7:12 pm

In theory the ac lite has lower gain antennas (1.5/2 db) whilst the Ax2 has higher gain antennas (4/4.5 db) so reception should be better on the Ax2, the opposite of what you measured.

Quite... that are many, many posts around AX signal strength on here that the gun isn't just smoking, it's firing.

robmaltsystems · Mon Aug 26, 2024 7:15 pm

Legacy wireless driver does not support 802.11w. So you won't spot a SA query timeout in HAP AC lite logs.

Understood but I was mainly looking the receive signal strength of the hAP devices for comparison.

robmaltsystems · Mon Aug 26, 2024 7:22 pm

Another observation. Normally, the SSID for 2.4GHz and 5GHz are identical. However, for this test, I added "5G" on the end of the SSID so I could force it onto one band or another. When the SSIDs are different, the SA Query timeout errors never occur. Even though the RX signal is poor, it's still managing pretty decent speeds:

I'm going to bet that when I remove the "5G" tag, I'll start getting the timeouts and it'll fall back to 2.4GHz. IMO a Tx Rate of ~800Mbps and Rx rate of ~500Mbps doesn't merit a fall back to 2.4GHz. I asked above whether the decision to fall back is triggered by the router, the client or both.

infabo · Mon Aug 26, 2024 7:25 pm

Easy bet. It is already known this is the root of the issue. That's why people commonly tinker around with connect-priority.

jaclaz · Mon Aug 26, 2024 7:32 pm

Another observation. Normally, the SSID for 2.4GHz and 5GHz are identical. However, for this test, I added "5G" on the end of the SSID so I could force it onto one band or another. When the SSIDs are different, the SA Query timeout errors never occur. Even though the RX signal is poor, it's still managing pretty decent speeds:

This is very interesting

, it may connect this SA Query Timeout to a "decision" to be made either on the Mikrotik or on the client about which frequency to use within a same SSID.
Obviously if the SSID's are different such a decision needs not to be taken, i.e.it is taken manually before when choosing one of the two SSID's.

robmaltsystems · Mon Aug 26, 2024 7:38 pm

Easy bet. It is already known this is the root of the issue. That's why people commonly tinker around with connect-priority.

Giving this a go! Disabled it on 5Ghz interface and switched back from WPA2/3 to WPA/WPA2.

erlinden · Mon Aug 26, 2024 7:43 pm

Giving this a go! Disabled it on 5Ghz interface and switched back from WPA2/3 to WPA/WPA2.

Why use WPA (when you can use open)?

jaclaz · Mon Aug 26, 2024 7:52 pm

Easy bet. It is already known this is the root of the issue. That's why people commonly tinker around with connect-priority.

I thought that was related to issues when roaming with two or more different AP's?
viewtopic.php?p=1093107#p1093107

infabo · Mon Aug 26, 2024 8:59 pm

Switching between bands on same AP is also called roaming AFAIK.

jaclaz · Mon Aug 26, 2024 11:34 pm

I see now, so in the referenced post the new and old AP are to be intended as same AP but new and old bands.

litvcom · Fri Aug 30, 2024 1:16 am

Similar behavior on my AX3, hopefully in RouterOS 7.16.x they will bring the work to the desired level.

Parking4754 · Thu Sep 05, 2024 11:45 am

Same problem here, setup as follows:
- 4009 as CAPsMAN
- CAP XL, ax2 and ax3 as AP’s
- Running 7.15.3

FT roaming works but clients regularly lose their connection to an AP and reconnect seconds later. Logs mention SA Query timeout. Only WPA2 and CCMP configured.

gigabyte091 · Thu Sep 05, 2024 2:43 pm

After disabling WPA3 I don't have wifi issues anymore, timeouts happens only when signal is weak.

robmaltsystems · Wed Sep 18, 2024 11:48 pm

I concur with the weak signal observation. Problem is that one doesn't feel the signal is weak when the SA Query timeout occurs.

ToTheFull · Thu Sep 19, 2024 12:26 am

Depends what you define as weak, the following cuulmination of events goes from conncted to my cAP ax upstairs roaming to my hAP ax2 Downstairs then going outside my house to another building with double layer brick walls which disconnects after a period and then re-joins. That would be a mobile phone in a pocket. if you call that not great I just can't agree. that would mean I just need an external AP?

19:36:46 wireless,info 9E:@cap-wifi1 roamed to 9E::DB@wifi2, signal strength -48
19:49:52 wireless,info 9E:@wifi2 disconnected, SA Query timeout, signal strength -71
19:49:57 wireless,info 9E:@wifi2 connected, signal strength -71

litvcom · Tue Sep 24, 2024 10:53 pm

I concur with the weak signal observation. Problem is that one doesn't feel the signal is weak when the SA Query timeout occurs.

This happens even a few meters away from the router, so it's definitely not due to a weak signal. I just upgraded to 7.16, but I don't see any fixes in the changelog, so I don't think anything has changed.

Coughy · Wed Sep 25, 2024 8:38 am

i have roaming working and no sa timeouts
and very little disconects
i have been playing with the config for minths now and i think i have it working pretty good
this is the best i can get it

Screenshot 2024-09-25 153727.png

Serge · Wed Sep 25, 2024 11:55 am

cAP ax
7.14.3 - free from this bug
7.15.x - BUG present
Whats about 7.16?

Sirafim · Thu Sep 26, 2024 12:15 pm

cAP ax
7.14.3 - free from this bug
7.15.x - BUG present
Whats about 7.16?

Nothing.
Until yesterday I had firmware 7.14.3 installed on AX3 - everything worked without a single problem.
Yesterday I installed 7.16 - again there were constant disconnections, SA and a new problem: AX3 unavailability for connection after disconnection.

AX3 is paired with hAP AX Lite. hAP AX Lite - no problems after upgrading to 7.16.

As a result: I returned firmware 7.14.3 on AX3

infabo · Thu Sep 26, 2024 1:38 pm

It is probably all because of this innocent changelog line in ROS 7.15 changelog:

*) wifi-qcom - updated driver;

Jeez, why Mikrotik not reverting this change and re-introduce updated drivers once they got the issues fixed? Instead they take into account people having issues by running latest version of ROS.

Coughy · Thu Sep 26, 2024 2:06 pm

running 7.16.rc4 , runing 7.16.rc4 firmware
no sa querys, time outs or really any of the sort like it used to yes i do get a couple disconects but noithing like what it use to be like
no real issues at moment , i did have the authentisicate loop bug but i have got that to dissapear
hapax3 , hapax2, capax x 3 all running 7.16.rc4 firmware
all roaming and working yes i do get a couple of disconects and stuff high signals but it is getting better
i have tweaked the config file a bit but seems to be working for me
i have started a complete new config as i found that a restored config made issues and bugs
so i update and make a completely new config for that base ros and i dont really have issues anymore learnt this over the last few months of fault finding and testing settings.
im happy to share my config and for some to try and see if it helps out as i have been useing bits and pieces from here to try and test out as well

cAP ax
7.14.3 - free from this bug
7.15.x - BUG present
Whats about 7.16?
Nothing.
Until yesterday I had firmware 7.14.3 installed on AX3 - everything worked without a single problem.
Yesterday I installed 7.16 - again there were constant disconnections, SA and a new problem: AX3 unavailability for connection after disconnection.

AX3 is paired with hAP AX Lite. hAP AX Lite - no problems after upgrading to 7.16.

As a result: I returned firmware 7.14.3 on AX3

neki · Thu Sep 26, 2024 3:20 pm

cAP ax
7.14.3 - free from this bug
7.15.x - BUG present
Whats about 7.16?
Nothing.
Until yesterday I had firmware 7.14.3 installed on AX3 - everything worked without a single problem.
Yesterday I installed 7.16 - again there were constant disconnections, SA and a new problem: AX3 unavailability for connection after disconnection.

AX3 is paired with hAP AX Lite. hAP AX Lite - no problems after upgrading to 7.16.

As a result: I returned firmware 7.14.3 on AX3

Can you share your config please? Same applies to you @infabo

Sirafim · Thu Sep 26, 2024 4:51 pm

Nothing.
Until yesterday I had firmware 7.14.3 installed on AX3 - everything worked without a single problem.
Yesterday I installed 7.16 - again there were constant disconnections, SA and a new problem: AX3 unavailability for connection after disconnection.

AX3 is paired with hAP AX Lite. hAP AX Lite - no problems after upgrading to 7.16.

As a result: I returned firmware 7.14.3 on AX3
Can you share your config please? Same applies to you @infabo

No problem.
This is one variant that works fine on 7.14.3, but doesn't work on 7.15+

/interface wifi channel
add band=5ghz-ax disabled=no frequency=5220,5240 name=channel.ax width=20/40/80mhz
add band=5ghz-ac disabled=no frequency=5220,5240 name=channel.ac width=20/40/80mhz
/interface wifi security
add authentication-types=wpa2-psk connect-priority=0/1 disable-pmkid=yes disabled=no ft=no ft-over-ds=no group-encryption=ccmp \
    group-key-update=12h management-protection=disabled name=security.b1 wps=disable
/interface wifi
set [ find default-name=wifi1 ] channel.frequency=5220 comment="WIFI AX" configuration=cfg.ax configuration.mode=ap disabled=no
add channel.frequency=5220 comment="WIFI AC" configuration=cfg.ac configuration.mode=ap disabled=no mac-address=XX:XX \
    master-interface=wifi1 name=wifi3 security=security.b1
/interface wifi configuration
add channel=channel.ax country=Ukraine datapath=datapath.b1 disabled=no mode=ap multicast-enhance=enabled name=cfg.ax security=\
    security.b1 ssid=AX
add channel=channel.ac country=Ukraine datapath=datapath.b1 disabled=no mode=ap multicast-enhance=enabled name=cfg.ac security=\
    security.b1 ssid=AC
/interface wifi datapath
add bridge=bridge.b1 disabled=no name=datapath.b1

neki · Thu Sep 26, 2024 9:15 pm

This is weird, as it was already mentioned here, SA Query is part of 802.11w (protected management frames), so this shouldn't be even possible with management-protection=disabled.

I also had this issue, but it was caused by misconfiguration on my side. Anyway, I also encountered another bug when my security settings weren't properly applied. Counldn't this be the issue?

ToTheFull · Thu Sep 26, 2024 9:19 pm

Flapping problem has returned with 7.16

Sirafim · Sat Sep 28, 2024 1:09 pm

Mediabox TOX1 on RoS 7.15+ firmware was losing connection with AX3 on 5GHz every 2-5 minutes. After returning to firmware 7.14.3, everything started working stably again.
At the same time connection to hAP AX lite on 2GHz via N protocol works stably on TOX1 media box.
About TOX1 media box https://techxreviews.com/tox1-tv-box-review/

POCO F4 smartphone refused to connect to the AP after losing connection with AX3 on RoS 7.15+ firmware. No problem occurred on firmware 7.14.3 with the same configuration.

The same happens on ASUS laptop on AX, on HP laptop on AC.
Also checked on TP-Link DWA-185 (Linux,Windows) same problems on firmware 7.15+.

zubrev · Sat Sep 28, 2024 2:04 pm

Use only wpa2!
management protection - disable!

the problem seems to have disappeared (No SA query timeout messages in log, roaming messages between AP appeared)!

neki · Sat Sep 28, 2024 11:30 pm

7.17beta2

*) wifi - re-word the "SA Query timeout" log message to "not responding";

flynno · Sat Sep 28, 2024 11:51 pm

7.17beta2

*) wifi - re-word the "SA Query timeout" log message to "not responding";

Fixing typo's

MrRobotdev · Sun Sep 29, 2024 8:35 am

I had the same problem with hap ax2 only with my win10 laptops. No problem with mobiles.

I was using WPA2 and WPA3.

When i select only WPA3, problem disappeared.

Probable works with only WPA2.

Not an expert to know the details why this is happening but right now i have zero problems.

Sirafim · Sun Sep 29, 2024 11:11 am

7.17beta2

Fixing typo's

The problem will remain, but it will be called something else?

infabo · Sun Sep 29, 2024 12:03 pm

According to Mikrotik it is not a problem. It is just a notice. "wireless,info" gives the severity already

flynno · Sun Sep 29, 2024 1:48 pm

This has been going on since installed, capsmanv2 with 2x cAPGi-5HaxD2HaxD and 1x C52iG-5HaxD2HaxD
All running 7.15.3

10 wireless devices have no issue and do not disconnect and about 4-5 devices keep disconnecting and reconnecting,
Basic settings applied below

/interface wifi channel
add band=2ghz-ax comment="1, 6, 11 = 2.4G" disabled=no frequency=2412 name=\
channel1_2,4G skip-dfs-channels=all width=20/40mhz-Ce
add band=2ghz-ax disabled=no frequency=2437 name=channel6_2.4G \
skip-dfs-channels=all width=20/40mhz-eC
add band=2ghz-ax disabled=no frequency=2462 name=channel11_2.4G \
skip-dfs-channels=all width=20/40mhz-eC
add band=5ghz-ax comment="indoor channels 36, 40, 44, 48 = 5G" disabled=no \
frequency=5180 name=channel36_5G skip-dfs-channels=all width=20/40/80mhz
add band=5ghz-ax disabled=no frequency=5200 name=channel40_5G \
skip-dfs-channels=all width=20/40/80mhz
add band=5ghz-ax disabled=no frequency=5220 name=channel44_5G \
skip-dfs-channels=all width=20/40/80mhz
add band=5ghz-ax disabled=no frequency=5240 name=channel48_5G \
skip-dfs-channels=all width=20/40/80mhz

/interface wifi security
add authentication-types=wpa2-psk disabled=no ft=yes ft-over-ds=yes \
group-encryption=ccmp group-key-update=40m name=local_sec
add authentication-types=wpa2-psk disabled=no ft=yes ft-over-ds=yes \
group-encryption=ccmp group-key-update=40m name=mgmt_sec
add authentication-types=wpa2-psk disabled=no ft=yes ft-over-ds=yes \
group-encryption=ccmp group-key-update=40m name=secondary_sec

pdrsks · Tue Oct 01, 2024 5:44 pm

Hi guys, I had this problem with a cap ax on 7.16 and an intel ax200 wifi card, with Windows 10 (not 11) on the last wifi drivers. After trying different things, including using only WPA2, disabling fast roaming, downgrading to 7.14.3 (this one worked), the solution was to modify an advanced parameter on the driver settings.

In device manager, go to network adapters, properties, advanced properties and in MIMO power save mode select No SMPS. With this, all my disconnections dissapeared, I hope this also works for someone else.

MrRobotdev · Wed Oct 02, 2024 6:50 am

Unfortunately the problem reappeared after 2 days on WPA3 only. So i really dont know what the solution would be...

Thats why nobody recommends Mikrotik for WiFi - AP... this is a major problem, not be able to connect steady one laptop

Wed Oct 02, 2024 8:53 am

I have 10 AP roaming setup here, all devices but one are working just fine, the only one with issue is with intel ax200/201 wifi card and windows 11, it randomly decides to disconnect form the closest/best AP (signal level -50) and roam to worst possible AP (signal level -86/-90) for absolutely no reason, while stacionary on the table....

all indications are that it is client decision to disconnect and move.

I have tried latest driver, changed few settings (fast roaming, wpa3 disabled etc). Internet shows that there are lots of similar problems with that intel card on different vendors also...

infabo · Wed Oct 02, 2024 9:17 am

Interesting.

"Some legacy APs may have compatibility issue with supporting the SMPS mode and may cause various link quality problems such as low throughput. Change this setting to No SMPS may help to work around the issue"
https://www.intel.com/content/www/us/en ... he%20issue

And already one report on the forum on this: viewtopic.php?t=207037

woland · Wed Oct 02, 2024 10:44 am

In device manager, go to network adapters, properties, advanced properties and in MIMO power save mode select No SMPS. With this, all my disconnections dissapeared, I hope this also works for someone else.

Nice input, thanks I´ll try disabling SMPS.
The link Infabo provided clearly shows , that this should only happen on "legacy APs" .
I only have trouble with this on my CAPax, which I did not consider legacy up until now. It only happens with one laptop I use. I never have any problems on other APs with this device.
I think MT Wifi will be considered legacy for me as well soon, but I stil wish MT wakes up and puts more efforts to resolve this issue!

infabo · Wed Oct 02, 2024 11:12 am

Indeed. MIMO SMPS is as old as 802.11n. See https://dot11ap.wordpress.com/spatial-m ... save-smps/
But maybe some kind of bug in either Intel drivers or on Mikrotik AP side. Given that disconnecting clients issue is really related to Intel SMPS setting at all.

dmfr · Wed Oct 02, 2024 5:36 pm

From my side, on 7.17beta2, using
- security.authentication-types=wpa2-eap
- security.management-protection=disabled
So far, the issue does not occur anymore, on any wifi adapter (low-end RTL8821 or high-end Intel AX201)

litvcom · Wed Oct 02, 2024 9:35 pm

In device manager, go to network adapters, properties, advanced properties and in MIMO power save mode select No SMPS. With this, all my disconnections dissapeared, I hope this also works for someone else.

I tried it on RouterOS 7.16, but it didn't help, so it looks like I'll have to go back to RouterOS 7.14.3 and forget about the update.

inray · Thu Oct 03, 2024 12:21 am

I have tried latest driver, changed few settings (fast roaming, wpa3 disabled etc). Internet shows that there are lots of similar problems with that intel card on different vendors also...

This is unfortunately not a windows driver problem as the same issues exist with Linux clients.
It is a known interoperability problem of RouterOS with the specific Intel WiFi chipsets (AX2xx) used in the vast majority of laptops and motherboards.

Only functional workaround known so far is to disable WPA3 and management protection on ROS side.
Certainly not the ideal solution but the only one until Mikrotik developers find and fix the issue.

MrRobotdev · Mon Oct 07, 2024 9:04 am

@normis

You asked for my support ticket regarding the SA query timeout and the inability to connect different business laptops to wifi since 7.15 version.

Some expert users have found the problem and MIkrotik still in 7.17 beta version has no fix.

Really? Take a Lenovo L13 laptop and setup a wifi with wpa3 configuration and you will understand what i mean.

BEFORE proceeding to feature development you all must fix the important problems like that. Users cannot connect to wifi - this should be a priority i think.

Please read the posts above regarding the problem.

woland · Mon Oct 07, 2024 3:00 pm

Agree with @MrRobotdev, but could you just post your WiFi Adapter type? Most Lenovos come in lots of different variants with possibly different WLAN chipsets.

My Lenovo YogaPro 9 can be added to the list. It has the latest drivers installed and has no issues with TPLink Omada, Unify, Cisco APs using WPA3 PSK or WPA3 Enterprise. There are no issues with CAPac APs running WPA2. But on my CAPax with 7.16: unusable.
WIFI Chipset:
Intel WiFi 6E AX211

infabo · Mon Oct 07, 2024 3:56 pm

I agree. Let's collect the affected client chipsets here. Once there is a larger list collected: Mikrotik can invest ~20$ for that wireless card that appear most frequent in that list. Put this card into some old notebook and start debugging happily. Hopefully resulting in a fix soon.

pdrsks · Mon Oct 07, 2024 8:12 pm

I thought that I solved the problem with the intel ax200 chipset with the no SPMS parameter but unfortunately I still had disconnects. I have switched to a Realtek based card for 22 euros, in particular based on the chipset 8852BE and all my problems are gone and the signal is a little better. For me, it was not worth spending so much time diagnosing the problem insted of buying a new card. I hope the problem can be fixed for intel cards.

woland · Mon Oct 07, 2024 8:23 pm

Well replacing the WLAN adapter in my company issued laptop is not the way I want to go. My Intel card is working perfectly well with every other AP I tried. Also some Lenovos simply refuse WLAN adapters which they don´t get shipped with (don´t ask me why, dumbness of Lenovos policies?).
Also I have one more suspect, but I could not fully confirm it yet: my sons Laptop has a Realtek 8822CE. He complained a lot last summer about the connectivity to the CAPax. So maybe this bug doesn´t only affect Intel cards.

dmfr · Tue Oct 08, 2024 1:54 am

my sons Laptop has a Realtek 8822CE...
So maybe this bug doesn´t only affect Intel cards.

It doesn't. Realtek's 88xx are affected as well.

Side note, these series have a history of problems with APs powered by (some) Mediatek chipsets. Ubiquiti Nano HDs were a total disaster with Realtek clients.
So I thought at first the same was happening with new Qualcomm firmware (ROS > 7.14.3)... until we experienced same issues with Intel AXs and discovered how global that problem is..

woland · Tue Oct 08, 2024 10:04 am

Thanks @dmfr! But to me it looks like not all RTL88xx are affected, as @pdrsks wrote, that his 8852BE works flawlessly.
Still good to know the issues are complicated at does not only affect MT.

MrRobotdev · Tue Oct 08, 2024 10:04 pm

Agree with @MrRobotdev, but could you just post your WiFi Adapter type? Most Lenovos come in lots of different variants with possibly different WLAN chipsets.

My Lenovo YogaPro 9 can be added to the list. It has the latest drivers installed and has no issues with TPLink Omada, Unify, Cisco APs using WPA3 PSK or WPA3 Enterprise. There are no issues with CAPac APs running WPA2. But on my CAPax with 7.16: unusable.
WIFI Chipset:
Intel WiFi 6E AX211

Same exactly WIFI adapter here, Intel Wifi 6E AX211 on a Lenovo L13

woland · Thu Oct 10, 2024 12:31 am

Thanks @MrRobotdev, so until now we have:
Intel WiFi 6E AX211
Realtek 8822CE

Those are affected, if WPA3 is used.
Any other chipsets?

inray · Thu Oct 10, 2024 12:03 pm

Thoroughly tested by me and affected when WPA3 is used
Intel WiFi 6E AX201
Intel WiFi 6E AX210
Intel® WiFi 7 BE200
and of course Intel WiFi 6E AX211

dmfr · Thu Oct 10, 2024 1:42 pm

Bad news, below is my last update to support ticket

--------------------------

After more testing in living conditions with :
- 7.17beta2 or 7.16 stable
- wpa2 only + management protection disabled
- additionally, band steering disabled
- various chipsets (Realtek 8821, Intel AX201, Google Pixel 4/6)

it seems that unfortunately the problem is deeper than management protection frames and/or wpa3.
Unexplained connectivity drops still happens under some conditions.

Example :
- 2 (or more) stations with busy, continuous traffic (ex UDP or websocket video streaming)
- other stations almost idle
- at some point, at the same time :
- - connectivity breaks on one of the active stations...
- -... and connectivity breaks as well on one (or more) random idle station(s)
- affected stations will eventually reconnect after several attempts
- no relevant messages in log, except disconnect / connect
Revert to 7.14.3, no more issues. Stress tests such as above always pass.

"SA Query timeout" might be one of the symptoms when mgmt protection enabled, but it is definitely not the root cause.
As of today any potential workaround mentionned does not entirely clear the problem, except revert to 7.14.3

ivicask · Thu Oct 10, 2024 1:59 pm

This is exactly my observation with same settings tried.
For example yesterday i tried to watch movie and my LG OLED and Samsung soundbar disconnected with connection lost 4 times in 2 hours while i try to watch a movie...

Most of the time router kicks all clients same time with query timeout (or connection lost on 7.17)

Zero problems on 7.14.3.

I think at this point Mikrotik should just revert new Qualcomm drivers they added in 7.15 until they figure whats wrong...

infabo · Thu Oct 10, 2024 2:59 pm

it is known to be issues since many months. not even reverted in 7.17beta2. so won't happen.

woland · Thu Oct 10, 2024 7:39 pm

Thanks for your inputs!
So we have issues with WPA3 with the new WIFI AX Drivers at least with the following chipsets:

Intel WiFi 6E AX201
Intel WiFi 6E AX210
Intel WiFi 6E AX211
Intel WiFi 7 BE200
Realtek 8822CE

Unfortunately these are very common chipsets!

I hope MT wakes up and gives us some hints? This must affect lots of users, MT looses lots of reputation here. @Normis ?

infabo · Thu Oct 10, 2024 7:55 pm

Intel ax200 also reported by some.

dmfr · Thu Oct 10, 2024 8:03 pm

So we have issues with WPA3 with the new WIFI AX Drivers at least with the following chipsets:

"SA query timeout" is a symptom, not the root cause.
The problem occurs as well with wpa2 + no mgmt protection.
WPA3 just makes is more obvious.

I am not sure chipset vendor / model really matters anyway.
Reviewing logs from controller I've seen "drops" from Iphone, Pixel, Intel AX, Realtek 88xx...

One thing, the drop have a tendancy to occur on APs with more than one active (significant traffic) station.
It never happens if there's only one station registered to the AP.

Sddaw · Thu Oct 10, 2024 10:10 pm

busy, continuous traffic (ex UDP or websocket video streaming)

dunno bout significant traffic but this! every second-third time i'm on a zoom call wifi drops! ax211 lap <-> hap ax3

robmaltsystems · Thu Oct 10, 2024 11:20 pm

I had the same problem with hap ax2 only with my win10 laptops. No problem with mobiles.

I was using WPA2 and WPA3.

When i select only WPA3, problem disappeared.

Probable works with only WPA2.

Not an expert to know the details why this is happening but right now i have zero problems.

Sounds like a very similar configuration to me. Same hAP ax2, only with Windows laptops.

woland · Fri Oct 11, 2024 10:39 am

Huhh, not easy to catch and we are probably talking about multiple bugs.
I never had issues with my previous laptop (gave that back, so Wifi chipset unknown) and my mobiles. Only my new laptop seems to be affected and my childs laptop. My previous laptop had Win10 my current one and also my childs laptop has Win11 installed.
I have WPA3 enabled.
Unfortunately I do only spend time around there where my CAPax is installed every 2-3Weeks, so I can´t test right now, but I´ll check tomorrow with WPA2/WPA3 and swithcing off/on management frame protection and then will roll back to 7.14.3, probably will try 7.17betaX as well.
I also have a few Linux laptops, I´ll check them too!

So for me those chips under Win11 are affected with 7.15.x-7.16 on my CAPax.
Intel WiFi 6E AX211
Realtek 8822CE

Thanks everyone for the infos!

MrRobotdev · Sun Oct 13, 2024 7:29 am

If 7.14.3 works, why Mikrotik just revert the relevant drivers to that state until they figure out what is going on?

STOP feature development and start bug fix guys... simple as that...

What is the meaning of moving forward to 7.17 or 7.18 if we cannot connect with our business laptops to wifi?

HP also affected

netmn · Tue Oct 15, 2024 2:21 pm

The same issue on AX3, so using 7.14.3 version with Factory Firmware 7.15.2.

Very sad issue.

luki · Wed Oct 16, 2024 10:20 am

7.17beta2
Unfortunately, the problem still exists, only the name has changed
Intel WiFi 6E AX211

alibloke · Wed Oct 16, 2024 11:23 am

*) wifi - re-word the "SA Query timeout" log message to "not responding";

We might have to rename this thread

inray · Wed Oct 16, 2024 4:00 pm

Rewording a long-standing issue instead of fixing it.

Well done, Mikrotik!

Wed Oct 16, 2024 4:03 pm

Code: Select all
*) wifi - re-word the "SA Query timeout" log message to "not responding";
We might have to rename this thread

Done.

infabo · Wed Oct 16, 2024 4:05 pm

Nit picking: "f.k.a" instead of "a.k.a"

"not responding" - f.k.a. SA Query timeout

Wed Oct 16, 2024 4:06 pm

True ...

dmfr · Wed Oct 16, 2024 10:07 pm

Everyone can understand fixing such an issue is no trivial matter.

Especially as it involves a driver from third party (Qualcomm), maybe a binary blob driver,
and it sure takes some special conditions to reproduce,
- ie continuous traffic on several stations (video call is good example),
- plus chipset vendor/model might matter, or maybe not so much, anyway..

However if a few guys at Mikrotik are listening, maybe just a little bit, to their users, they cannot deny the fact that :

** there is something wrong with qcom driver >= 7.15beta **

.and it's not limited to WPA3 / mgmt protection
..and it's not limited to a few low-end chipsets
...and it's not limited to some niche usage

I pers. think (and i'm probably not alone on this) that time for agile testing/debugging based on "stable" releases is largely over now.

As a wifi equipment vendor, mikrotik should be able to build real-hard-life test beds in their own labs, instead on endlessly asking for pcaps and supouts.

In the meantime, for the sake of Mikrotik's reputation,

** please revert, one way or another, to a clean qcom driver (<= 7.14.3 like) ***

Message in a bottle ? Anyone reading this ?
hope so, because :

- users that -are- aware of the problem (a few percent) are legitimately excepting a fix from the vendor, so far the fix (and the vendor) are nowhere to be found, and this is bad

- users (the rest) that are just rolling equipment on production are experiencing everyday bad performance (disconnects, drops), and will legitimely blame mikrotik at the end, not without a lesson learned for their future investments. And this is even worse.

woland · Thu Oct 17, 2024 4:55 pm

Probably no use complaining, but it feels refreshing. After some horrible test results with 7.16.1, 7.17b2 last weekend. I was rolling back my CAPax to 7.14.3. Turns out that even then the results with the laptop of my son (RTL chipset) are still horrible. There are random interruptions, lot of jitter.

I got fed up and purchased TPLink Omada, I´ll replace my CAPax this weekend. I need stable WIFI and I can use my time better for more important things than to try to figure out the newest MT bugs.

Still got one installation based on CAPac/WAPac, but that´s my last one. Runs ROS7, but the old drivers. Lack of VLAN tagging on the driver side for the new drivers is a big no no.

The purchase of my CAPax was just money thrown out the window.

infabo · Thu Oct 17, 2024 5:50 pm

Good point. And given my findings today, it's time to evaluate the competition again. The reason: local flent tests (local test server) are suddenly performing terribly. The whole WiFi tilts and/or pings go beyond 1000ms during the test. Interestingly, the same flent test ran ~half year ago on version 7.13 flawlessly (including perfect prioritization). I have no idea where the problem is coming from now. The UniFi U6+ didn't convince me back then. TP-Link or Zyxel - though I’m leaning more towards Zyxel. I'm curious to see what these manufacturers can offer out of the box.

dmfr · Thu Oct 17, 2024 7:39 pm

I'm curious to see what these manufacturers can offer out of the box.

Some good & bad probably.
Talking about Unifi, it's a Java controller, some devices have been brillant (AC long range), some devices a real disaster (Nano HD, drops & disconnects never solved)

The general chit-chat about promising competitors might feel good in a frustrating situation, but the focus here is to see the infamous problem fixed the quickest.

However, if it can help Mikrotik to realize how fast the house is burning...

WeWiNet · Thu Oct 17, 2024 7:50 pm

Good point. And given my findings today, it's time to evaluate the competition again. The reason: local flent tests (local test server) are suddenly performing terribly. The whole WiFi tilts and/or pings go beyond 1000ms during the test. Interestingly, the same flent test ran ~half year ago on version 7.13 flawlessly (including perfect prioritization). I have no idea where the problem is coming from now. The UniFi U6+ didn't convince me back then. TP-Link or Zyxel - though I’m leaning more towards Zyxel. I'm curious to see what these manufacturers can offer out of the box.

My own personal guessing is that additionally the steering (and other stuff) Mikrotik is doing, creates lot of issues. Since the recent ax drivers I see my devices hang, not respond on Wifi
while on 2.4G they should have at least decent coverage. Pages do not load, speed test failures etc. Something I never had before.
But as Mikrotik does not want to give you any meaningful logs for steering events (I asked for that long time ago) nor any other advanced Wifi mechanism, and as nothing can be tuned
its a failing black box.
I am in my last attempt to solve my Mikrotik Wifi network before going to some other brand.

woland · Thu Oct 17, 2024 10:41 pm

Talking about Unifi, it's a Java controller, some devices have been brillant (AC long range), some devices a real disaster (Nano HD, drops & disconnects never solved)

I got no real experience with Unify, but my current Omada setup has replaced a previous CAPac & Capsman based installation here (this is another flat, not the one where I was trying to use the CAPax). I had the CAPacs for a year. Before that I had different Openwrt based setups. I have spent so much more time with Capsman and the CAPac APs, than with all the other setups together for the last 15 years. I have high levels of interference here, a scan shows around 100 SSIDs. With CAPacs that was a problem, required continous optimizations. With my current setup which is installed a year ago, I spent maybe 3-4Hours configuring in total. It just works, has lots of nice features, I have no jitter, no disruptions, great performance, VLANs are easy to configure.

The general chit-chat about promising competitors might feel good in a frustrating situation, but the focus here is to see the infamous problem fixed the quickest.
However, if it can help Mikrotik to realize how fast the house is burning...

Well I still have lots of MT devices, and I love some aspects about them. So I definitely hope also some guys from MT are reading this thread and they do care. Except there were no signs of this yet.

ivicask · Fri Oct 18, 2024 10:19 am

After having months of constant disconnects and i tested every beta versions since 7.15 to 7.17 and tried every possible setting i may discovered something.

I changed wireless interfaces default queue type wireless default(SFQ) to CODEL ( /queue/interface>)

add fq-codel-ecn=no fq-codel-interval=60ms fq-codel-limit=800 kind=fq-codel name=fq

All problems stopped, got devices connected for 7 days now which was impossible before.(7.12 beta)

Can anyone else test this also to confirm?

dmfr · Fri Oct 18, 2024 11:33 pm

Can anyone else test this also to confirm?

Just tried with 7.17beta2 and super-fresh 7.17beta4) with no luck.
Queues on wifi1 (5GHz) and wifi2 (2.4Ghz, not used, but anyway) as per your instructions, replacing wireless-default.
Exact same symptoms.

Test setup used :
- Realtek 8821ce / AX201 laptops, running bittorrent to generate bulk traffic
- Pixel 4a streaming video feed (webrtc like, continuous traffic, no buffering)

In matter of seconds : video stuttering and event. stops. Bit Torrent traffic falling to zero.
Controller log : connection lost / not responding / disconnect / reconnect

Tried again the same after 7.14.3 downgrade, and tried again, and again.
- BitTorrent at 15/20 MB/s (realtek AC max in real life)
- smooth video feeds (with strictly no buffering)

Josephny · Sat Oct 19, 2024 4:49 am

After having months of constant disconnects and i tested every beta versions since 7.15 to 7.17 and tried every possible setting i may discovered something.

I changed wireless interfaces default queue type wireless default(SFQ) to CODEL ( /queue/interface>)
Code: Select all
add fq-codel-ecn=no fq-codel-interval=60ms fq-codel-limit=800 kind=fq-codel name=fq
All problems stopped, got devices connected for 7 days now which was impossible before.(7.12 beta)

Can anyone else test this also to confirm?

I just tried this (ax3, iPhone) and the frequent association/disconnection continues.

Thank you for the working on this!

ivicask · Sat Oct 19, 2024 5:36 am

Can anyone else test this also to confirm?
Just tried with 7.17beta2 and super-fresh 7.17beta4) with no luck.
Queues on wifi1 (5GHz) and wifi2 (2.4Ghz, not used, but anyway) as per your instructions, replacing wireless-default.
Exact same symptoms.

Test setup used :
- Realtek 8821ce / AX201 laptops, running bittorrent to generate bulk traffic
- Pixel 4a streaming video feed (webrtc like, continuous traffic, no buffering)

In matter of seconds : video stuttering and event. stops. Bit Torrent traffic falling to zero.
Controller log : connection lost / not responding / disconnect / reconnect

Tried again the same after 7.14.3 downgrade, and tried again, and again.
- BitTorrent at 15/20 MB/s (realtek AC max in real life)
- smooth video feeds (with strictly no buffering)

Yeah, "not responding" is another issue, I never saw this in my logs, my fix helped with "connection lost" or "query timeout" type of logs under full signal..

TikTime24 · Sun Oct 20, 2024 2:53 pm

After having months of constant disconnects and i tested every beta versions since 7.15 to 7.17 and tried every possible setting i may discovered something.

I changed wireless interfaces default queue type wireless default(SFQ) to CODEL ( /queue/interface>)
Code: Select all
add fq-codel-ecn=no fq-codel-interval=60ms fq-codel-limit=800 kind=fq-codel name=fq
All problems stopped, got devices connected for 7 days now which was impossible before.(7.12 beta)

Can anyone else test this also to confirm?

Hey Ivica, how did you calculate fq-codel-interval and fq-codel-limit? Why 60ms and 800?

dmfr · Sun Oct 20, 2024 9:15 pm

Yeah, "not responding" is another issue, I never saw this in my logs, my fix helped with "connection lost" or "query timeout" type of logs under full signal..

"Connection lost" is actually the 7.17 rename of the infamous "SA Query timeout".
Different log name, same disease.
Despite all potential fixes tried, it invariably narrows down to the bogus "qcom driver update" introduced in 7.15, which for some reason seem very hard to admit at Mikrotik.

woland · Mon Oct 21, 2024 1:46 pm

My replacement AP did not get delivered in time, so I thankfully tested the suggestion von @ivicask on 7.17b4. I tried testing with HW queue only and also with Codel. I did not notice any positive changes in behavior.
Too bad

infabo · Mon Oct 21, 2024 4:13 pm

@ anyone with wpa3-psk enabled and flapping clients: try to enable GCMP (in addition to CCMP). On security profile or directly on the wifi interface:

/interface wifi security set encryption=ccmp,gcmp

woland · Tue Oct 29, 2024 6:12 pm

Thanks @infabo !
Unfortunately I always had both (CCMP & GCMP) enabled.

netmn · Thu Oct 31, 2024 12:48 pm

so we must using 7.14.3 version for normal functionality, great

Santi70 · Thu Oct 31, 2024 1:18 pm

I had that problem for a long time, it was removed by itself at some point with version 15

# 2024-10-31 12:13:09 by RouterOS 7.16.1
# software id = G48Y-1U35
#
# model = RBD52G-5HacD2HnD
# serial number = xxxx
/interface wifi security
add authentication-types=wpa2-psk,wpa3-psk disabled=no ft=yes ft-over-ds=yes name=sec1 wps=disable
/interface wifi
set [ find default-name=wifi1 ] channel.band=2ghz-n .frequency=2412 .width=20mhz \
    configuration.country=Spain .mode=ap .ssid=mired .tx-power=6 disabled=no security=sec1
set [ find default-name=wifi2 ] channel.band=5ghz-ac .frequency=5660,5220 .width=20/40mhz \
    configuration.country=Spain .mode=ap .ssid=mired .tx-power=18 disabled=no mtu=1500 security=\
    sec1

Jelezka · Sat Nov 02, 2024 9:42 pm

7.16.1 - same problem(( SA Query timeout

robmaltsystems · Sat Nov 02, 2024 11:22 pm

This topic has now been around for over a year. At some point, we all call it a day. I travel with my laptop to all sorts of places and rarely have an issue. Sure, we all end up in places where they're trying to use an underpowered access point and way too many clients. But generally I just connect and work.

But not at home with my hAP ax2 where I'm usually no more than a few metres away and there's only maybe 10 devices connected. Stability is poor.

Keep getting adverts for WiFi 7 routers. Seriously tempted. Doubt it's can be any worse.

Jef61 · Sat Nov 02, 2024 11:34 pm

Tried 7.16.1 today but again many disconnects on WiFi, and back to 7.14.3

woland · Mon Nov 04, 2024 11:37 am

But generally I just connect and work.
But not at home with my hAP ax2 where I'm usually no more than a few metres away and there's only maybe 10 devices connected. Stability is poor.

I´m very sad, that I have to agree. Me and my family are using different laptops, from very cheap to very expensive, some old, some brand new. We almost never experience any issues with WLAN. It´s just the CAPax + WPA3.
Since last Friday, the issues are gone as I have given up and replaced the CAPax by a somewhat smaller, but similar in appearance device, which only costs slightly more.
Now we have perfect coverage in every corner of our flat, there is no jitter, no timeouts, no problems and no more time investment needed.
Of course: that device does not support SMB or running containers, but I could not care less. I needed a working AP!

MT has signalized not much interest into looking in this issue since 7.14.3!!!

infabo · Mon Nov 04, 2024 12:54 pm

Please provide a name of the new AP - or it did not happen.

woland · Mon Nov 04, 2024 2:27 pm

Hmm, I did avoid it, so as to not make the MT fanatics too angry.

But since you don´t believe me otherwise: it´s a TP-Link Omada EAP673 with an OC200 controller (I might add some more APs in the future). They are both fed by a HEXPoE. Firewall/router is a an RB5009 here.
I´ve decided to not jump on the WIFI7 train yet and save some money, but also a lot of electric power.

On my other family site I have 2 slightly older EAP670 + a single EAP615 with the same controller. Switches are from MT, firewall is Opnsense.
This setup runs since 2 years, without any problems/tuning on the WIFI side. That´s something, because If I run a scan I get over 100 SSIDs (some have insane TX power) as this is located inside a courtyard. I get lots of noise from every direction.

I don't have any photos, but if I did, I'd probably be a bit embarrassed to show my sloppy cabling.

infabo · Mon Nov 04, 2024 2:52 pm

Thank you. There are not many Mikrotik wireless fanatics here. If any at all (maybe erlinden

).

erlinden · Mon Nov 04, 2024 3:07 pm

eddieb · Tue Nov 05, 2024 7:57 am

/me too ...
running all MT wifi here

infabo · Tue Nov 05, 2024 8:33 am

I am running Mikrotik wireless as well. But I would not call me a die-hard fan of the gear. But I did not find anything better that matches my requirements. Always open for improvement.

infabo · Thu Nov 07, 2024 10:19 pm

So, now I have wap ax running for about a week and I can't seem to have any of the issues discussed here. I have it pretty much on default, meaning I have wpa2-psk/wpa3-psk enabled and all the other bells and whistles like FT and so on. No issues. Well, don't have fancy pants latest iPhones nor do I have any "smart" IOT wifi devices. Some AX200 cards (win10/linux) as well. But nothing exploded nor did something go crazy.

woland · Fri Nov 08, 2024 10:46 am

Strange, @infabo, maybe you are not running jitter/loss sensitive sessions and you did not look at the logs? Maybe you don´t have interference?
Maybe there was something in my config? But if that was the case, why did others report similar issues like mine. Anyway: I´m not going to throw out my CAPax, so for future reference:
give us your config or nothing happened.

Ps. there were no explosions on my side, just disconnects & jitter

seriquiti · Fri Nov 08, 2024 10:57 am

I'm on 7.16.1 on my HAP AX2 at home and still getting WIFI "Lockouts" too.

10-20 seconds of no data going through to wifi clients - totally unresponsive. 7.14.3 doesn't have the issue.

I don't even have WPA3 enabled. Have tried different frequences with no difference. It's at the point where I have installed an old HAP AC Lite where WIFI actually works.

infabo · Fri Nov 08, 2024 11:14 am

My log is flooded with "too strong signal" log entries ("xxxxxx@cap-wifi2 disconnected, too strong signal, signal strength 159"). But this is nothing ever reported here and I have already reported that to Mikrotik. SA query timeout only occasional, no more frequently than on cap ac running wifi-qcom-ac.

Regarding the interference: pretty sure I have no interference. 5ghz spectrum is clean as clean can get. Even on 2ghz I have only one neighbor AP in reach where I can easily use a different channel. Regarding the jitter thing I can't tell. I have no webrtc or any other kind of streams in use. So I can't say.

/interface wifi channel
add frequency=2412,2442,2472 name=channel-2ghz reselect-interval=6h..12h
add frequency=5490-5710 name=channel-5ghz reselect-interval=6h..12h
/interface wifi security
add authentication-types=wpa2-psk,wpa3-psk encryption=ccmp,gcmp ft=yes ft-over-ds=yes name=foobar wps=disable
add authentication-types=wpa2-psk,wpa3-psk encryption=ccmp,gcmp name=foobar-guest wps=disable
/interface wifi capsman
set enabled=yes upgrade-policy=suggest-same-version
/interface wifi configuration
add country=Austria datapath=foobar-guest multicast-enhance=enabled name=foobar-guest security=foobar-guest ssid=foobar-guest
add channel=channel-2ghz country=Austria datapath=foobar multicast-enhance=enabled name=foobar-2ghz security=foobar ssid=foobar
add channel=channel-5ghz country=Austria datapath=foobar multicast-enhance=enabled name=foobar-5ghz security=foobar ssid=foobar
/interface wifi datapath
add bridge=bridge client-isolation=yes name=foobar-guest
add bridge=bridge name=foobar
/interface wifi provisioning
add action=create-dynamic-enabled disabled=no master-configuration=foobar-2ghz slave-configurations=foobar-guest supported-bands=2ghz-n
add action=create-dynamic-enabled disabled=no master-configuration=foobar-5ghz supported-bands=5ghz-ac

woland · Fri Nov 08, 2024 11:45 am

Thanks @infabo! I don´t see any difference worth mentioning, but I don´t have access to my config now.
I have never seen that "too strong signal" entry.
Maybe your clients are only using WPA2?
The SA Query timeouts mostly happened to laptops further away from the AP, but not only.
As for the jitter, I spend a lot of time in teleconferences, so probably that´s the reason of my sensitivity.

Beste Grüße

Fri Nov 08, 2024 12:44 pm

Strange, @infabo, maybe you are not running jitter/loss sensitive sessions and you did not look at the logs?

I've got logs from my ax³ going back to August, and I see only 55 instances of "not responding" in that time, the first being 41 days ago, so roughly once a day. The only WiFi bug I'm experiencing is the one where it occasionally latches onto the 2.4GHz and won't switch to 5 until forced.

Maybe you don´t have interference?

I'm in a small town, in a detached house, but not so far from neighbors that I'd make that claim. I can see a dozen other networks at the moment.

give us your config or nothing happened.

Okay.

woland · Fri Nov 08, 2024 2:40 pm

I appreciate your answer and your homepage @tangent!
I´m completely clueless, why these issues affect someone, while others don´t have them. It might have something to do with the fact, that in my 2 setups there is interference from many other APs, as both are located in a courtyard on the 2nd floor, facing many other flats.
I certainly had no day passing by without at least a few tens of timeouts.

I´ll certainly observe how MT WIFI makes progress, as the versatility of MT HW & SW is fascinating, but I don´t regret having been replaced it.

DesertDweller · Sun Nov 10, 2024 10:06 pm

Hopefully this helps someone. I simply changed the channel from 36 ( 5180 ) to 40 ( 5200 ) and the problem went away.
Edit: spoke too soon :/

MrRobotdev · Sat Nov 16, 2024 10:59 am

Still No solution for this problem.... An ideas how can solve it?

balu · Tue Nov 19, 2024 4:01 pm

What's new in 7.17beta5 (2024-Nov-13 12:51):

*) wifi - add information to each interface, showing which CAPsMAN manages it or which CAP hosts it when applicable;
*) wifi - added station-roaming support (additional fixes);
*) wifi - fixed failure with "auto" peer update on the OWE interface;
*) wifi-qcom-ac - fix possible conflict between radio and USB initialization on hAP ac2;
*) wifi-qcom-ac - improved CPU load balancing and system stability;

I think it's worth trying.

erlinden · Tue Nov 19, 2024 5:34 pm

Still No solution for this problem.... An ideas how can solve it?

Can you share your config?
I read a lot of people running into problems, while others have perfectly stable connections. It might be config related, at least that is pretty easy to analyse.

/interface wifi export

Remove serial and any other private info, post between code tags by using the </> button.

I used @tangent's config as baic config, it can be found here:
https://tangentsoft.com/mikrotik/wiki?n ... ome+WiFi&p

Wed Nov 20, 2024 9:13 am

If the latest beta version does not solve your issue, please send supout.rif file to support, describing in detail about what happened.

Sheriff1972 · Wed Nov 20, 2024 9:54 am

I am looking forward to the latest WiFi changes getting rolled into a stable release. At this point I will give it a try

balu · Wed Nov 20, 2024 11:04 am

If the latest beta version does not solve your issue, please send supout.rif file to support, describing in detail about what happened.

So far it looks good - no drops all day. The logs are clear too. My device is AX3.

jdub88 · Wed Nov 20, 2024 11:54 am

Just wanted to add my $0.02 here, too. This has been a huge problem for me for a while now. I have a hAP AX3. I work from home and regularly have to be on video calls, which is usually when this issue will rear it's head. I've tried skipping DFS channels, disabling WPA3..nothing seems to have helped. At the moment I have my work VLAN SSID running only on 2.4GHz which has been more stable. I am in the UK, so I've set the correct country.

Here's my wifi config - does anything look out of place here?

interface wifi
set [ find default-name=wifi1 ] channel.skip-dfs-channels=10min-cac comment=IOT configuration.country="United Kingdom" .mode=ap .ssid=IOT disabled=no security.authentication-types=wpa2-psk,wpa3-psk
set [ find default-name=wifi2 ] channel.skip-dfs-channels=10min-cac comment=IOT configuration.country="United Kingdom" .mode=ap .ssid=IOT disabled=no security.authentication-types=wpa2-psk,wpa3-psk .connect-priority=0
add comment=WORK configuration.hide-ssid=no .mode=ap .ssid=WORK mac-address=XX:XX:XX:XX:XX:XX master-interface=wifi1 name=wifi3 security.authentication-types=wpa3-psk .connect-priority=0
add comment=WORK configuration.hide-ssid=no .mode=ap .ssid=WORK disabled=no mac-address=XX:XX:XX:XX:XX:XX master-interface=wifi2 name=wifi4 security.authentication-types=wpa3-psk .connect-priority=0
add comment=GUEST configuration.mode=ap .ssid=GUEST disabled=no mac-address=XX:XX:XX:XX:XX:XX master-interface=wifi1 name=wifi5 security.authentication-types=wpa2-psk,wpa3-psk
add comment=GUEST configuration.mode=ap .ssid=GUEST disabled=no mac-address=XX:XX:XX:XX:XX:XX master-interface=wifi2 name=wifi6 security.authentication-types=wpa2-psk,wpa3-psk
add comment=HOME configuration.mode=ap .ssid=HOME disabled=no mac-address=XX:XX:XX:XX:XX:XX master-interface=wifi1 name=wifi7 security.authentication-types=wpa2-psk,wpa3-psk
add comment=HOME configuration.mode=ap .ssid=HOME disabled=no mac-address=XX:XX:XX:XX:XX:XX master-interface=wifi2 name=wifi8 security.authentication-types=wpa2-psk,wpa3-psk

The consensus here seems to be to downgrade to 7.14.3 - However given the big changes at 7.15 to wifi, is that as simple as installing the ros and qcom package for this version and hitting downgrade, or are there config changes/other caveats to be aware of? I am reluctant to try the beta version; I don't need or want latest and greatest, I just need my multiple VLANs & WiFi to be stable. My recent experience upgrading even on the stable channel has been....disappointing, shall we say!

I hope Mikrotik can fix this problem ASAP and turn that golden version that actually gives stable wifi into an LTS.

mainTAP · Wed Nov 20, 2024 1:44 pm

I am also experiencing this issue on AX2 and Chateau LTE18 ax both running 7.16.1 and it's quite frustrating.

balu · Wed Nov 20, 2024 1:57 pm

Do you even read what I wrote above, or are you just typing these posts to write something? @jdub88, have you tried the version I mentioned? On my AX3, the problem no longer occurs.

mndtrp · Wed Nov 20, 2024 2:10 pm

If the latest beta version does not solve your issue, please send supout.rif file to support, describing in detail about what happened.

Can you share what change in beta5 is related to resolving this issue?

ateran · Wed Nov 20, 2024 3:01 pm

They renamed the log message so you are not going to see the "SA Query timeout" message.
It's in the changelog: wifi - re-word the "SA Query timeout" log message to "not responding";
So yeah, problem solved...

erlinden · Wed Nov 20, 2024 3:43 pm

FFS, creating a profile just to make fun.

@mndtrip:
*) wifi - added station-roaming support (additional fixes);

In addition, I used the config supplied by @tangent:
https://tangentsoft.com/mikrotik/wiki?n ... ome+WiFi&p

You may want to try this to see if it helps.

infabo · Wed Nov 20, 2024 3:44 pm

If the latest beta version does not solve your issue, please send supout.rif file to support, describing in detail about what happened.
Can you share what change in beta5 is related to resolving this issue?

Can you share the issue you are experiencing besides the log message? It is your first post in this topic.

ateran · Wed Nov 20, 2024 4:05 pm

I created the profile because I'm fed up with basic functionality not working in a wireless router.
I have a hAP ax³ and since I had it never worked well with multiple devices. But the worst thing is that I cannot even use the 5Ghz band with my notebook(having Intel AX200 card) because of the frequent disconnects, standing 2 meters away from the device. I tested it with the latest beta too, same issues present.
This forum, reddit etc. is full of these problems about Mikrotik wireless devices, but still some people like to blame the users

Wed Nov 20, 2024 4:14 pm

I'm sorry about your experience, but as you can see in this thread, beta versions do solve most of the issues for many people.
If you are running the latest beta and stll have some issues, you have to post the full logs and problem descriptions, as we don't know if it's even related to what is being fixed in the betas.

mainTAP · Wed Nov 20, 2024 4:24 pm

Updated the AX2 to the beta5 but the issue is still present.

 2024-11-20 14:29:20 wireless,info 8C:17:59:xx:xx:xx@5ghz disconnected, not responding, signal strength -53
 2024-11-20 14:29:28 wireless,info 8C:17:59:xx:xx:xx@5ghz connected, signal strength -53
 2024-11-20 14:29:44 wireless,info 8C:17:59:xx:xx:xx@5ghz disconnected, not responding, signal strength -50
 2024-11-20 14:29:45 wireless,info 8C:17:59:xx:xx:xx@5ghz connected, signal strength -52
 2024-11-20 15:13:24 wireless,info 8C:17:59:xx:xx:xx@5ghz disconnected, connection lost, signal strength -54
 2024-11-20 15:13:25 wireless,info 8C:17:59:xx:xx:xx@2ghz connected, signal strength -46
 2024-11-20 15:16:31 wireless,info 8C:17:59:xx:xx:xx@2ghz disconnected, not responding, signal strength -47
 2024-11-20 15:16:33 wireless,info 8C:17:59:xx:xx:xx@2ghz connected, signal strength -49
 2024-11-20 15:19:35 wireless,info 8C:17:59:xx:xx:xx@2ghz disconnected, not responding, signal strength -47
 2024-11-20 15:19:37 wireless,info 8C:17:59:xx:xx:xx@2ghz connected, signal strength -47
 2024-11-20 15:21:40 wireless,info 8C:17:59:xx:xx:xx@2ghz disconnected, not responding, signal strength -48
 2024-11-20 15:21:40 wireless,info 8C:17:59:xx:xx:xx@5ghz connected, signal strength -56

jdub88 · Wed Nov 20, 2024 4:50 pm

@jdub88, have you tried the version I mentioned? On my AX3, the problem no longer occurs.

Not yet, no - I am rather reluctant to try betas when there's plenty of folks saying it hasn't addressed their issue. I can't mess about too much with this router for work reasons.

2.4Ghz is working well for me at the moment

alibloke · Wed Nov 20, 2024 5:27 pm

Does this setting help you guys?

security.connect-priority=0/1

mndtrp · Wed Nov 20, 2024 5:41 pm

Can you share what change in beta5 is related to resolving this issue?
Can you share the issue you are experiencing besides the log message? It is your first post in this topic.

Single HAP AX2 providing WIFI 2.4Ghz and 5GHz WIFI.
Seeing "disconnected, connection lost, signal strength -<number>
Persistent issues with MS Teams calls and casting to Chromecasts.
Mobile phone disconnects/reconnects.
Issues are only noticeable on 5Ghz.
It's been like this post 7.14.3 and I'm tired of testing builds. That is why I asked.

infabo · Wed Nov 20, 2024 6:20 pm

I have a hAP ax³ and since I had it never worked well with multiple devices. But the worst thing is that I cannot even use the 5Ghz band with my notebook(having Intel AX200 card) because of the frequent disconnects, standing 2 meters away from the device. I tested it with the latest beta too, same issues present.

I have Intel AX200 card too in my notebook. Access point is wap ax right now though. Usually cap ac (with wifi-qcom-ac package) for a very long time. No, I do not have frequent disconnects. 5m and three brick walls away. Yes, 5ghz. Yes, it just works. What now? Maybe this is primarily all an AX3 issue?

But I can tell you one thing: Intel AX200 is a diva. At least the Linux drivers (written by Intel lol).

mainTAP · Wed Nov 20, 2024 6:34 pm

For me the 2ghz seems even worse than 5ghz :

 2024-11-20 15:13:24 wireless,info 8C:17:59:xx:xx:xx@5ghz disconnected, connection lost, signal strength -54
 2024-11-20 15:13:25 wireless,info 8C:17:59:xx:xx:xx@2ghz connected, signal strength -46
 2024-11-20 15:16:31 wireless,info 8C:17:59:xx:xx:xx@2ghz disconnected, not responding, signal strength -47
 2024-11-20 15:16:33 wireless,info 8C:17:59:xx:xx:xx@2ghz connected, signal strength -49
 2024-11-20 15:19:35 wireless,info 8C:17:59:xx:xx:xx@2ghz disconnected, not responding, signal strength -47
 2024-11-20 15:19:37 wireless,info 8C:17:59:xx:xx:xx@2ghz connected, signal strength -47
 2024-11-20 15:21:40 wireless,info 8C:17:59:xx:xx:xx@2ghz disconnected, not responding, signal strength -48
 2024-11-20 15:21:40 wireless,info 8C:17:59:xx:xx:xx@5ghz connected, signal strength -56
 2024-11-20 16:55:00 wireless,info 8C:17:59:xx:xx:xx@5ghz disconnected, connection lost, signal strength -60
 2024-11-20 16:55:02 wireless,info 8C:17:59:xx:xx:xx@5ghz connected, signal strength -57
 2024-11-20 16:55:48 wireless,info 8C:17:59:xx:xx:xx@5ghz disconnected, connection lost, signal strength -52
 2024-11-20 16:55:48 wireless,info 8C:17:59:xx:xx:xx@2ghz connected, signal strength -47
 2024-11-20 16:58:51 wireless,info 8C:17:59:xx:xx:xx@2ghz disconnected, not responding, signal strength -48
 2024-11-20 16:59:00 wireless,info 8C:17:59:xx:xx:xx@2ghz connected, signal strength -48
 2024-11-20 17:02:02 wireless,info 8C:17:59:xx:xx:xx@2ghz disconnected, not responding, signal strength -47
 2024-11-20 17:02:13 wireless,info 8C:17:59:xx:xx:xx@2ghz connected, signal strength -46
 2024-11-20 17:04:23 wireless,info 8C:17:59:xx:xx:xx@2ghz disconnected, not responding, signal strength -47
 2024-11-20 17:04:26 wireless,info 8C:17:59:xx:xx:xx@2ghz connected, signal strength -47
 2024-11-20 17:07:29 wireless,info 8C:17:59:xx:xx:xx@2ghz disconnected, not responding, signal strength -47
 2024-11-20 17:07:38 wireless,info 8C:17:59:xx:xx:xx@2ghz connected, signal strength -47
 2024-11-20 17:10:40 wireless,info 8C:17:59:xx:xx:xx@2ghz disconnected, not responding, signal strength -47
 2024-11-20 17:10:47 wireless,info 8C:17:59:xx:xx:xx@2ghz connected, signal strength -46
 2024-11-20 17:13:50 wireless,info 8C:17:59:xx:xx:xx@2ghz disconnected, not responding, signal strength -47
 2024-11-20 17:13:52 wireless,info 8C:17:59:xx:xx:xx@2ghz connected, signal strength -48
 2024-11-20 17:16:55 wireless,info 8C:17:59:xx:xx:xx@2ghz disconnected, not responding, signal strength -48
 2024-11-20 17:16:57 wireless,info 8C:17:59:xx:xx:xx@2ghz connected, signal strength -484
 2024-11-20 17:20:00 wireless,info 8C:17:59:xx:xx:xx@2ghz disconnected, not responding, signal strength -49
 2024-11-20 17:20:08 wireless,info 8C:17:59:xx:xx:xx@2ghz connected, signal strength -48
 2024-11-20 17:23:11 wireless,info 8C:17:59:xx:xx:xx@2ghz disconnected, not responding, signal strength -47
 2024-11-20 17:23:13 wireless,info 8C:17:59:xx:xx:xx@2ghz connected, signal strength -47
 2024-11-20 17:26:16 wireless,info 8C:17:59:xx:xx:xx@2ghz disconnected, not responding, signal strength -45
 2024-11-20 17:26:23 wireless,info 8C:17:59:xx:xx:xx@2ghz connected, signal strength -44
 2024-11-20 17:29:25 wireless,info 8C:17:59:xx:xx:xx@2ghz disconnected, not responding, signal strength -47
 2024-11-20 17:29:36 wireless,info 8C:17:59:xx:xx:xx@2ghz connected, signal strength -46

woland · Thu Nov 21, 2024 1:32 pm

For me the 2ghz seems even worse than 5ghz :

Sry. but not very useful, pls. give some details: ROS Version ? Config? Chipset in client?