Chateau LTE6 ax: Ring Video Intercom keeps disconnecting

fmontagna · May 15, 2026, 11:30am

Hi all,

I'm experiencing repeated disconnections of a Ring Video Intercom on a MikroTik Chateau LTE6 ax running RouterOS 7.22.3 with the wifi-qcom driver. All other IoT devices on the same SSID/VLAN are stable.

WiFi interface config:
configuration.installation=indoor .ssid="myhome-iot-wifi" .mode=ap .hide-ssid=yes
security.authentication-types=wpa2-psk .group-key-update=1d .disable-pmkid=yes .management-protection=disabled .beacon-protection=disabled .wps=disable
datapath.vlan-id=2091
channel.frequency=2412,2437,2462 .band=2ghz-ax .width=20mhz .skip-dfs-channels=disabled .reselect-time=04:00:00..04:30:00

What I have already tried, without any improvement:

hide-ssid yes/no --> no effect
group-key-update: 1h, 1d --> no effect
channel.band: 2ghz-ax, 2ghz-n, 2ghz-g --> no effect

The device disconnects and reconnects every 1-6 minutes (random intervals). All other 802.11n devices on the same Chateau are stable.

Has anyone experienced something similar or have any suggestions?

Thanks

mkx · May 15, 2026, 11:34am

Log should contain signal strength ... is it higher than around -75? WiFi doesn't work too well with signal strengths below -70 or so, ideally (to get maximum throughput) it should be somewhere between -40 and -55.

holvoetn · May 15, 2026, 11:47am

Other suggestion:
maybe create SSID with only WPA to test ? Maybe even no authentication-type at all (just to test) ?
Some of those IoT devices are known to be VERY "conservative" with wifi security (read: dinosaur ancient).

