First of all, congratulations, MikroTik! I was waiting for this day for quite some time now. And let me tell you why..
You have routers, switches, cpe's, ap's - basically almost everything small to medium size WISP needs. And The Dude is like a glue for all this MikroTik ecosystem. You can quickly access devices via winbox, monitor traffic, access terminal, use tools like torch, spectral scan, wireless scan, bandwidth test, etc in a very convenient way (and they all work via proprietary MT protocol, which I'm ok with, because you don't need to additionally configure anything since it ships prepared (at least it should in theory)). For those that are almost 100% MT based, this is an essential and extremely convenient tool that saves lots of effort and provides functionality that otherwise would have to be implemented via several different products, each with its own complexities and still wouldn't deliver the same convenience. It's tremendous advantage and one of the things that keep me loyal to MT. I'm so used to it, I can't imagine myself letting it go.
Here's the story of my Dude..
Even if it was considered abandonware, I'm still using The Dude till now. There are of course limitations and bugs, but somehow I've found ways of dealing with them and ended up quite happy. I've dropped the Windows based server long ago and for a few years I'm using x86 ROS running as Xen DomU guest. It's of course v5.26, since that was the last version that used to work with 4.0b3.. But it works like charm: counts uptime of almost 1.5 years now (got down only because of hardware upgrade), monitors >2000 devices, collects bandwidth data of wireless and ethernet links, sends emails, sms notifications and even calls my phone in case of critical emergencies. There are some wizardry done with vlans, bridges and interfaces, ending up with The Dude machine having filtered access to all the parts of the network it needs to access and monitor.
To address a couple of the requests made by others I have something to say:
- The Android/iOS version or implementation would be nice, but I think the Windows client version has to be mature in the first place. The same applies for web version. Even now you can permanently run The Dude client in a dedicated or virtual machine with Linux (via Wine) or even Windows and access it via VNC/RDP. If you're paranoid about security, VPNs and other tunneling options are there for you. In this modern age of large screen smartphones and LTE everywhere, it's quite good and convenient solution. I'm using it everyday and have nothing to complain about.
- If it saves MikroTik any effort and speeds up development, keep only ROS version of The Dude server-side. The quality shouldn't suffer from the desire to be universal.
And finally, my personal wishes and suggestions:
- Fix the 'export to file' in Windows client. Now the client crashes and fails to make an export on large Dude setups (though I see you added this function via cli, so it's probably going the right way);
- Fix the 32-bit only SNMP counters and do something to make it possible to collect RB260GS bandwidth graphs (again - MT ecosystem!);
- Upgrade winbox in The Dude or make it possible to drop in the latest winbox.exe ourselves;
- Make some user roles not only to limit changes to The Dude, but also for non-admin users not to be able to connect via winbox to ROS devices or even better - for different user groups to connect using different users in device's ROS (for example guest);
- Make the Dude server multi-threaded;
It's already a great piece of software, it needs so little to become even greater
Thanks for the great news again! Good luck