Capsman intermittent interrupts

dorking_duck · January 1, 2026, 2:32pm

Hello,

I’m farily new to mikrotik, I’ve a RB5009UG with a MikroTik cAP ax directly connected to it using capsman. Both AP and router are running version 7.20.6 (latest recommended). I’m intermittently getting below messages, as it’s provisioning I’m lossing the wifi for 10-20 seconds. It happens maybe 2-4 times every 24 hours.

2026-01-01 13:28:25 Buffer disconnected @F4:1E:57:E8:09:98%*b, connection interrupted

2026-01-01 13:28:34 Message provision@F4:1E:57:E8:09:98%*b radio F4:1E:57:E8:09:9B

2026-01-01 13:28:34 provision @F4:1E:57:E8:09:98%*b radio F4:1E:57:E8:09:9B

2026-01-01 13:28:34 @F4:1E:57:E8:09:98%*b joined

I’ve checked the ethernet link and it’s not flaping. Not sure what more information that but I followed this guide setting it up https://mikrotikmasters.com/basic-ap-deployment/

Regards

BartoszP · January 1, 2026, 2:36pm

Hi,

Has cAP static IP address or obtained by DHCP. For me it looks as it losts connectivity to CAPSMAN while refreshing IP, CAPSMAN is reprovisioning radio that implies disconnections you observe.

dorking_duck · January 1, 2026, 3:58pm

Thanks a lot! That’s probably the issue, had some issues when setting it up initially so accidently had both DHCP and static. Removed the dynamic one, will monitor it and mark it as solution if it gets solved

[username@AP] > /ip address print
Flags: D - DYNAMIC
Columns: ADDRESS, NETWORK, INTERFACE
#   ADDRESS          NETWORK     INTERFACE
0   10.10.10.2/24    10.10.10.0  bridge
1 D 10.10.10.254/24  10.10.10.0  bridge
[username@AP] > /ip dhcp-client print
Columns: INTERFACE, USE-PEER-DNS, ADD-DEFAULT-ROUTE, STATUS, ADDRESS
# INTERFACE  USE-PEER-DNS  ADD-DEFAULT-ROUTE  STATUS  ADDRESS
0 bridge     yes           yes                bound   10.10.10.254/24
[username@AP] >
[username@AP] > /ip dhcp-client disable 0
[username@AP] >
[username@AP] >
[username@AP] > /ip dhcp-client remove 0
[username@AP] > /ip address print
Columns: ADDRESS, NETWORK, INTERFACE
# ADDRESS        NETWORK     INTERFACE
0 10.10.10.2/24  10.10.10.0  bridge
[username@AP] >

Regards

dorking_duck · January 5, 2026, 1:11pm

Unfortunaly the issue isn’t solved, I’ve enabled debug and getting below logs. The AP is now using a static IP, can’t see any interface flaps, any ideas? Got some logs and AP config below, would router config help? As mentioned it’s intermittent, happened around 8 and 13 today.

Logs from Router (motherduck):
disconnected quackpoint@F4:1E:57:E8:09:98%*b, connection interrupted
provisioning created interface cap-wifi2 for F4:1E:57:E8:09:9B@quackpoint@F4:1E:57:E8:09:98%*b
provision quackpoint@F4:1E:57:E8:09:98%*b radio F4:1E:57:E8:09:9B
provisioning created interface cap-wifi1 for F4:1E:57:E8:09:9A@quackpoint@F4:1E:57:E8:09:98%*b
provision quackpoint@F4:1E:57:E8:09:98%*b radio F4:1E:57:E8:09:9A
quackpoint@F4:1E:57:E8:09:98%*b joined
cap-wifi2: starting AP on 2437/ax
cap-wifi1: starting AP on 5745/ax

Logs from AP (quackpoint):
disconnected from motherduck@04:F4:1C:8F:D9:C9%*7, failed to connect
no suitable CAPsMAN
connected to motherduck@04:F4:1C:8F:D9:C9%*7
selected CAPsMAN motherduck@04:F4:1C:8F:D9:C9%*7