Just another question:
is it a problem if the device disconnects or is it just because you see it happening that it worries you ?
Is it otherwise usable in the app (I suppose you use Ring app to see what's on the device) ?

fmontagna · May 15, 2026, 12:54pm

Signal strength is consistently between -44 and -50, well within the acceptable range as you can see from the logs:

2026-05-15 13:52:05 wireless,info AC:9F:C3:00:24:04@wifi4(myhome-iot-wifi) connected, signal strength -50
2026-05-15 13:53:01 wireless,info AC:9F:C3:00:24:04@wifi4(myhome-iot-wifi) disconnected, connection lost, signal strength -45
2026-05-15 13:53:01 wireless,info AC:9F:C3:00:24:04@wifi4(myhome-iot-wifi) connected, signal strength -49
2026-05-15 13:53:45 wireless,info AC:9F:C3:00:24:04@wifi4(myhome-iot-wifi) disconnected, connection lost, signal strength -45
2026-05-15 13:53:45 wireless,info AC:9F:C3:00:24:04@wifi4(myhome-iot-wifi) connected, signal strength -50
2026-05-15 13:55:01 wireless,info AC:9F:C3:00:24:04@wifi4(myhome-iot-wifi) disconnected, connection lost, signal strength -45
2026-05-15 13:55:02 wireless,info AC:9F:C3:00:24:04@wifi4(myhome-iot-wifi) connected, signal strength -50
2026-05-15 14:00:46 wireless,info AC:9F:C3:00:24:04@wifi4(myhome-iot-wifi) disconnected, connection lost, signal strength -44
2026-05-15 14:00:46 wireless,info AC:9F:C3:00:24:04@wifi4(myhome-iot-wifi) connected, signal strength -50
2026-05-15 14:02:06 wireless,info AC:9F:C3:00:24:04@wifi4(myhome-iot-wifi) disconnected, connection lost, signal strength -44
2026-05-15 14:02:06 wireless,info AC:9F:C3:00:24:04@wifi4(myhome-iot-wifi) connected, signal strength -50

I wasn't able to complete the initial setup: the Ring app keeps showing an error due to network issues.

I'll try using WPA instead of WPA2.
Tonight I'll try setting up a Unifi access point and connecting it to see if it stays connected with that one.

fmontagna · May 15, 2026, 1:48pm

Update: The issue also occurs when using only WPA or WPA/WPA2 together.

jaclaz · May 15, 2026, 1:54pm

I would tend to exclude a Chateau (in the sense of specific device) issue.
But a RoS<->Ring incompatibiliy of some kind is well possible.

You said you are running 7.22.3, but, which one?:

This is the first Ros I run on this device or it is the first time I attempt to connect to it the Ring.
The setup worked just fine with previous Ros 7.x.y.
Something else changed.

fmontagna · May 15, 2026, 3:20pm

I connected the device for the first time a few days ago; at the time, I had version 7.22.2 installed. The problem was the same, so I tried updating it since version 7.22.3 was available, but the problem persisted.

jaclaz · May 15, 2026, 3:38pm

I believe 7.22.2 sucks excels behaves in a very similar way to 7.22.3.

Which version you can downgrade to (factory version)?

If I were you I would try RouterOS 7.20.8 long-term (yes, 7.20.8, not the newer long term 7.21.4) only to see if the issue is with newish (and not yet fully tested) versions.

Ring (at least in the US) is - I believe - very common, so an incompatibility (if any) would have been noticed and reported by now.

fmontagna · May 15, 2026, 8:14pm

I tried downgrading to 7.20.8, but with that version, the device disconnects about every 10 seconds. I updated to 7.21.4, and the results seem similar to 7.22.2. Maybe with 7.22.3 the situation has improved slightly (I'm not sure).

I tested it with the Unifi AP: it stayed connected for over an hour without any disconnections.
I also tried connecting the Ring to a Shelly 1Plus (connected to my Wi-Fi and with access point mode enabled), and it stays connected there as well.

It seems like a bug or some kind of incompatibility with the ROS wifi-qcom package.

jaclaz · May 15, 2026, 8:54pm

Did you keep firmware "aligned" to RouterOS version?

Post an export of your full configuration, instructions here:
Forum rules - #5 by gigabyte091

Maybe there Is some other settings that Is causing the issue.

fmontagna · May 15, 2026, 9:28pm

Yes, the RouterBOARD firmware is aligned with RouterOS.

Below the configuration:

# 2026-05-15 23:04:35 by RouterOS 7.22.3
# software id = ***
#
# model = S53UG+5HaxD2HaxD&FG621-EA
# serial number = ***
/interface bridge
add admin-mac=XX:XX:XX:XX:XX:XX arp-timeout=1h auto-mac=no dhcp-snooping=yes \
    igmp-snooping=yes name=bridge1 vlan-filtering=yes
/interface wireguard
add listen-port=51820 mtu=1420 name=wg1
/interface vlan
add interface=ether1 name=vlan1036 vlan-id=1036
add comment=lan1 interface=bridge1 name=vlan2090 vlan-id=2090
add comment=iot1 interface=bridge1 name=vlan2091 vlan-id=2091
add comment=srv1 interface=bridge1 name=vlan2092 vlan-id=2092
/interface pppoe-client
add comment=wan1 disabled=no interface=vlan1036 name=pppoe-out1 user=\
    ***
/interface ethernet switch
set 0 cpu-flow-control=yes
/interface list
add comment="wan2 [lte]" name=wan2
add comment=lan1 name=lan1
add name=vpn1
add comment="wan1 [vdsl]" name=wan1
add comment="wan [all]" include=wan1,wan2 name=wan
add name=wan1-mgmt
add name=iot1
add name=srv1
/interface lte apn
add add-default-route=no apn=mobile.vodafone.it comment=vodafone name=\
    vodafone use-peer-dns=no
/interface lte
set [ find default-name=lte1 ] allow-roaming=no apn-profiles=vodafone band="" \
    comment=wan2
/interface wifi channel
add band=5ghz-ax comment=wifi:channel:5g deprioritize-unii-3-4=yes disabled=\
    no frequency=5180-5640 name=wifi:channel1 reselect-time=\
    04:00:00..04:30:00 skip-dfs-channels=10min-cac width=20/40/80mhz
add band=2ghz-ax comment=wifi:channel:2g disabled=no frequency=2412,2437,2462 \
    name=wifi:channel2 reselect-time=04:00:00..04:30:00 skip-dfs-channels=\
    disabled width=20mhz
/interface wifi security
add authentication-types=wpa2-psk,wpa3-psk comment=wifi:myhome-wifi disabled=\
    no name=wifi:sec1 wps=disable
add authentication-types=wpa2-psk beacon-protection=disabled comment=\
    wifi:myhome-iot-wifi disable-pmkid=yes disabled=no group-key-update=1d \
    management-protection=disabled name=wifi:sec2 wps=disable
/interface wifi configuration
add comment=wifi:myhome-wifi country=Italy datapath.vlan-id=2090 disabled=no \
    installation=indoor mode=ap name=wifi:config1 security=wifi:sec1 ssid=\
    myhome-wifi
add comment=wifi:myhome-iot-wifi datapath.vlan-id=2091 disabled=no hide-ssid=\
    yes installation=indoor mode=ap name=wifi:config2 security=wifi:sec2 \
    ssid=myhome-iot-wifi
/interface wifi
set [ find default-name=wifi1 ] channel=wifi:channel1 comment=\
    wifi:5g:myhome-wifi configuration=wifi:config1 configuration.mode=ap \
    disabled=no
set [ find default-name=wifi2 ] channel=wifi:channel2 comment=\
    wifi:2g:myhome-wifi configuration=wifi:config1 configuration.mode=ap \
    disabled=no security.ft=yes .ft-over-ds=yes
add channel=wifi:channel2 comment=wifi:2g:myhome-iot-wifi configuration=\
    wifi:config2 configuration.mode=ap disabled=no mac-address=\
    XX:XX:XX:XX:XX:XX master-interface=wifi2 name=wifi4
/ip pool
add comment=pool:dhcp:vlan2091 name=pool2 ranges=10.36.91.150-10.36.91.199
add comment=pool:dhcp:vlan2090 name=pool1 ranges=10.36.90.150-10.36.90.199
/ip dhcp-server
add address-pool=pool2 bootp-support=none comment=dhcp:vlan2091 interface=\
    vlan2091 lease-time=1w name=dhcp2
add address-pool=pool1 bootp-support=none comment=dhcp:vlan2090 interface=\
    vlan2090 lease-time=1d name=dhcp1
/queue type
add fq-codel-ecn=no kind=fq-codel name=fq-codel-ethernet-default
/queue interface
set ether1 queue=fq-codel-ethernet-default
set ether2 queue=fq-codel-ethernet-default
set ether3 queue=fq-codel-ethernet-default
set ether4 queue=fq-codel-ethernet-default
set ether5 queue=fq-codel-ethernet-default
/disk
set usb1 media-interface=*2000000
add media-interface=bridge1 parent=usb1 partition-number=1 partition-offset=\
    1048576 partition-size=62006493184 type=partition
/disk settings
set auto-media-interface=bridge1
/ip smb
set enabled=no
/interface bridge port
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged \
    interface=ether2 pvid=2090
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged \
    interface=ether3 pvid=2091
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged \
    interface=ether4 pvid=2092
add bridge=bridge1 frame-types=admit-only-vlan-tagged interface=wifi1
add bridge=bridge1 frame-types=admit-only-vlan-tagged interface=wifi2
add bridge=bridge1 frame-types=admit-only-vlan-tagged interface=wifi4
add bridge=bridge1 frame-types=admit-only-vlan-tagged interface=ether5
/ip settings
set tcp-syncookies=yes
/ipv6 settings
set forward=no
/interface bridge vlan
add bridge=bridge1 tagged=ether5,wifi1,wifi2,wifi4 vlan-ids=2091
add bridge=bridge1 tagged=ether5 vlan-ids=2092
add bridge=bridge1 tagged=ether5,wifi1,wifi2 vlan-ids=2090
/interface list member
add interface=lte1 list=wan2
add interface=pppoe-out1 list=wan1
add interface=wg1 list=vpn1
add interface=ether1 list=wan1-mgmt
add interface=vlan2091 list=iot1
add interface=vlan2092 list=srv1
add interface=vlan2090 list=lan1
/ip address
add address=10.36.80.2/30 comment=wan1-mgmt interface=ether1 network=\
    10.36.80.0
add address=10.36.81.0/24 comment=wg1 interface=wg1 network=10.36.81.0
add address=10.36.91.1/24 comment=iot1 interface=vlan2091 network=10.36.91.0
add address=10.36.90.1/24 comment=lan1 interface=vlan2090 network=10.36.90.0
add address=10.36.92.1/24 comment=srv1 interface=vlan2092 network=10.36.92.0
/ip cloud
set ddns-enabled=yes update-time=no
/ip dhcp-server config
set accounting=no
/ip dhcp-server network
add address=10.36.90.0/24 comment=dhcp:vlan2090 dns-server=10.36.90.1 \
    gateway=10.36.90.1 netmask=24 ntp-server=10.36.90.1
add address=10.36.91.0/24 comment=dhcp:vlan2091 dns-server=10.36.90.1 \
    gateway=10.36.91.1 netmask=24 ntp-server=10.36.90.1
/ip dns
set allow-remote-requests=yes mdns-repeat-ifaces=vlan2090,vlan2091 servers=\
    8.8.8.8,1.1.1.1 use-doh-server=https://cloudflare-dns.com/dns-query \
    verify-doh-cert=yes
/ip firewall filter
add action=accept chain=input comment=\
    "input:accept:conn-state=established/related/untracked" connection-state=\
    established,related,untracked
add action=drop chain=input comment="input:drop:conn-state=invalid" \
    connection-state=invalid log=yes log-prefix=drop:invalid
add action=accept chain=input comment=\
    "input:accept:sinft=lan1,daddr=10.36.90.1,proto=tcp,dport=22,80" \
    dst-address=10.36.90.1 dst-port=22,80 in-interface-list=lan1 log=yes \
    log-prefix=accept:lan1-http protocol=tcp
add action=accept chain=input comment=\
    "input:accept:sintf=vpn1,daddr=10.36.90.1,proto=tcp,dport=22,80" \
    dst-address=10.36.90.1 dst-port=22,80 in-interface-list=vpn1 log=yes \
    log-prefix=accept:vpn1-http protocol=tcp
add action=accept chain=input comment=\
    "input:accept:sintf=wan1,proto=udp,dport=51820,comment=wireguard" \
    dst-port=51820 in-interface-list=wan1 log=yes log-prefix=\
    accept:wan-wireguard protocol=udp
add action=accept chain=input comment="input:accept:sintf=!wan,proto=icmp" \
    in-interface-list=!wan protocol=icmp
add action=accept chain=input comment=\
    "input:accept:sintf=!wan,proto=udp,dport=53" dst-port=53 \
    in-interface-list=!wan log-prefix=input-dns protocol=udp
add action=accept chain=input comment=\
    "input:accept:sintf=!wan,proto=udp,dport=123" dst-port=123 \
    in-interface-list=!wan log-prefix=input:ntp protocol=udp
add action=accept chain=input comment="input:accept:sintf=!wan,daddr=255.255.2\
    55.255,proto=udp,sport=68,dport=67" dst-address=255.255.255.255 dst-port=\
    67 in-interface-list=!wan protocol=udp src-port=68
add action=accept chain=input comment="input:accept:daddr=127.0.0.1" \
    dst-address=127.0.0.1
add action=drop chain=input comment=input:drop log=yes log-prefix=\
    drop:default
add action=fasttrack-connection chain=forward comment=\
    "forward:fasttrack-connection:conn-state=established/related" \
    connection-state=established,related
add action=accept chain=forward comment=\
    "forward:accept:conn-state=established/related/untracked" \
    connection-state=established,related,untracked
add action=drop chain=forward comment="forward:drop:conn-state=invalid" \
    connection-state=invalid log=yes log-prefix=drop:invalid
add action=drop chain=forward comment=\
    "forward:drop:conn-state=new,nat-state=!dstnat,sintf=wan" \
    connection-nat-state=!dstnat connection-state=new in-interface-list=wan \
    log=yes log-prefix=drop:wan-not-dstnated
add action=accept chain=forward comment=\
    "forward:accept:sintf=lan1,dintf=iot1" in-interface-list=lan1 log-prefix=\
    lan1-to-iot1 out-interface-list=iot1
add action=accept chain=forward comment=\
    "forward:accept:sinft=lan1,dintf=srv1" in-interface-list=lan1 \
    out-interface-list=srv1
add action=accept chain=forward comment=\
    "forward:accept:sintf=lan1,dintf=wan1_mgmt" in-interface-list=lan1 \
    out-interface-list=wan1-mgmt
add action=accept chain=forward comment="forward:accept:sintf=lan1,dintf=wan" \
    in-interface-list=lan1 log=yes log-prefix=accept:lan1-wan \
    out-interface-list=wan
add action=accept chain=forward comment="forward:accept:sintf=iot1,dintf=wan" \
    in-interface-list=iot1 log=yes log-prefix=accept:iot1-wan \
    out-interface-list=wan
add action=accept chain=forward comment="forward:accept:sintf=srv1,dintf=wan" \
    in-interface-list=srv1 log=yes log-prefix=accept:srv1-wan \
    out-interface-list=wan
add action=accept chain=forward comment=\
    "forward:accept:sintf=vpn1,saddr=10.36.81.0/24,dintf=lan1" \
    in-interface-list=vpn1 out-interface-list=lan1 src-address=10.36.81.0/24
add action=accept chain=forward comment=\
    "forward:accept:sintf=vpn1,saddr=10.36.81.0/24,dintf=iot1" \
    in-interface-list=vpn1 out-interface-list=iot1 src-address=10.36.81.0/24
add action=accept chain=forward comment=\
    "forward:accept:sintf=vpn1,saddr=10.36.81.0/24,dinft=srv1" \
    in-interface-list=vpn1 out-interface-list=srv1 src-address=10.36.81.0/24
add action=drop chain=forward comment=forward:drop log-prefix=drop:default
/ip firewall nat
add action=masquerade chain=srcnat comment=\
    "srcnat:masquerade:dintf=wan1_mgmt" out-interface-list=wan1-mgmt
add action=masquerade chain=srcnat comment="srcnat:masquerade:dintf=wan1" \
    out-interface-list=wan1
add action=masquerade chain=srcnat comment="srcnat:masquerade:dintf=wan2" \
    ipsec-policy=out,none out-interface-list=wan2
/ip ipsec policy
set 0 disabled=yes
/ip route
add comment=wan1:check-gw:cloudflare disabled=no distance=1 dst-address=\
    1.1.1.2/32 gateway=pppoe-out1 routing-table=main scope=10
add comment=wan1:check-gw:opendns disabled=no distance=1 dst-address=\
    208.67.220.220/32 gateway=pppoe-out1 routing-table=main scope=10
add comment=wan2:check-gw:cloudflare disabled=no distance=1 dst-address=\
    1.0.0.2/32 gateway=lte1 routing-table=main scope=10
add comment=wan2:check-gw:opendns disabled=no distance=1 dst-address=\
    208.67.222.222/32 gateway=lte1 routing-table=main scope=10
add check-gateway=ping comment=wan1:default disabled=no distance=1 \
    dst-address=0.0.0.0/0 gateway=1.1.1.2 routing-table=main target-scope=11
add check-gateway=ping comment=wan1:default disabled=no distance=1 \
    dst-address=0.0.0.0/0 gateway=208.67.220.220 routing-table=main \
    target-scope=11
add check-gateway=ping comment=wan2:default disabled=no distance=2 \
    dst-address=0.0.0.0/0 gateway=1.0.0.2 routing-table=main target-scope=11
add check-gateway=ping comment=wan2:default disabled=no distance=2 \
    dst-address=0.0.0.0/0 gateway=208.67.222.222 routing-table=main \
    target-scope=11
/ipv6 address
add address=fd27:129::6f4:1cff:fe49:f591 eui-64=yes interface=vlan2091
/ipv6 firewall address-list
add address=::/128 comment="defconf: unspecified address" list=bad_ipv6
add address=::1/128 comment="defconf: lo" list=bad_ipv6
add address=fec0::/10 comment="defconf: site-local" list=bad_ipv6
add address=::ffff:0.0.0.0/96 comment="defconf: ipv4-mapped" list=bad_ipv6
add address=::/96 comment="defconf: ipv4 compat" list=bad_ipv6
add address=100::/64 comment="defconf: discard only " list=bad_ipv6
add address=2001:db8::/32 comment="defconf: documentation" list=bad_ipv6
add address=2001:10::/28 comment="defconf: ORCHID" list=bad_ipv6
add address=3ffe::/16 comment="defconf: 6bone" list=bad_ipv6
/ipv6 firewall filter
add action=accept chain=input comment=\
    "defconf: accept established,related,untracked" connection-state=\
    established,related,untracked
add action=drop chain=input comment="defconf: drop invalid" connection-state=\
    invalid
add action=accept chain=input comment="defconf: accept ICMPv6" protocol=\
    icmpv6
add action=accept chain=input comment="defconf: accept UDP traceroute" \
    dst-port=33434-33534 protocol=udp
add action=accept chain=input comment=\
    "defconf: accept DHCPv6-Client prefix delegation." dst-port=546 protocol=\
    udp src-address=fe80::/10
add action=accept chain=input comment="defconf: accept IKE" dst-port=500,4500 \
    protocol=udp
add action=accept chain=input comment="defconf: accept ipsec AH" protocol=\
    ipsec-ah
add action=accept chain=input comment="defconf: accept ipsec ESP" protocol=\
    ipsec-esp
add action=accept chain=input comment=\
    "defconf: accept all that matches ipsec policy" ipsec-policy=in,ipsec
add action=drop chain=input comment=\
    "defconf: drop everything else not coming from LAN" in-interface-list=\
    !*2000011
add action=fasttrack-connection chain=forward comment="defconf: fasttrack6" \
    connection-state=established,related
add action=accept chain=forward comment=\
    "defconf: accept established,related,untracked" connection-state=\
    established,related,untracked
add action=drop chain=forward comment="defconf: drop invalid" \
    connection-state=invalid
add action=drop chain=forward comment=\
    "defconf: drop packets with bad src ipv6" src-address-list=bad_ipv6
add action=drop chain=forward comment=\
    "defconf: drop packets with bad dst ipv6" dst-address-list=bad_ipv6
add action=drop chain=forward comment="defconf: rfc4890 drop hop-limit=1" \
    hop-limit=equal:1 protocol=icmpv6
add action=accept chain=forward comment="defconf: accept ICMPv6" protocol=\
    icmpv6
add action=accept chain=forward comment="defconf: accept HIP" protocol=139
add action=accept chain=forward comment="defconf: accept IKE" dst-port=\
    500,4500 protocol=udp
add action=accept chain=forward comment="defconf: accept ipsec AH" protocol=\
    ipsec-ah
add action=accept chain=forward comment="defconf: accept ipsec ESP" protocol=\
    ipsec-esp
add action=accept chain=forward comment=\
    "defconf: accept all that matches ipsec policy" ipsec-policy=in,ipsec
add action=drop chain=forward comment=\
    "defconf: drop everything else not coming from LAN" in-interface-list=\
    !*2000011
/ipv6 nd
set [ find default=yes ] advertise-dns=yes
/system clock
set time-zone-name=Europe/Rome
/system identity
set name=***
/system ntp client
set enabled=yes
/system ntp server
set enabled=yes
/system ntp client servers
add address=pool.ntp.org
/system routerboard mode-button
set enabled=yes on-event=dark-mode
/system routerboard wps-button
set enabled=yes on-event=wps-accept

jaclaz · May 15, 2026, 9:49pm

Cannot see anything that seems related, but you have a few asterisks that shouldn't be there, check point #21:
GP & CSA (Good Practice and Common Sense Advice) for Mikrotik devices

Can you try disabling the ft settings in /interface wifi?

fmontagna · May 16, 2026, 9:07am

I fixed the points where the asterisks were; they shouldn't be related.

I tried disabling FT (it should be disabled by default),but nothing changed.

fmontagna · May 16, 2026, 9:27am

Digging a little deeper, I analyzed the .debug section of supout.rif.

From what I can tell, the qcom driver seems to be encountering an error with this specific client:

localphy:nlMsgCb: unhandled err, ack or no genlmsghdr: 2400000002000001d6750400e7000000fe000000a404000018000100d6750400e7000000
seq 292310 pid 231  err 254

Below are the extended logs:

2026.05.16-08:53:59.75@0: localphy:lcmdUpdateSta: AC:9F:C3:00:24:04 isolation 0
2026.05.16-08:53:59.75@0: localphy:lcmdUpdateSta: AC:9F:C3:00:24:04 mask 0x2 set 0x2
2026.05.16-08:53:59.75@0: localphy:nlMsgCb: unhandled err, ack or no genlmsghdr: 2400000002000001d6750400e7000000fe000000a404000018000100d6750400e7000000
2026.05.16-08:53:59.75@0: seq 292310 pid 231  err 254
2026.05.16-08:54:27.57@0: localphy:nlDelStation: AC:9F:C3:00:24:04 vap->state 2
2026.05.16-08:54:27.57@0: localphy:LConn::receive: unknown message 0x201a
2026.05.16-08:54:27.67@3: ActAp::handleAuth: new AC:9F:C3:00:24:04@<0x14d350|wifi4> sig -55
2026.05.16-08:54:27.67@3: ActAp::staAuthOk: AC:9F:C3:00:24:04@<0x14d350|wifi4>
2026.05.16-08:54:27.67@3: ActAp::handleAssoc: AC:9F:C3:00:24:04@<0x14d350|wifi4> signal strength: -55 reassoc: no
2026.05.16-08:54:27.67@3: ActAp::staAssocOk: AC:9F:C3:00:24:04@<0x14d350|wifi4>
2026.05.16-08:54:27.68@3: localphy:nlVendor: unhandled subcmd 0x14a data 00ac9fc3002404
2026.05.16-08:54:27.68@3: RsnAuthSta::associated: delay
2026.05.16-08:54:27.78@3: RsnAuthSta::associated: akm 0xfac02 ucast 0xfac04
2026.05.16-08:54:27.78@3: ActAp::staRsnSend: size 99
2026.05.16-08:54:27.80@2: lphy-qcom: instkeys 0x2 and probably frame 2
2026.05.16-08:54:27.80@0: localphy:nlMsgCb: unhandled err, ack or no genlmsghdr: 240000000200000181760400e700000000000000240000001800050081760400e7000000
2026.05.16-08:54:27.80@0: seq 292481 pid 231  ack
2026.05.16-08:54:27.80@0: RsnAuthSta::handleFrame: 3
2026.05.16-08:54:27.80@0: RsnAuth::gtkGet: new user, gtk 2091
2026.05.16-08:54:27.80@0: RsnAuthSta::send3: rsc=
2026.05.16-08:54:27.80@0: ActAp::staRsnSend: size 155
2026.05.16-08:54:27.80@2: RsnAuthSta::handleFrame: 3
2026.05.16-08:54:27.80@2: ActAp::staRsnKey: cipher 0xfac04 key 716085996449c68e9bd93e193493b530
2026.05.16-08:54:27.80@2: ActAp::staRsnEvent: 4
2026.05.16-08:54:27.80@2: localphy:lcmdUpdateSta: AC:9F:C3:00:24:04 isolation 0
2026.05.16-08:54:27.80@2: localphy:lcmdUpdateSta: AC:9F:C3:00:24:04 mask 0x2 set 0x2
2026.05.16-08:54:27.80@2: localphy:nlMsgCb: unhandled err, ack or no genlmsghdr: 240000000200000184760400e7000000fe000000a40400001800010084760400e7000000
2026.05.16-08:54:27.80@2: seq 292484 pid 231  err 254
2026.05.16-08:55:47.64@0: localphy:nlDelStation: AC:9F:C3:00:24:04 vap->state 2
2026.05.16-08:55:47.64@0: localphy:LConn::receive: unknown message 0x201a
2026.05.16-08:55:47.75@0: ActAp::handleAuth: new AC:9F:C3:00:24:04@<0x14d350|wifi4> sig -56
2026.05.16-08:55:47.75@0: ActAp::staAuthOk: AC:9F:C3:00:24:04@<0x14d350|wifi4>
2026.05.16-08:55:47.75@0: ActAp::handleAssoc: AC:9F:C3:00:24:04@<0x14d350|wifi4> signal strength: -55 reassoc: no
2026.05.16-08:55:47.75@0: ActAp::staAssocOk: AC:9F:C3:00:24:04@<0x14d350|wifi4>
2026.05.16-08:55:47.76@2: localphy:nlVendor: unhandled subcmd 0x14a data 00ac9fc3002404
2026.05.16-08:55:47.76@2: RsnAuthSta::associated: delay
2026.05.16-08:55:47.86@2: RsnAuthSta::associated: akm 0xfac02 ucast 0xfac04
2026.05.16-08:55:47.86@2: ActAp::staRsnSend: size 99
2026.05.16-08:55:47.88@2: lphy-qcom: instkeys 0x2 and probably frame 2
2026.05.16-08:55:47.88@2: localphy:nlMsgCb: unhandled err, ack or no genlmsghdr: 24000000020000016b780400e70000000000000024000000180005006b780400e7000000
2026.05.16-08:55:47.88@2: seq 292971 pid 231  ack
2026.05.16-08:55:47.88@2: RsnAuthSta::handleFrame: 3
2026.05.16-08:55:47.88@2: RsnAuth::gtkGet: n

jaclaz · May 16, 2026, 9:42am

I think it is time to open a support ticket at support@mikrotik.com.

I presume that the Ring thingy is as "plain" as it can be an there is little or nothing to change in its settings.

What I find strange is that it should be a rather common device, so it should have already generated reports similar to yours.

But, on the other hand, the good Mikrotik guys recently botched iPhone/IOS connections in 7.22 (+Winbox 3) and there were very few (proportionally to the installed base of Mikrotik and Apple) people reporting the issue.

fmontagna · May 16, 2026, 9:50am

Yeah, that's right. There's not much I can do on the Ring side.

I'll open a ticket with Mikrotik support. I'll let you know if there are any updates.