As you can see, when detecting a radar signal, the interface crashes and never works again despite having another NO DFS channel nor does it show any errors.
This is not the first time it has happened to me, but other times I have forgotten to document it
SUP-144391
As you can see it does NOT work, TX POWER without value, STATE: selecting channel and does not show any error
However, in addition to channel 5660, it has 5220 as a secondary NO DFS channel.
I use version 7.13.5 (ax3), and those signals appear randomly, I would say once a month, I assume they are false signals, the other AP (ax2) also has a DFS channel and it did not go down and it is not very far away
Thanks for documenting and reporting the issue to Mikrotik. I have not experienced this behaviour myself - because I either don’t have radar events nor do I restrict the channel frequencies that tight. But I’ve seen several reports in different topics in the last weeks - and all describe this behaviour.
How does the router know it’s a radar? Presumably is it looking for something generating a valid carrier, but no WiFi structure (thereby excluding noise)? Or is it able to discern known genuine radar signals?
I experienced false positives on the legacy wireless driver. The event of “enabling” wifi on one of my tablet devices caused a “radar detection” on AP.