AP configuration:

/interface bridge
add name=bridge
/interface wifi
# managed by CAPsMAN 04:F4:1C:8F:D9:C9%bridge, traffic processing on CAP
# mode: AP, SSID: Murkla_2.4, channel: 2437/ax
set [ find default-name=wifi2 ] configuration.manager=capsman .mode=ap datapath.bridge=bridge disabled=no name=Murkla_2.4
# managed by CAPsMAN 04:F4:1C:8F:D9:C9%bridge, traffic processing on CAP
# mode: AP, SSID: Murkla_5G, channel: 5745/ax
set [ find default-name=wifi1 ] configuration.manager=capsman .mode=ap datapath.bridge=bridge disabled=no name=Murkla_5G
/interface ethernet switch
set 0 cpu-flow-control=yes
/interface bridge port
add bridge=bridge interface=ether1
/ip neighbor discovery-settings
set discover-interface-list=!dynamic
/interface wifi cap
set caps-man-addresses=10.10.10.1 certificate=request discovery-interfaces=bridge enabled=yes
/ip address
add address=10.10.10.2/24 interface=bridge network=10.10.10.0
/ip route
add gateway=10.10.10.1
/system clock
set time-zone-name=Europe/Stockholm
/system identity
set name=quackpoint
/system logging
add topics=caps,debug

jaclaz · January 5, 2026, 1:57pm

You should post logs including date/time (to understand how long the interruption and restoring takes) and a few lines above and below the "key" ones (maybe some other event happened).

It is clear that a disconnection between CAPSMAN and CAP happens, but it is not clear at all if it is initiated on the CAPSMAN or on the CAPS or it depends from another problem (as an example link down on one of the ethernet interfaces).

Yes, post also the configuration of the CAPSMAN device, the one you posted for the CAP seems to me fairly basic, nothing that stands out as a possible cause of the issue in it that I can see.

OT, nice naming, motherduck and quackpoint.

dorking_duck · January 5, 2026, 3:31pm

Thank you, trying to follow a duck theme on most of the network devices

The logs from the devices, looking at the time stamps nothing really stands out other than that the AP failed to connect and that the router tne disconnected. I’m still thinking about testing another cable between the AP and the router just to rule it out, currently don’t have a spare one.

The AP is connected to the router via the POE injector that followed the AP, could that be something? I’ve looked at the load and CPU + memory is low during these events.

Router (motherduck):
2026-01-05 12:49:17	user admin logged in from 10.10.10.17 via winbox
2026-01-05 13:36:32 disconnected quackpoint@F4:1E:57:E8:09:98%*b, connection interrupted
2026-01-05 13:36:49 provisioning created interface cap-wifi2 for F4:1E:57:E8:09:9B@quackpoint@F4:1E:57:E8:09:98%*b
2026-01-05 13:36:49	provision quackpoint@F4:1E:57:E8:09:98%*b radio F4:1E:57:E8:09:9B
2026-01-05 13:36:49	provisioning created interface cap-wifi1 for F4:1E:57:E8:09:9A@quackpoint@F4:1E:57:E8:09:98%*b
2026-01-05 13:36:49	provision quackpoint@F4:1E:57:E8:09:98%*b radio F4:1E:57:E8:09:9A
2026-01-05 13:36:49	quackpoint@F4:1E:57:E8:09:98%*b joined
2026-01-05 13:36:54 cap-wifi2: starting AP on 2437/ax
2026-01-05 13:36:54 cap-wifi1: starting AP on 5745/ax
2026-01-05 13:36:56 lan_dhcp assigned 10.10.10.12 for 98:F4:AB:C2:C8:91 ESP_C2C891
2026-01-05 13:36:56 lan_dhcp deassigned 10.10.10.12 for 98:F4:AB:C2:C8:91 ESP_C2C891
2026-01-05 13:36:56 98:F4:AB:C2:C8:91@cap-wifi2(Murkla_2.4) connected, signal strength -43
2026-01-05 13:37:00 50:EC:50:0F:36:8C@cap-wifi2(Murkla_2.4) associated, signal strength -51

