This is a fantastic radio at a very competitive price point. We have been installing them about as fast as we can for short wireless hops. There are a few things about them however that I think either we are confused or there is still a bit of work on the firmware. We are using the 6.47.3 (stable) release and use The Dude to monitor our network.
For reference, we give the radios an IP on the bridge and put “all” interfaces on the bridge.
From time to time we end up with a Cube Lite60 that will fail with the service ping but is still accessible via the cli using a MAC telnet session. It still works perfectly fine as a bridge passing traffic but you simply can not ping it (or connect with WinBox unless you use a MAC connection instead of an IP connection). Both of these of course require being on the network directly attached.
You can go to the AP Bridge (master) and simply disable the wlan60-station that is not responding for a second and then re-enable it to fix the ping issue. It will also generally fix it’s self after some random time before failing again. I don’t think this is a “the Dude” problem as you can’t access the unit via IP when it fails from anyplace on the network using any tool.
This happens mostly on Cube Lite60’s with a license level 4 and multiple Cube’s configured in the “bridge” mode (typically 2 or 3) but I have seen it on a PTP links using default license level 3. We use the stock config (no ip filters).
This happened with older firmware as well.
The other concern is the new mounting bracket. I love it but why did you use all stainless still hardware except for the small screws that go into the plastic to hold the bracket to the Cube? Only the 4 little screws (and thank you for the extra) are coated steal instead of stainless and will corrode. It would also be very nice if Mikrotik also included those brackets on any of the SXTsq products that have the same 4 holes that would accept the bracket.
I can provide Supout.rif (or any other documentation) if you think it would help but I really think this is a very repeatable and common issue.