+1Please, return web access feature. Only these stops to migrate dude from windows to CCR. Enything else what we need is worked in 6.35.2 on CCR1016.
+1Please, return web access feature. Only these stops to migrate dude from windows to CCR. Enything else what we need is worked in 6.35.2 on CCR1016.
Thanks for the feedback.We have some ideas for new web interface for The Dude. However at the moment there is no known date on when this new web interface might get implemented and in what form it will come. Note that it will not be re-implementation of old web interface.
Hi! Can you provide info about this 'some plans' to us?)@ste
At the moment that is not possible, but it might be in the future. We have some plans similar plans regarding The Dude to what you described in your request.
Admins would like to ssh into dude server and just say: /dude outages print, /dude device [id=xyz] print. Works with the slowest Smartphone connection.If management from Winbox is added that means it could be also managed from TikApp or at least view some info for devices - up/down status etc.
I'd like to see that a lot even if not soon. And for me at least if this is possible there is no real need for web access.
[jarda@CHR virt1] /dude> pri
enabled: yes
data-directory: disk1/dude
status: applying settings: enabling: vacuuming after page size change
+1 I agree very much with this. Alternative is to use a web interface.It's very inconvenient to install additional client version each time the dude is updated. Please, make the client more universal like winbox is to allow the connection to multiple server versions.
Email notifications now works!!!Changes in v6.36rc33:
*) Fixed - Mac to Ip lookup.
*) Fixed - Auto-discovery feature for devices behind remote Agents.
*) Fixed - Access of ROS tab for devices behind remote Agents.
*) Fixed - Email notifications. (broken in one of previous rc builds)
*) Fixed - Client crash which occurred when in device management window in snmp tab
under interface section any of interfaces where double clicked for detailed view.
I have the same problem.I upgraded from RC 21 to 33 this morning. Upgraded the client to the same version and now when I try to login I get "Operation Failed: 10053:An established connection was aborted by the software in your host machine"
Suggestions on how to troubleshoot this.
I used TCPing on port 2211 and it is responding so I believe the service is up.
dont understand what you mean... Im trying to login dude server via dude client and its says me wrong username and password.Username and password now integrated with user management in ros, you need to use username and password using log into router.
You dude server is on Mikrotik is it service on RouterOS use username and password that you use to log on that router. Before some RC version there is not any more user management in Dude.dont understand what you mean... Im trying to login dude server via dude client and its says me wrong username and password.Username and password now integrated with user management in ros, you need to use username and password using log into router.
Great! our oldest resolved outage is from 2010 .Changes in v6.36rc35:
*) Fixed - Auto-discovery tool has problems with typical homeAP/CPE setups that
has snmp enabled. (only one of many devices gets discovered. Due to identical LAN networks.);
*) Fixed - Outages cannot be removed by "remove resolved" button;
*) Fixed - Link label does not show correct link speed when ROS mastering type is used, in place of 1G it shows 10M.
Unfortunately, the above procedure doesn't work.@dnelson @jcmelik
Download latest client from our download page and reinstall it manually. I think that was the version where we started work on moving client update side to cloud. And this first build didn't contain all of the needed changes, so it cannot update it self to most recent builds.
Yes I get this error on multiple workstations and the Dude server status is running.@jchmelik
You get this error on multiple workstations with latest rc client? Is server status on ROS host "running"?
[jarda@CHR virt1] /dude> vacuum-db
append as-value do file interval once without-paging
action timed out - try again, if error continues contact MikroTik support and send a supout file (13)
Same as for many other programs The Dude installed treats it similarly as program upgrade which is why there is only one entry in windows installed program list. I could check if we can make a portable archive version this. I guess it would fit this case better than installer?Having multiple Dude versions installed in different virtual / physical devices for testing purposes (mainly RC builds). For each version I have separate client software installed on my pc (in its own folder). When I move forward with some versions, I do not need the relevant client anymore. So I go to the "add and remove programs" in Windows7 and I see that there is only one "dude" record to be unistalled while 8 different versions are installed now. Why I cannot remove selectively in the standard way the versions of the dude client that I do not need anymore?
Please, make the windows installer to work correctly with versions! Each version should have its record in "add and remove programs" to be managed separately if installed separately.
That will be done at some point. I understand the issue of syslog not being a whole with The Dude server as it was originally.Please, put the logging to syslog files back.
It's doubtful that Import/Export button will make reappearance in client side.Please, make again backup/restore function to be working like in old 3.6 or 4.0b3 version.
Before we do this, we will dig around and bit more in CLI side. After that we could possibly start adding support for The Dude in Winbox/Webfig side.Please, make the dude commands usable from CLI to be available from Winbox (and webfig) too. Think about to make these functions manageable from the dude client too, if possible.
Vacuum command has no arguments, so they are not relevant.Those additional parameters for dude vacuum-db are not described in the manual:
Code: Select allAre they relevant?Code: Select all[jarda@CHR virt1] /dude> vacuum-db append as-value do file interval once without-paging
In v6.36 final build there wont be that problem, rc39/rc40 had some crashes that occurred on server disable this prevented: disable, export, vacuum.Tried vacuum again with rc40.
Running vaccuum-db in "running" state it failed with message:
Code: Select allCode: Select allaction timed out - try again, if error continues contact MikroTik support and send a supout file (13)