AP (quackpoint):
2026-01-05 12:49:13 user admin logged in from 10.10.10.17 via winbox
2026-01-05 13:36:29 disconnected from motherduck@04:F4:1C:8F:D9:C9%*7, failed to connect
2026-01-05 13:36:33 no suitable CAPsMAN
2026-01-05 13:36:47 connected to motherduck@04:F4:1C:8F:D9:C9%*7
2026-01-05 13:36:47 selected CAPsMAN motherduck@04:F4:1C:8F:D9:C9%*7
2026-01-05 13:37:00 user admin logged out from 10.10.10.17 via winbox
2026-01-05 13:37:17 user admin logged in from 10.10.10.32 via winbox

The router configuration, bride101 is currently not used and can probably be ignored. It was supposed to be a mgmt interface but starting out simple and getting it stable is more prioritized. Ether4 is connected to a TV, had some issues with link flaps on it and the auto neg off seems to have solved that.

/interface bridge
add name=bridge101 protocol-mode=none
add name=lan_bridge
/interface ethernet
set [ find default-name=ether4 ] auto-negotiation=no speed=100M-baseT-full
/interface list
add comment=defconf name=WAN
add comment=defconf name=LAN
/interface wifi channel
add band=5ghz-ax frequency=5180 name=5GHZ::CH36 width=20mhz
add band=5ghz-ax frequency=5200 name=5GHZ::CH40 width=20mhz
add band=5ghz-ax frequency=5220 name=5GHZ::CH44 width=20mhz
add band=5ghz-ax frequency=5240 name=5GHZ::CH48 width=20mhz
add band=5ghz-ax frequency=5745 name=5GHZ::CH149 width=20mhz
add band=5ghz-ax frequency=5765 name=5GHZ::CH153 width=20mhz
add band=5ghz-ax frequency=5785 name=5GHZ::CH157 width=20mhz
add band=5ghz-ax frequency=5805 name=5GHZ::CH161 width=20mhz
add band=5ghz-ax disabled=no frequency=5825 name=5GHZ::CH165 width=20mhz
add band=2ghz-ax disabled=no frequency=2412,2437,2462 name=2GHZ::AUTO width=20mhz
add band=5ghz-ax disabled=no frequency=5180,5200,5220,5240,5745,5765,5785,5805,5825 name=5GHZ::NON-DFS width=20mhz
add band=5ghz-ax disabled=no frequency=5180 name=5GHZ::CH5745 width=20/40/80mhz
add band=5ghz-ax disabled=no frequency=5180,5200,5220,5240 name=5GHZ::UNII-1 width=20mhz
add band=5ghz-ax disabled=no frequency=5745,5765,5785,5805,5825 name=5GHZ::UNII-3 width=20mhz
/interface wifi datapath
add bridge=lan_bridge disabled=no name=datapath-murkla
/interface wifi security
add authentication-types=wpa2-psk disabled=no encryption=ccmp name=sec-murkla
/interface wifi configuration
add channel=5GHZ::NON-DFS datapath=datapath-murkla disabled=no mode=ap name=cfg-5GHz security=sec-murkla ssid=\
    Murkla_5G
add channel=2GHZ::AUTO country=Sweden datapath=datapath-murkla disabled=no mode=ap name=cfg-2.4Ghz security=\
    sec-murkla ssid=Murkla_2.4
