Changes in v6.37:
*) Fixed - XML import, was only semi successful in some cases.
*) Fixed - Various db import problems.
*) Fixed some client and server crashes.
*) Fixed - Custom created panel functionality.
*) Fixed - Remove resolved buttons; (both)
*) Fixed - Device panel → ROS tab → Device sub-tab “Upgrade” button.
*) Fixed - Tooltips are now displayed correctly in mouse-over device icon window.
*) Major change - The Dude now uses winbox port, this includes agents. The port
should change automatically both in client loader and agent configuration.
*) Change - Disabled upload and drag&drop feature in Dude, for the file management use Winbox, Webfig or ftp.
*) Added support for The Dude configuration from CLI; (work in progress).
*) Added - Option to pass dude login credentials as variables for custom login tools.
*) Added back notification type “Execute on Server”. In this notification you can type
in ROS script and it will be executed on The Dude server host. Useful all kinds
of custom notifications and actions.
*) Added - Dude client will be instantly disconnected when the Dude server has stopped or disabled.
Sending SMS. (now that execute on server option has been added, this wont be added as separate notification type)
Custom email.
And practically anything else.
Note:
Just a precaution, before upgrading to v6.37 create a backup file. As this build db will no longer be compatible with older versions.
The download page does not show a link to the release version of 6.37 dude client yet and connecting with an older client bombs out. Is there another place to get this?
I rolled back to 6.36.3 to fix the service.status issue in 6.37, But do not have a version of the client. Where do I download it at? Also downgrading client does not work. I am getting this error when it tries to connect to 6.36.3 with a 6.37 client. "get settings failed: std failed: not implemented (3),
Need a ftp or somewhere I can download 6.36.3 version of client.
UPDATE: I was able to find one another ADMIN downloaded because it would not autoupdate.
service status notification bug still present in a current release? Im a little suprised that the mikrotik brass let this bug out of the RC builds and into a current release. it’s kind of a doozy for a monitoring system. ETA on a fix for that?
Don’t know where the problem is. We have dude currently on a CHR running on version 6.36.3.
When I update routerOS and dude to 6.37, I am not able to connect to dude server anymore (client on windows is updated as well to 6.37).
Of course to the new dude port 8291.
Status bar in dude shows but doesn’t continue
When I check the Log on dude server, it shows <user [dude] logged in from >
Does anyone have an idea of the cause of this problem
When I rollback the system to 6.36.3 I can connect to dude server fine.
Found the problem. In Version 6.36.3 the user dude only needed rights for policies-> read, (write), dude
With the new Versioin 6.37 dude clients also need to have rights to the policy
I upgraded from 6.36 to 6.37.1 and the upgrade went just fine (CHR), but so far we’ve seen some things that were okay in 6.36, but broken now:
Link lines are all black now, no gradient towards the “full” color
Submap custom labels don’t show (labels for submaps only show if the label field is up-ticked so it uses the default)
Found the problem. In Version 6.36.3 the user dude only needed rights for policies-> read, (write), dude
With the new Versioin 6.37 dude clients also need to have rights to the policy [/quote]
I see that the link to the latest The Dude client is not available on the website. So when using an older version it requests me to update it, but fails…
