I have setup a couple of testing units with DUDE 3 beta 1 and began the painful process of Beta Testing.
When runing the Dude Server in the services mode, remote Dude Clients and Remote Dude Agents will not connect in either the remote mode or the secure modes. (Running on Windows 2003 Server)
Dude 3 need the ability to inport backup files from the 2.X version in the future. Otherwise, those with complex setups will pull out their hair.
A few of the build in tools such as Winbox, Scan, etc. should have the ability to select the device that this runs under, ie. the tool winbox is none functional for none RouterOS boxes
Dude shows me everything as down (even if I have ping to the devices).
I don’t have snmp probes to ROS devices (I think it is connected with the ping problem above).
The wallpaper turns white when I zoom.
For now - unusable.
Back to v2.1 hopefully everything seems fine for now, except that percents of Disk space are too long (10-15 symbols after decimal point) and icons are very fat now .
I second this ability… I’ve installed 3.0 Beta 2 without the crash while installing The Dude what I saw with 3.0 Beta 1. Thought it all went incredibly nice and smooth.. but sadly enough it didn’t..
I’m able to import my backup from a Dude 2.1 version..
I get a graphical representation of all these devices, the services/probes but for some stupid reason it just won’t identify the physical devices..
This results in a huge load of red and garbled icons of devices..
Please Mikrotik guru’s, please fix this.. (I need to get hair again..)