/ip pool
add name=pool101 ranges=10.10.1.10-10.10.1.254
add name=lan_pool ranges=10.10.10.10-10.10.10.254
/ip dhcp-server
add address-pool=lan_pool interface=lan_bridge lease-time=1d name=lan_dhcp
add address-pool=pool101 interface=bridge101 name=dhcp101
/disk settings
set auto-media-interface=lan_bridge auto-media-sharing=yes auto-smb-sharing=yes
/interface bridge port
add bridge=lan_bridge comment=defconf interface=ether2
add bridge=lan_bridge comment=defconf interface=ether3
add bridge=lan_bridge comment=defconf interface=ether4
add bridge=lan_bridge comment=defconf interface=ether5
add bridge=lan_bridge comment=defconf interface=ether6
add bridge=lan_bridge comment=defconf interface=sfp-sfpplus1
add bridge=lan_bridge interface=ether1
add bridge=bridge101 interface=ether7
/ip neighbor discovery-settings
set discover-interface-list=LAN
/interface list member
add interface=lan_bridge list=LAN
add interface=ether8 list=WAN
add interface=bridge101 list=LAN
/interface wifi capsman
set enabled=yes package-path=firmware require-peer-certificate=no upgrade-policy=suggest-same-version
/interface wifi provisioning
add action=create-dynamic-enabled disabled=no master-configuration=cfg-5GHz supported-bands=5ghz-ax,5ghz-ac
add action=create-dynamic-enabled disabled=no master-configuration=cfg-2.4Ghz supported-bands=2ghz-ax,2ghz-n
/ip address
add address=10.10.1.1/24 interface=bridge101 network=10.10.1.0
add address=10.10.10.1/24 interface=lan_bridge network=10.10.10.0
/ip cloud
set ddns-enabled=yes
/ip cloud advanced
set use-local-address=yes
/ip dhcp-client
add interface=ether8
/ip dhcp-server lease
add address=10.10.10.10 always-broadcast=yes comment=PS5 mac-address=78:C8:81:D5:CD:47 server=lan_dhcp
add address=10.10.10.50 always-broadcast=yes comment=TV mac-address=F8:4E:58:A0:30:E8 server=lan_dhcp
add address=10.10.10.102 always-broadcast=yes comment=PiholeUnbound mac-address=BC:24:11:02:49:B1 server=lan_dhcp
add address=10.10.10.103 comment=AnsibleServer mac-address=BC:24:11:B5:F5:C1 server=lan_dhcp
add address=10.10.10.104 always-broadcast=yes comment=Portainer mac-address=BC:24:11:D9:AD:B3 server=lan_dhcp
add address=10.10.10.105 always-broadcast=yes comment=Prometheus mac-address=BC:24:11:A8:3B:1F server=lan_dhcp
add address=10.10.10.110 always-broadcast=yes comment="Home Assistant" mac-address=20:F8:3B:00:40:BA server=lan_dhcp
add address=10.10.10.120 always-broadcast=yes comment=Reverseproxy mac-address=BC:24:11:A5:F7:67 server=lan_dhcp
add address=10.10.10.100 always-broadcast=yes comment=ROCK4SE mac-address=AA:D2:2E:AB:B5:82 server=lan_dhcp
add address=10.10.10.101 always-broadcast=yes comment=Proxmox mac-address=E8:FF:1E:DB:52:70 server=lan_dhcp
add address=10.10.10.12 always-broadcast=yes comment="Automation Str\C3\B6mbrytare altan" mac-address=\
    98:F4:AB:C2:C8:91 server=lan_dhcp
add address=10.10.10.14 comment="Automation dreamview" mac-address=60:74:F4:4F:80:2A server=lan_dhcp
add address=10.10.10.13 always-broadcast=yes comment="Automation Bryggeri Temp" mac-address=38:1F:8D:63:57:7D server=\
    lan_dhcp
add address=10.10.10.11 always-broadcast=yes comment="Nintendo Switch" mac-address=BC:CE:25:EB:1A:9F server=lan_dhcp
add address=10.10.10.108 always-broadcast=yes comment=tools mac-address=BC:24:11:03:8D:3F
/ip dhcp-server network
add address=10.10.1.0/24 dns-server=10.10.1.1 gateway=10.10.1.1
add address=10.10.10.0/24 dns-server=10.10.10.102 gateway=10.10.10.1
/ip dns
set allow-remote-requests=yes
/ip dns static
add address=10.10.10.1 comment=defconf name=router.lan type=A
/ip firewall filter
add action=accept chain=input comment="Accept established,related,untracked" connection-state=\
    established,related,untracked
