Code: Select all
Update 2:
Now working workaround(time range 2 days):
Downgrade to ROS to 7.13.2.
2 radar events are registered and "wifi3" come up again on another frequency.
After 1 or 2 weeks I'll set it to "resolved" Code: Select all
Update 1:
It is not necessary to restart the device, it is sufficient to deactivate the interface "wifi3" and then activate it again.
After disable / enable and the CAC-test(1min), will be running again until a radar event comes.
does anyone know a solution?
I think I'll solve it using a script as a workaround.
After a while, if no frequency is specified in the status, restart the interfaceHello
my Audience become after a while running to a "unwanted state" with interface "wifi3".
"wifi3" is not correct working after a while.
At a power down / startup the system all 3 interfaces works well.
After some hours normal working of all 3 interfaces, "wifi3" will become a non-working state.
On winbox shows "wifi3" the state "running" but no frequency show in the channel tab.
While normal operation a value about 5500 mhz is shown.
TX-Power show a value of 31,a very high value, but the interface is not working.
In normal operating a value of 25 is shown.
"wifi1" and "wifi2" are working normal over all time.
The "unwanted state" comes after a "radar" event is shown.
In the eventlog shows that: "wifi3: radar detected on 5560/ac/eeeC"
after that event the interface "wifi3" will never come up again until a reboot or power down / up.
DFS skipped only the 10min CAC. The 1 min detection will be run normal at power up the first time.
The regularly, country(germany) and installation(indoor) is set correctly.
Firmware is 7.13.4
WW2 Driver used
The settings for "wifi3":
set [ find default-name=wifi3 ] channel.skip-dfs-channels=10min-cac .width=20/40/80mhz configuration=cfg1-IoT configuration.country=Germany .mode=ap disabled=no security=sec1-IoT
Greets
