Radio drops out occationally

We are having a strange issue. It seems like the AP/Radio drops out for a seconds or so before it returns back up. See Screenshots.
This causes failed ping requests and the network to go down for <1 sec. The Station is an identical radio.

How can I avoid this? Need rock solid connectivity for remote control operation.


dropped.png
ok.png

# 2024-11-08 13:08:35 by RouterOS 7.15.3
# software id = 50RY-EZBW
#
# model = L23UGSR-5HaxD2HaxD
# serial number = H***C5
/interface bridge
add name=bridge1
/interface wifi
set [ find default-name=wifi1 ] configuration.mode=ap
set [ find default-name=wifi2 ] channel.band=5ghz-ax .skip-dfs-channels=all .width=20mhz configuration.chains=0,1 .country=Bolivia .mode=ap \
    .ssid=XXXXRemote .tx-chains=0,1 .tx-power=40 datapath.bridge=bridge1 disabled=no security.authentication-types=wpa2-psk,wpa3-psk
/interface bridge port
add bridge=bridge1 interface=wifi2
add bridge=bridge1 interface=ether1
/ip address
add address=10.15.140.10/24 interface=bridge1 network=10.15.140.0
/ip dns
set servers=8.8.8.8,8.8.4.4
/ip route
add disabled=no distance=1 dst-address=0.0.0.0/0 gateway=10.15.140.1 pref-src="" routing-table=main scope=30 suppress-hw-offload=no \
    target-scope=10
/system clock
set time-zone-name=Europe/Oslo
/system identity
set name=XXXXX
/system leds
add interface=wifi2 leds=led1,led2,led3,led4,led5 type=wireless-signal-strength
/system note
set show-at-login=no

Anything in logs of both devices?

Logs shows this when connection drops out.
Screenshot 2024-11-09 085401.png
Seems to be related/caused by;

 08:56:22 bridge,stp GENERAL: wifi2:0 discarding
 08:56:22 route,debug,calc GENERAL: route/calc/merge/input/route
 08:56:22 route,debug,calc GENERAL: route/calc/merge/route
 08:56:22 route,debug,calc GENERAL: route/calc/fwp/merge
 08:56:22 route,debug,calc GENERAL: route/calc/publish
 08:56:22 route,debug,calc GENERAL: route/calc/cleanup/route
 08:56:24 bridge,stp GENERAL: wifi2:0 learning
 08:56:25 bridge,stp GENERAL: wifi2:0 discarding
 08:56:27 bridge,stp GENERAL: wifi2:0 learning
 08:56:28 bridge,stp GENERAL: wifi2:0 forwarding
 08:56:28 route,debug,calc GENERAL: route/calc/merge/input/route
 08:56:28 route,debug,calc GENERAL: route/calc/merge/route
 08:56:28 route,debug,calc GENERAL: route/calc/fwp/merge
 08:56:28 route,debug,calc GENERAL: route/calc/publish
 08:56:28 route,debug,calc GENERAL: route/calc/cleanup/route

CONFIG

# 2024-11-09 08:58:20 by RouterOS 7.16.1
# software id = 50RY-EZBW
#
# model = L23UGSR-5HaxD2HaxD
# serial number = HGRXXXXXXXXC5
/interface bridge
add name=bridge1
/interface wifi
set [ find default-name=wifi1 ] channel.band=2ghz-n .frequency=2417 .skip-dfs-channels=disabled .width=20mhz configuration.country=Norway \
    .mode=ap .ssid=STR disabled=no security.authentication-types=""
set [ find default-name=wifi2 ] channel.band=5ghz-n .frequency=5745 .skip-dfs-channels=disabled .width=20mhz configuration.chains=0,1 \
    .country=Bolivia .mode=ap .ssid=XXXX .tx-chains=0,1 .tx-power=28 datapath.bridge=bridge1 disabled=no \
    security.authentication-types=wpa2-psk,wpa3-psk
/interface bridge port
add bridge=bridge1 interface=wifi2
add bridge=bridge1 interface=ether1
add bridge=bridge1 interface=wifi1
/ip address
add address=10.15.140.10/24 interface=bridge1 network=10.15.140.0
/ip dns
set servers=8.8.8.8,8.8.4.4
/ip ipsec profile
set [ find default=yes ] dpd-interval=2m dpd-maximum-failures=5
/ip route
add disabled=no distance=1 dst-address=0.0.0.0/0 gateway=10.15.140.1 pref-src="" routing-table=main scope=30 suppress-hw-offload=no \
    target-scope=10
/system clock
set time-zone-name=Europe/Oslo
/system identity
set name=XXXXX
/system leds
add interface=wifi2 leds=led1,led2,led3,led4,led5 type=wireless-signal-strength
/system logging
add prefix=WIFI topics=wireless
add prefix=INTERFACE topics=interface
add prefix=GENERAL topics=!wireless
/system note
set show-at-login=no

Disabling STP (rstp) alltogether on the bridge seems to have fixed it.

Is there any chance that you actually have some loop in your network? Not necessarily directly on either of these two wireless devices?

Another possibility is that there’s an actual bug (in combination between L23UGSR and recent ROS), but only MT can tell that.

I will recheck. There could very well be some unfortunate setup on the networks (Multiple locations tied together with Mikrotik(ZeroTier) and Peplink.

But I don’t really see how this radio would detect/see this since it is an edge device with only 1 station pseudobridge connected to it (connected to a linux box).

Logs are saying that there are some STP events which cause bridge to block wifi2 interface … and 7 seconds later traffic resumes. As I wrote, those events don’t necessarily originate from either of wifi bridge members, they could start somewhere else and got propagated across other switches and bridges, parts of your L2 network. If you’re sure that there isn’t a loop which would involve the particular wireless interfaces (with ap it’s hard to be sure, any of connected stations could create a loop), you could explicitly set


/interface bridge port
add bridge=bridge1 interface=wifi2 > edge=yes

Interesting. Is there any way I can log those events?

I’m not sure. I some related tings (such as “received packet with own MAC address” or something like that) are logged even by default, not sure if there are some more extensive loggings available for STP.