add action=accept chain=input comment="Accept ICMP" protocol=icmp
add action=accept chain=input comment=CAPsMAN dst-address=127.0.0.1
add action=accept chain=input dst-port=5246,5247 in-interface-list=LAN protocol=udp
add action=accept chain=input comment="Allow LAN to router" in-interface-list=LAN
add action=accept chain=input comment="Wireguard regel" dst-address=10.10.10.100 dst-port=51820 protocol=udp \
    src-address=10.10.10.0/24
add action=drop chain=input comment="Drop all not coming from LAN" in-interface-list=!LAN
add action=drop chain=input comment="Drop invalid" connection-state=invalid
add action=drop chain=forward comment="Drop regler ligga h\C3\A4r" disabled=yes out-interface-list=WAN src-address=\
    10.10.10.13
add action=fasttrack-connection chain=forward comment=Fasttrack connection-state=established,related hw-offload=yes
add action=accept chain=forward comment="Accept established,related, untracked" connection-state=\
    established,related,untracked
add action=accept chain=forward comment="Allow port-forwarded traffic" connection-nat-state=dstnat
add action=accept chain=forward comment="Pi-hole DNS UDP" dst-port=53 out-interface-list=WAN protocol=udp \
    src-address=10.10.10.102
add action=accept chain=forward comment="Pi-hole DNS TCP" dst-port=53 out-interface-list=WAN protocol=tcp \
    src-address=10.10.10.102
add action=drop chain=forward comment="Block LAN DNS UDP" dst-port=53 in-interface-list=LAN log=yes \
    out-interface-list=WAN protocol=udp
add action=drop chain=forward comment="Block LAN DNS TCP" dst-port=53 in-interface-list=LAN out-interface-list=WAN \
    protocol=tcp
add action=accept chain=forward comment=Allow_LAN_Internet in-interface-list=LAN out-interface-list=WAN
add action=drop chain=forward comment="drop invalid" connection-state=invalid
add action=drop chain=forward comment=drop_all
/ip firewall nat
add action=masquerade chain=srcnat comment=PAT ipsec-policy=out,none out-interface-list=WAN
add action=dst-nat chain=dstnat comment="Wireguard DNAT" dst-port=123,51820 protocol=udp to-addresses=10.10.10.100 \
    to-ports=51820
add action=dst-nat chain=dstnat disabled=yes dst-port=51820 protocol=udp to-addresses=10.10.10.100 to-ports=51820
/ip kid-control
add name=Cornelis
/ipv6 firewall address-list
add address=::/128 comment="defconf: unspecified address" list=bad_ipv6
add address=::1/128 comment="defconf: lo" list=bad_ipv6
add address=fec0::/10 comment="defconf: site-local" list=bad_ipv6
add address=::ffff:0.0.0.0/96 comment="defconf: ipv4-mapped" list=bad_ipv6
add address=::/96 comment="defconf: ipv4 compat" list=bad_ipv6
add address=100::/64 comment="defconf: discard only " list=bad_ipv6
add address=2001:db8::/32 comment="defconf: documentation" list=bad_ipv6
add address=2001:10::/28 comment="defconf: ORCHID" list=bad_ipv6
add address=3ffe::/16 comment="defconf: 6bone" list=bad_ipv6
/ipv6 firewall filter
add action=accept chain=input comment="defconf: accept established,related,untracked" connection-state=\
    established,related,untracked
add action=drop chain=input comment="defconf: drop invalid" connection-state=invalid
add action=accept chain=input comment="defconf: accept ICMPv6" protocol=icmpv6
add action=accept chain=input comment="defconf: accept UDP traceroute" dst-port=33434-33534 protocol=udp
add action=accept chain=input comment="defconf: accept DHCPv6-Client prefix delegation." dst-port=546 protocol=udp \
    src-address=fe80::/10
