UPDATE: For now I suggest to revert to rc15 and stay at that version till further notice.
Now there will be some rc builds published where client will stay in this broken state. Problem is that changes in the background to server/client side are so massive that at this state there is no point for us to fixing it just yet.
All entries below are already confirmed and reported to DEV for fixing.
Higher priority problems:
Client updater broken.
Lower priority problems:
Adapt dude link labels to be able to show 10G traffic and larger (snmp part left to fix);
Enhancement requests:
Add option to use functions and oids in notification messages;
Add AES encryption method to dude side snmp v3 profiles;
Add option to configure user in a way to allow access only to certain panels;
Changes in v6.37rc4:
*) Added support for The Dude configuration from CLI; (work in progress).
Notes:
At the moment only initial support has been added. While moving forwards in rc builds more functionality will become available in cli.
Due to the massive changes in background various features in dude might be broken. We are aware of that.
Client auto-updater is broken and manual install of rc builds (at least early ones) will be needed.
*** v6.37 db is no longer backwards compatible with v6.36 version. Make sure that you have backup of v6.36 db if you intend to downgrade server.**
*) Added support for The Dude configuration from CLI; (work in progress)
*) Fixed - Copy/Pase; (broken in previous rc)
*) Fixed - Undo/Redo; (broken in previous rc)
Updated from 6.36rc40 to 6.37rc5 and The Dude client will not update, therefore The Dude is now, effectively, completely non-functional. What’s worse is that there’s no 6.37rc5 Dude Client on the MikroTik website so there seems no way to get a functional client.
Yeah, was just saying that even in rc5 it still isn’t working. I found the client above where I was looking in the CHR page - there really should be a link to the client in the CHR area, too.
(Thanks for the snappy (speed-wise) response!)
Can I also add that even though Agent functionality was restored towards the end of the 6.36rc process, it looks like it has now been broken again - at least in 6.37rc5 I can no longer connect to any Agents.
If that you is your main server then I suggest to leave it at v6.36 build at least for now. These first rc builds of v6.37 might break some functions. If it’s just a test server then go on.
And Agents are indeed broken. Problem is now reported for fixing.
This has got me wondering. Agents work, then Agents break, then Agents work, then Agents break. What sort of source coding system are you guys using internally that results in so many breakages of previously working code as you move forward?
*) Major change - The Dude now uses winbox port, this includes agents. The port
should change automatically both in client loader and agent configuration.
*) Fixed - Client auto update; (broken in one of previous rc builds)
*) Fixed - Object Copy/Paste between maps; (broken in one of previous rc builds)
*) Fixed - Agents broken; (broken in one of previous rc builds)
That will change when CLI support for The Dude will be fully finished.
Data polling will go dormant only if you disable the devices in Device list. Just by disabling map server wont stop collecting data from those devices.
At some point in the future web interface will return in a new form.
At this point I cannot say if The Dude will appear as separate app on Android or iOS. Either way I speculate that web interface will get returned first and for start it will do for mobile devices.
Downgrade to older versions wont be possible from v6.37. To much major changes in the background. You will need to have two clients installed one for v6.36 and other for v6.37.