add action=accept chain=input comment="defconf: accept IKE" dst-port=500,4500 protocol=udp
add action=accept chain=input comment="defconf: accept ipsec AH" protocol=ipsec-ah
add action=accept chain=input comment="defconf: accept ipsec ESP" protocol=ipsec-esp
add action=accept chain=input comment="defconf: accept all that matches ipsec policy" ipsec-policy=in,ipsec
add action=drop chain=input comment="defconf: drop everything else not coming from LAN" in-interface-list=!LAN
add action=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=!LAN
/system clock
set time-zone-name=Europe/Stockholm
/system identity
set name=motherduck
/system logging
add topics=caps,debug
add topics=caps,debug
add topics=wireless,debug
add topics=caps,info
add topics=caps,debug
add topics=wireless,info
add topics=wireless,debug
/tool mac-server
set allowed-interface-list=LAN
/tool mac-server mac-winbox
set allowed-interface-list=LAN

So nothing fancy in the configuration yet.

jaclaz · January 5, 2026, 3:58pm

Given the timing, the disconnection is initiated from the AP, at:

2026-01-05 13:36:29 disconnected from motherduck@ ...

the router then registers the disconnection after 2 or 3 seconds:

2026-01-05 13:36:32  disconnected quackpoint@ ...

And the re-connection happens as well initiated by the AP:

2026-01-05 13:36:33 no suitable CAPsMAN
2026-01-05 13:36:47 connected to motherduck@ ...

and the router does whatever it is supposed to do a couple seconds later:

...
2026-01-05 13:36:49	quackpoint@F4:1E:57:E8:09:98%*b joined
...

Let's see if any of the more expert members can spot something suspect that could cause the issue, with static addresses it cannot be anymore the DHCP.

I would try with a single fixed freequency set (one for 2.4 and one for 5 GHz) but cannot say if it could be part of the issue.

As a side note, I take back what I said previously about nice names , Murkla seems to come right out of an IKEA store

BartoszP · January 5, 2026, 4:04pm

What device is quackpoint as MAC shows RtBrick Inc as an owner of that MAC?

dorking_duck · January 5, 2026, 4:16pm

Its a MikroTik cAP ax

https://mikrotik.com/product/cap_ax

dorking_duck · January 5, 2026, 4:20pm

Could absolutly try single radio frequence on both bands to narrow it down

And yea, that name has haunted me for way too long but too lazy to reconnect my iot devices

SpeedHeed · January 7, 2026, 4:45pm

Could it be that it connects to CAPSMan via Layer 2? My CAPSMan shows there an IP address instead of the MAC (I manually configured my caps). That would indicate that there's an error on Layer 2.

SpeedHeed · January 7, 2026, 4:49pm

Or maybe just an corrupted Mikrotik OS/Firmware tryed to reinstall ROS via Netinstall?

dorking_duck · January 8, 2026, 10:04am

Thanks, noticed the same thing but when new on a product I wasn’t sure how it was supposed to look, reading more documentation and forum posts lead me to change below (removal of discovery-interfaces on the AP) and from what I can tell it’s using L3 now.

/interface wifi cap set caps-man-addresses=10.10.10.1 certificate=request discovery-interfaces=bridge enabled=yes

To

/interface wifi cap set caps-man-addresses=10.10.10.1 certificate=request discovery-interfaces="" enabled=yes

After the change the logs looks like below (it’s a manual provision)
2026-01-07 12:04:00 provisioning created interface cap-wifi1 for F4:1E:57:E8:09:9A@quackpoint@10.10.10.2
2026-01-07 12:04:00 provision ``quackpoint@10.10.10.2`` radio F4:1E:57:E8:09:9A
2026-01-07 12:04:00 cap-wifi1: stopping AP, disabling
2026-01-07 12:04:00 cap-wifi2: stopping AP, disabling
2026-01-07 12:04:01 provisioning created interface cap-wifi2 for F4:1E:57:E8:09:9B@quackpoint@10.10.10.2
2026-01-07 12:04:01 provision ``quackpoint@10.10.10.2`` radio F4:1E:57:E8:09:9B

With discovery-interfaces set to bridge on AP
2026-01-05 18:05:21 provisioning created interface cap-wifi2 for F4:1E:57:E8:09:9B@quackpoint@F4:1E:57:E8:09:98%*b
2026-01-05 18:05:21 provision quackpoint@F4:1E:57:E8:09:98%*b radio F4:1E:57:E8:09:9B

From the AP

[admin@quackpoint] /interface/wifi/cap> print
                    enabled: yes
       discovery-interfaces:
                certificate: request
         caps-man-addresses: 10.10.10.1
      requested-certificate: <cert>
   current-caps-man-address: 10.10.10.1
  current-caps-man-identity: motherduck

After that it looks more stable, haven’t had an issue since making the change but will monitor it a couple of more days, the change was made the 5th

2026-01-05 19:12:03 wifi CAP settings changed by ssh:admin@10.10.10.32 (/interface wifi cap set caps-man-addresses=10.10.10.1 discovery-interfaces="")

Previously I had issues fairly often

 2025-12-30 17:32:09 caps,info disconnected from motherduck@04:F4:1C:8F:D9:C9%*7, failed to connect
 2025-12-30 19:38:53 caps,info disconnected from motherduck@04:F4:1C:8F:D9:C9%*7, failed to connect
 2025-12-30 19:42:09 caps,info disconnected from motherduck@04:F4:1C:8F:D9:C9%*7, failed to connect
 2025-12-30 20:26:05 caps,info disconnected from motherduck@04:F4:1C:8F:D9:C9%*7, failed to connect
 2025-12-30 20:38:30 caps,info disconnected from motherduck@04:F4:1C:8F:D9:C9%*7, failed to connect
 2025-12-31 12:06:21 caps,info disconnected from motherduck@04:F4:1C:8F:D9:C9%*7, failed to connect
 2025-12-31 21:02:34 caps,info disconnected from motherduck@04:F4:1C:8F:D9:C9%*7, failed to connect
 2025-12-31 21:18:36 caps,info disconnected from motherduck@04:F4:1C:8F:D9:C9%*7, failed to connect
 2025-12-31 21:21:43 caps,info disconnected from motherduck@04:F4:1C:8F:D9:C9%*7, failed to connect
 2025-12-31 22:21:12 caps,info disconnected from motherduck@04:F4:1C:8F:D9:C9%*7, failed to connect
 2026-01-01 07:33:10 caps,info disconnected from motherduck@04:F4:1C:8F:D9:C9%*7, failed to connect
 2026-01-01 13:28:27 caps,info disconnected from motherduck@04:F4:1C:8F:D9:C9%*7, failed to connect
 2026-01-02 18:19:01 caps,info disconnected from motherduck@04:F4:1C:8F:D9:C9%*7, failed to connect
 2026-01-03 04:39:51 caps,info disconnected from motherduck@04:F4:1C:8F:D9:C9%*7, failed to connect
 2026-01-03 16:14:47 caps,info disconnected from motherduck@04:F4:1C:8F:D9:C9%*7, failed to connect
 2026-01-03 20:48:49 caps,info disconnected from motherduck@04:F4:1C:8F:D9:C9%*7, failed to connect
 2026-01-03 21:10:35 caps,info disconnected from motherduck@04:F4:1C:8F:D9:C9%*7, failed to connect
 2026-01-04 20:21:55 caps,info disconnected from motherduck@04:F4:1C:8F:D9:C9%*7, failed to connect
 2026-01-04 20:44:40 caps,info disconnected from motherduck@04:F4:1C:8F:D9:C9%*7, failed to connect
 2026-01-05 08:10:49 caps,info disconnected from motherduck@04:F4:1C:8F:D9:C9%*7, failed to connect
 2026-01-05 13:36:29 caps,info disconnected from motherduck@04:F4:1C:8F:D9:C9%*7, failed to connect
 2026-01-05 17:18:45 caps,info disconnected from motherduck@04:F4:1C:8F:D9:C9%*7, failed to connect
 2026-01-05 18:05:01 caps,info disconnected from motherduck@04:F4:1C:8F:D9:C9%*7, failed to connect
 2026-01-05 18:11:06 caps,info disconnected from motherduck@04:F4:1C:8F:D9:C9%*7, failed to connect