Page 1 of 1

The Dude, work continues: v6.35rc test builds.

Posted: Mon Feb 01, 2016 11:38 am
by krisjanis
As The Dude is still in testing stage I suggest moving on to v6.35rc builds for those that experience issues with v6.34 release.


Known issues in v6.35rc44 (reported for fixing):

All entries below are already confirmed and reported to DEV for fixing.

Higher priority problems:
* Device discovery tool does not work with Agents.
* Devices behind Agents have problems: link labels with mastering type ROS, ROS login, ROS upgrade
* Some servers still experience issues after latest 6.34rc/6.34 builds (Checking this actively based on info provided by sent in supout files).
* Dude server does not reconnect to agents after connection has been lost to them.
* Cannot access ROS mgmt tab in device settings for device that are behind agent.
* Vacuum takes up a lot of space on system store for large db's.
* 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.)
* Device MAC to IP lookup broken.
* Cannot upgrade device is it is running old ROS version: 5.26, 6.7. Error: "router packages unknown"

Lower priority problems:
* Client - local pinger broken.
* Client - Charts do not get renewed in real time when viewed.
* Adapt dude link labels to be able to show 10G traffic
speed and larger (snmp part left to fix)
* Outages cannot be removed by "remove resolved" button.
* Dude loader preferences menu "auto connect at startup" check-box seems to be ignored.
* SNMP returns incorrectly formated values from some of"/system health" menu oid's.
* Importing db from v4 removes assigned icons from devices/device-types.
* Memory related default function no longer work.
* Client crash on update (finally reproduced...)

Enhancement requests:
* Add check-box in dude client loader to allow upgrade/downgrade without prompting user each time.
* 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.
* Add new notification method that allows to use ROS tool sms.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Mon Feb 01, 2016 12:21 pm
by krisjanis
Some things on which I didn't have change to answer in v6.34rc topic:

# Those ssh log entries are from dude ssh probe.

# Regarding those that noticed server side hogging more hardware resources than usually. It would be good to check it with 6.35rc1 build and if that cpu load problem is still there then send supout from that server host to support@mikrotik.com

# One change was made to the dude server defaults, with v6.34 build. the server is now by defaults disabled after package installation and needs to be enabled. On few of my dude test servers I noticed that on upgrade from v6.34rc builds it did by some reason disable the server even it it was already running there previously.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Mon Feb 01, 2016 6:21 pm
by mars
will it be possible to get a refresh button in the client

Re: The Dude, work continues: v6.35rc test builds.

Posted: Mon Feb 01, 2016 11:47 pm
by alexspils
missing dude-6.35rc2.npk

Re: The Dude, work continues: v6.35rc test builds.

Posted: Mon Feb 01, 2016 11:57 pm
by ebreyit
missing dude-6.35rc2.npk

Also getting this when trying to update CCR from system \ packages in winbox 3.1

Re: The Dude, work continues: v6.35rc test builds.

Posted: Tue Feb 02, 2016 10:10 pm
by LogicalNZ
It would be fantastic if "The Dude" could support ROMON as a connectivity protocol.

What do the rest of you think????

Re: The Dude, work continues: v6.35rc test builds.

Posted: Wed Feb 03, 2016 2:24 pm
by satish143
Mikrotik support suggested to try 6.35rc3 because my mikrotik was getting reboot in certain load. Where is the download link for 6.35rc3?

Re: The Dude, work continues: v6.35rc test builds.

Posted: Wed Feb 03, 2016 2:34 pm
by ste
"Remove Resolved" in Services->Outages does not work. Did not work on 4.0beta3, too. So I have thousands of entries over the years.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Wed Feb 03, 2016 2:52 pm
by krisjanis
Changes in 6.35rc3:

* Fix server crash that can sometimes be encountered on db import.
* Fix XML backup import (again, broken in one of last v6.34rc builds).
* Fix some servers crashes.
* Fixed: Charts not automatically refreshing.
* Changed client loader status field to be wider in order to fit some of the longer error messages.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Wed Feb 03, 2016 2:59 pm
by krisjanis
@satish143

rc3 should now be available.

@ste

"Remove resolved" button is indeed broken, problem reported to DEV as bug.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Wed Feb 03, 2016 3:00 pm
by ste
As The Dude is still in testing stage I suggest moving on to v6.35rc builds for those that experience issues with v6.34 release.


<b>Known issues in v6.35rc1 (reported for fixing):<b/>

<b>All entries below are already confirmed and reported to DEV for fixing.</b>

High priority problems:
* Device discovery tool does not work with Agents.
* Devices behind Agents have problems: link labels with mastering type ROS, ROS login, ROS upgrade
* Some servers still experience issues after latest 6.34rc/6.34 builds (Checking this actively based on info provided by sent in supout files)

Low priority problems:
* Client - Charts do not get renewed in real time when viewed.
* Adapt dude link labels to be able to show 10G traffic
speed and larger (snmp part left to fix)

Enhancement requests:
* Add checkbox in dude client loader to allow upgrade/downgrade without prompting
user each time.
* Add option to use functions and oids in notification messages.


"Secure mode" does not work

Re: The Dude, work continues: v6.35rc test builds.

Posted: Wed Feb 03, 2016 3:12 pm
by ste
As The Dude is still in testing stage I suggest moving on to v6.35rc builds for those that experience issues with v6.34 release.


<b>Known issues in v6.35rc1 (reported for fixing):<b/>

<b>All entries below are already confirmed and reported to DEV for fixing.</b>

High priority problems:
* Device discovery tool does not work with Agents.
* Devices behind Agents have problems: link labels with mastering type ROS, ROS login, ROS upgrade
* Some servers still experience issues after latest 6.34rc/6.34 builds (Checking this actively based on info provided by sent in supout files)

Low priority problems:
* Client - Charts do not get renewed in real time when viewed.
* Adapt dude link labels to be able to show 10G traffic
speed and larger (snmp part left to fix)

Enhancement requests:
* Add checkbox in dude client loader to allow upgrade/downgrade without prompting
user each time.
* Add option to use functions and oids in notification messages.


"Secure mode" does not work
Enhancement request:

Use more processes on tilera for snmp/ros query/ping/... operations and give some information/control on query processing

Re: The Dude, work continues: v6.35rc test builds.

Posted: Wed Feb 03, 2016 3:31 pm
by aTan
I've installed the Dude 6.34 on CCR1016 and have imported a db archive (the dude's db file path is on a usb pen drive) with several hundreds devices and several tens of maps. There are some small issues, but the biggest one is the slowness. Each map opens very slowly, some devices doesn't have data (snmp or routeros). There is always only one core at 100% in Resources. And I guess that this is the root of the problem, the Dude doesn't use other cores at all. Until it is fixed, the Dude is usable only on a x86 hardware. It's a shame. CCR could be a perfect replacement for a x86 servers.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Wed Feb 03, 2016 5:37 pm
by krisjanis
"Secure mode" does not work
Please generate supout file on that dude server host and send it to support@mikrotik.com.
Use more processes on tilera for snmp/ros query/ping/... operations and give some information/control on query processing.
It is in DEVs todo list to check how all those processes can be improved.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Wed Feb 03, 2016 5:39 pm
by krisjanis
I've installed the Dude 6.34 on CCR1016 and have imported a db archive (the dude's db file path is on a usb pen drive) with several hundreds devices and several tens of maps. There are some small issues, but the biggest one is the slowness. Each map opens very slowly, some devices doesn't have data (snmp or routeros). There is always only one core at 100% in Resources. And I guess that this is the root of the problem, the Dude doesn't use other cores at all. Until it is fixed, the Dude is usable only on a x86 hardware. It's a shame. CCR could be a perfect replacement for a x86 servers.
Please also generate supout file on dude server device and send it to support@mikrotik.com

Re: The Dude, work continues: v6.35rc test builds.

Posted: Thu Feb 04, 2016 2:20 am
by HiltonT
I know that scanning remote networks via Agents is currently broken (post 6.34RC34), but on 6.35RC3 when I even try an add an Agent, the Agent connects, the Dude Client then disconnects (Error: connection closed) and reconnects and the Agent has been deleted. This happens whether the Agent is trying to connected via 2210 (insecure) or 2211 (secure).

Re: The Dude, work continues: v6.35rc test builds.

Posted: Thu Feb 04, 2016 9:04 am
by rcwmoab
So far so good guys, I'm stoked you started development again, and right as I was considering changing to NetXMS, so bonus points on saving me a whole mess of work although there are some extensibility aspects that could be copied from NetXMS.

One feature request in particular I'd like to put in is the ability to define custom interfaces on a device and have the dude treat it like any other interface and graph bit rates and all that. Specifically I manage a network of 1800 cambium subscriber modules and none of them have an IP address, I can proxy SNMP requests to them through their access points or pull the info off the access point directly so I can get interface counters for the SM and it would be wonderful to be able to place a function that does this on an interface label and have it graph the bitrate like any other interface.

In general I would like to see the dude become more flexible, right now it seems to expect Mikrotik devices and that should be changeable. The SNMP tab for a device is a wonderful concept but woefully underused in my case because only 4 of the tables will populate from Cambium access points. If I could point the tables towards my own snmp values they would provide me with an extremely helpful level of insight into my network all the way down to the customer level. The less fixed functions there are the better, naturally The Dude should ship in a state that works with generic network devices much like it does today but if the user wants they should be able to dig in and change things.

Once again thanks a million for reviving The Dude, I've been using it since I started networking and the thought of getting used to something else was unsettling.

Also for an actual bug report
interface.PNG
I would rank this as a very important issue, and in case there is any question the this I'm referencing is the data loss on interface graphs when the bandwidth gets too high.

I initially thought it was caused by The Dude using 32 bit ifTables to poll interface counters rather than 64 bit ifXTables but after digging a little deeper and creating my own interface graphs using diff64 and ifXTables and still getting the same results I don't think that's the issue. I'm not sure what causes it but if I remember correctly my interface graphs weren't always like this, it happened to them one by one over time. It might also just be an artifact of me monitoring some 350 devices with over a thousand data sources, I'm going to try moving my dude database to a high speed flash array and see what happens.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Thu Feb 04, 2016 11:25 pm
by kmk
Hi

I would like to report a feature request. In RouterOS you can set an SNMP v3 profile with security "private" to use AES as the encryption method. This is not available in The Dude. DES is broken by far, and I'd love to see AES added to The Dude. Keep up the great work!

ROS:
The_Dude_SNMPv3.PNG
The Dude:
RouterOS_SNMPv3.PNG

Re: The Dude, work continues: v6.35rc test builds.

Posted: Fri Feb 05, 2016 3:49 pm
by kolorasta
TheDude 6.35rc5 fails to connect to mikrotik devices. it worked fine in 6.35rc1 to rc4. before that, it failed to connect too.
2016-02-05_10-42-02.jpg

Re: The Dude, work continues: v6.35rc test builds.

Posted: Fri Feb 05, 2016 3:58 pm
by leoktv
I don't have any problems with 6,35rc5 conneting the routers all my are connected to the dute with no problem att all

Re: The Dude, work continues: v6.35rc test builds.

Posted: Fri Feb 05, 2016 4:04 pm
by kolorasta
I restarted the server and it connected to mikrotik devices.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Fri Feb 05, 2016 8:22 pm
by abis
I restarted the server and it connected to mikrotik devices.
Yes, I saw that problem too... sometimes, after I upgrade to the new version, I need to restart The Dude again, and after that the devices report the correct status again... But just sometimes, the last two upgrades I didn't have that problem.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Fri Feb 05, 2016 8:27 pm
by abis
@krisjanis,

1. When the last version of WinBox will be integrated in? I know isn't in the high priority but I think is an easy stuff to do ;)
2. I din't receive an answers about memory probe... for a moment I see just cpu % and disk % or is something what i need to do in functions to can display mem % ?

Thank you.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Fri Feb 05, 2016 10:54 pm
by sacwireless
I am trying on latest stable and release candidate versions of CHR, running on VirtualBox and Amazon AWS, and I can not get an import-db or export-db to work at all. I have a 220MB backup from Dude 4b3 I am trying to import-db into to a CHR, but it just processes with no progress or errors and returns to instantly to the prompt. I get the same with with adding a few devices on fresh Dude install on CHR and export-db does nothing.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Tue Feb 09, 2016 2:20 pm
by simobeliata
Hi all,
I noticed an issue with the syslog: Devices didn't appear with their source addresses. Instead, they are presented with the IP address of the router's interface in the same network with the Dude server.
To be more clear, I have multiple IP addresses on the "LAN" interface of the router without VLANs.
something like this:
[remote RB (192.168.2.1/24)]---(internet)---[main router (192.168.5.1/24;192.168.10.1/24)]---[switch]---(LAN 192.168.5.0/24)---[Dude server 192.168.10.240]
I configured all Mikrotik devices to send syslog messages to the Dude with predefined IP address, but they all appear with address 192.168.10.1
The main router itself is set to send messages with source address 192.168.5.1, but in the syslog it appears with 192.168.10.1

Re: The Dude, work continues: v6.35rc test builds.

Posted: Wed Feb 10, 2016 5:33 pm
by syadnom
I'm still unable to import into v6.35rc7. Fresh backup from a windows dude box. stuck on:
backup-file: bu.tgz
status: applying settings: enabling: reading db object #174
or
status: applying settings: enabling: reading db object #175
same issue, same object numbers.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Thu Feb 11, 2016 12:29 am
by wincdaniel
I've been having an issue since 6.34rcX, continuing into 6.35rc7.
I inherited a Windows The Dude Server (4.0b3), and I've been trying to migrate to a new CHR VM.
I've had no problems importing my old db, but I do run into an issue: None of the custom probes seem to work. I get "parse failed" for them all--even trivial ones.
When I use the very same oid on the object label that's in the probe, it shows up. snmpwalk shows good results as well. I'm not sure if there's something I'm doing wrong, but side-by-side, the old Dude and new Dude give different results.

old dude:
Image

new dude:
Image

snmpwalk:
Image

Little help?

Re: The Dude, work continues: v6.35rc test builds.

Posted: Thu Feb 11, 2016 6:06 pm
by diorges
Can we have a sms/email alert for agent probe? So we will receive on our smartphone alerts if any equipment goes down.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Thu Feb 11, 2016 6:39 pm
by stereomind
Can we have a sms/email alert for agent probe? So we will receive on our smartphone alerts if any equipment goes down.
You can already do that. Create a notification with type "email", and fill in the blanks.
For SMS, you can send email to your provider's email to SMS gateway. You can enable notifications for devices or individual services.

cheers

Re: The Dude, work continues: v6.35rc test builds.

Posted: Sat Feb 13, 2016 10:53 am
by partovi64
HI Dear Friends
Why Delete (note) in outages(services)?!!!!!!!!
We have report by it.
please help me about solve this problem.
OUTAGES.jpg

Re: The Dude, work continues: v6.35rc test builds.

Posted: Sat Feb 13, 2016 7:06 pm
by abstract
Please restore the web interface access, it is very useful to have a smart and rapid access to the network state.

Thank you

Re: The Dude, work continues: v6.35rc test builds.

Posted: Sun Feb 14, 2016 10:46 am
by jdsousa
Hello,

The new Dude will have translation for another language like the old Dude ?

Thanks.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Mon Feb 15, 2016 5:28 am
by HiltonT
My Dude 6.35rc8 is rebooting (CHR in VirtualBox). I'll send the autosupout.rif that was last generated and reference this post.

- HIlton

Re: The Dude, work continues: v6.35rc test builds.

Posted: Mon Feb 15, 2016 7:56 am
by HiltonT
My Dude 6.35rc8 is rebooting (CHR in VirtualBox). I'll send the autosupout.rif that was last generated and reference this post.n
On checking, it seems to rebooting around every 30 minutes or so...

- Hilton

Re: The Dude, work continues: v6.35rc test builds.

Posted: Mon Feb 15, 2016 10:55 am
by vaidehi
Hi,

We have been using Dude Version 3.6 at present which generating graph as shown in right half of below snap which is correct
& with v6.35rc3 graph generated is as shown at left half of snap in which the last 10min graph is showing false details.

Server configurations of chart are as below.
Kindly suggest what can be the misleading error…

Re: The Dude, work continues: v6.35rc test builds.

Posted: Mon Feb 15, 2016 2:01 pm
by vaidehi
I've been having an issue since 6.34rcX, continuing into 6.35rc7.
I inherited a Windows The Dude Server (4.0b3), and I've been trying to migrate to a new CHR VM.
I've had no problems importing my old db, but I do run into an issue: None of the custom probes seem to work. I get "parse failed" for them all--even trivial ones.
When I use the very same oid on the object label that's in the probe, it shows up. snmpwalk shows good results as well. I'm not sure if there's something I'm doing wrong, but side-by-side, the old Dude and new Dude give different results.

old dude:
Image

new dude:
Image

snmpwalk:
Image

Little help?

Hi,

I have similar issue,in v6.535rc8 we get parse failed error while with the same probe I am able to work in version 3.6.
Plz check snap for the same,left-hand side is v6.535rc8 & right-hand side is of v3.6
CPU.JPG
Plz guide...

Regards,
Vaidehi

Re: The Dude, work continues: v6.35rc test builds.

Posted: Tue Feb 16, 2016 10:48 am
by krisjanis
Changes in v6.35rc4 - v6.35rc9

* Fix various server crashes.
* Fix various db import crashes.
* Fix server crash on Agent configuration change.

@sacwireless

Try creating a new CHR from template in Amazon AWS again some issues were corrected there.
If that backup still fails to get imported by server send it to support@mikrotik.com and we will take a look at it locally.

@wincdaniel @vaidehi

We do have some hosts for which some of our servers also show parse failed status. Dev will take a look at that when he gets a chance.

@partovi64

Problem that "Remove Resolved" button is broken in Services, outages tab is known to us.

@HiltonT

That problem should be fixed now.

@jdsousa

At least for now there will be only English language interface for client.

@abstract

Old web interface wont be returned to new builds. Possibly in time we will create new web interface for the Dude.

@syadnom

Some backups files that presented that issue were sent in for checking. That issue is still in DEVs work queue

@kmk

Added your request to enhancement list.

@rcwmoab

I did check the theory with ROS/SNMP link mastering types while running 1G bidi test, I did not experience such issue with graphs.
linkwin.jpg
@simobeliata

Seemed to work in my case.
syslog.jpg

Re: The Dude, work continues: v6.35rc test builds.

Posted: Tue Feb 16, 2016 3:34 pm
by GlueMan
Please add.
In the Dude / Files / Packages / download the packages from Mikrotik pages.

Choice what will default make when double click on device in map (open Winbox, ping or other tool),setting device let him stay where it is now on right click and select on menu.

Thanks

Re: The Dude, work continues: v6.35rc test builds.

Posted: Tue Feb 16, 2016 7:15 pm
by meconiotronic
Hi, I'm experiencing some problem in x86 version 6.34 it seems to work discontinuely. Look:
Dude Timeout.jpg
185.87.240.50 is the dude server
Is not local pinger but server pinger, in winbox there is the same machine containing dude pinging itself same as dude client. Winbox no timeut, dude client yes.

When it is in timeout every change in the client (like move device) etc freezing until the ping starts reply.

I've tryed to install x86version on another machine, no import database but starting a new map, added device une by one and after some time the problem reappears.


Tell me how I can be useful to help you solve the problem

Thanks

Re: The Dude, work continues: v6.35rc test builds.

Posted: Tue Feb 16, 2016 8:49 pm
by pe1chl
When discovering devices, I would like to see a "crawler" type of discovery that walks along neighbors visible
in the MikroTik devices (retrieving info using snmp, winbox etc), rather than pinging whole IP ranges of networks.

Also it would be convenient when the discovery process could be limited to network devices (MikroTik, optionally
others like Ubiquiti, and switches). I would like to use the tool for network device monitoring, and I don't like to have
hundreds of other devices (computers, printers etc) in the view.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Wed Feb 17, 2016 12:16 am
by Inssomniak
I run dude in wine on OSX, and new version presents an error like this: when going to "tools, web", but it still opens safari and works as normal. 6.35rc10

Re: The Dude, work continues: v6.35rc test builds.

Posted: Wed Feb 17, 2016 10:13 am
by HiltonT
Just letting you know that the CHR rebooting issues are most definitely not fixed. Less than 30 minutes and my CHR rebooted here. Again. Running RC10 now. supout.rif sent in response to your last email saying it should now be fixed. ;)

Re: The Dude, work continues: v6.35rc test builds.

Posted: Wed Feb 17, 2016 10:02 pm
by jstump
Feature Request: Under Links - Links, please add a column showing what type of link (found under types tab) so that we can sort by type!

Re: The Dude, work continues: v6.35rc test builds.

Posted: Wed Feb 17, 2016 11:53 pm
by rcwmoab
I finally got my dude database to import, rc11 seems to have fixed whatever was wrong.

Also
One feature request in particular I'd like to put in is the ability to define custom interfaces on a device and have the dude treat it like any other interface and graph bit rates and all that. Specifically I manage a network of 1800 cambium subscriber modules and none of them have an IP address, I can proxy SNMP requests to them through their access points or pull the info off the access point directly so I can get interface counters for the SM and it would be wonderful to be able to place a function that does this on an interface label and have it graph the bitrate like any other interface.

In general I would like to see the dude become more flexible, right now it seems to expect Mikrotik devices and that should be changeable. The SNMP tab for a device is a wonderful concept but woefully underused in my case because only 4 of the tables will populate from Cambium access points. If I could point the tables towards my own snmp values they would provide me with an extremely helpful level of insight into my network all the way down to the customer level. The less fixed functions there are the better, naturally The Dude should ship in a state that works with generic network devices much like it does today but if the user wants they should be able to dig in and change things.
Are you able to pass this request on the the dev, from my perspective it is an absolute necessity.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Thu Feb 18, 2016 11:10 am
by simobeliata
@krisjanis

Thanks for your reply!
I found the cause of the problem - I had a bad masquerade rule on the central point.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Thu Feb 18, 2016 7:30 pm
by abis
Hello, until official fix you can use that "trick" to display the memory probe %
mem_probe.png
"The solution is simply to change "Ram" to "Other", so that the string now says:
iso.org.dod.internet.mgmt.mib-2.host.hrStorage.hrStorageTypes.hrStorageOther
This has to be done in two functions: mem_usage and mem_size. Once this is done, both the Appearance and probe features for memory work."

Thank's to macsrwe http://forum.mikrotik.com/memberlist.ph ... le&u=11740

Re: The Dude, work continues: v6.35rc test builds.

Posted: Sat Feb 20, 2016 7:49 pm
by jarda
How much free space do I need on the disk in relation to dude db file size to make the dude database vacuum?

The dude status messages are very confusing.
In running state I run "vaccuum-db". it tells: "status:running".
Then print command tells: "disabling before vaccuum: stoped".
Thinking I have to stop the dude first. So running "set enabled=no"
Getting status: "failure: vacuuming"
After a while the status is "running" again. checking the db file size - no change.
Stopping the dude "set enabled=no".
Having status "status: applying settings: disabling: stopped". What is it? Is the stopping stopped, or is the stopping in progress? Because dude process has left the profiler, I think the dude was stopped.
Running "vacuum-db" again. The steps are counting. To which number it should count to be sure everything went ok?
After a while the message: "status: vacuuming: failed database or disk is full".

Now the point: dude.db file has 130,5MB. The disk used for dude storage has 247MB of free space. Why it is not enough? How much it should be?

Mikrotik, please, make the manual describing the dude usage in order to correspond to actual situation and covering all messages, commands and their relationship.

Sorry I am writing it again (originally here http://forum.mikrotik.com/viewtopic.php ... 97#p522497 as these notes apply to 6.34.2), but as this thread is referenced in the changelogs, I think it is better to mention it rather here...

And to write something positive/helpful to others too: Like others I had problems with importing the backup.tgz file from 4.b3 to 6.34.2. My solution that worked was to unpack the .tgz file and copy the content into dude store directory of ROS while dude was disabled. After enabling it looks like majority of the things work fine. Just the custom added functions reading oids are reported with problem "parse failed". I do not know what to do with it so far.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Sat Feb 20, 2016 7:52 pm
by jarda
Hello, until official fix you can use that "trick" to display the memory probe %
mem_probe.png
"The solution is simply to change "Ram" to "Other", so that the string now says:
iso.org.dod.internet.mgmt.mib-2.host.hrStorage.hrStorageTypes.hrStorageOther
This has to be done in two functions: mem_usage and mem_size. Once this is done, both the Appearance and probe features for memory work."

Thank's to macsrwe http://forum.mikrotik.com/memberlist.ph ... le&u=11740
This works with mikrotik devices but it breaks memory reading of windows computers, for example. Looks like mikrotik started to use bad oids in the past, maybe.

My solution is following:
Copy the mem_size and mem_usage to new functions called pc_mem_size and pc_mem_usage. Correct the pc_mem_usage to use pc_mem_size instead the original mem_size.
Copy those new functions to ros_mem_size and ros_mem_usage, changing "Ram" to "Other" and linking together like in previous step.
Rewrite the original mem_size:
if(pc_mem_size() > 0, pc_mem_size(), ros_mem_size())
Rewrite the original mem_usage:
if(pc_mem_usage() > 0, pc_mem_usage(), ros_mem_usage())
Now the function cpu_mem_disk and memory probe work correctly with both types of devices.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Sun Feb 21, 2016 3:50 pm
by jarda
Looks like I am spamming here now... but for consideration, this should be taken as feature request for dude:

Allow to reorient the links to other devices without loosing the measured data.

Explanation: Having device A connected to device B. There is also a device C. Now I unplug wire leading to device A from device B and plug into device C. There is no way I can do the same in dude and keep the historical recorded values. Only the way is to create a totally new link and delete the old one, which leads to recorded data loss. I do not want to manipulate with raw database data to get such principal feature.

Are there also other dude users that are missing this possibility?

Re: The Dude, work continues: v6.35rc test builds.

Posted: Sun Feb 21, 2016 6:58 pm
by armandfumal
Hi

Concern import/export DB

I have my 50Mb db from 4.0b3.

I would like to import to 6.35.rc12

I have try to import in cli. the command is accepted but nothing is done. and get Import done but nothing was done...
no errors...

what's wrong

Armand

Re: The Dude, work continues: v6.35rc test builds.

Posted: Sun Feb 21, 2016 7:18 pm
by jarda
Have you tried what I suggested above?

Re: The Dude, work continues: v6.35rc test builds.

Posted: Sun Feb 21, 2016 7:24 pm
by armandfumal
Hi

Concern import/export DB

I have my 50Mb db from 4.0b3.

I would like to import to 6.35.rc12

I have try to import in cli. the command is accepted but nothing is done. and get Import done but nothing was done...
no errors...

what's wrong

Armand
Resolved. sorry I found

Re: The Dude, work continues: v6.35rc test builds.

Posted: Sun Feb 21, 2016 7:28 pm
by jarda
And one other thing. See the picture:
dude-temp-oid.jpg
On top there is temperature oid polled by dude 6.34.2, bottom by dude 4b3 at the same time using SNMPv3 from RB2011. Notice the different value representation.

Whats more, the subsequent function works in 4b3 but not in 6.34.2. The function is defined like oid value:
oid("1.3.6.1.4.1.14988.1.1.3.10.0") / 10
Is there any syntax change or what is the difference?

Re: The Dude, work continues: v6.35rc test builds.

Posted: Sun Feb 21, 2016 11:03 pm
by danayalop
As I can export a backup from an x86 to a tile? I receive this error message when I import both x86 and CHR

Image

Posted: Sun Feb 21, 2016 11:06 pm
by jarda
Disable dude. Unpack tgz file and copy the content directly to the storage. Enable dude.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Tue Feb 23, 2016 10:25 am
by Seema
How about .xml file?I can not import it.Always get "action timed out".The file size is about 150MB.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Tue Feb 23, 2016 1:54 pm
by danayalop
How about .xml file?I can not import it.Always get "action timed out".The file size is about 150MB.
Try copying the contents of folder /dude/data on your routeros server /dude folder. It worked properly

Re: The Dude, work continues: v6.35rc test builds.

Posted: Tue Feb 23, 2016 2:37 pm
by Seema
How about .xml file?I can not import it.Always get "action timed out".The file size is about 150MB.
Try copying the contents of folder /dude/data on your routeros server /dude folder. It worked properly
Sorry for a stupid question but how to access the dude folder on my routeros? :)

Re: The Dude, work continues: v6.35rc test builds.

Posted: Tue Feb 23, 2016 3:10 pm
by jarda
How about .xml file?I can not import it.Always get "action timed out".The file size is about 150MB.
Try copying the contents of folder /dude/data on your routeros server /dude folder. It worked properly
Sorry for a stupid question but how to access the dude folder on my routeros? :)
Use ftp. But the XML file cannot be used because there is db file like in v.4

Re: The Dude, work continues: v6.35rc test builds.

Posted: Tue Feb 23, 2016 4:22 pm
by Seema
Yes,there is a db file already in /dude folder on routeros created by default.I copied contents of data folder to dude folder in routeros,started the server,the server did some processing.After it finished,i started the server, tried to connect but nothing,no luck.Its empty :( :(

Re: The Dude, work continues: v6.35rc test builds.

Posted: Tue Feb 23, 2016 5:43 pm
by danayalop
Yes,there is a db file already in /dude folder on routeros created by default.I copied contents of data folder to dude folder in routeros,started the server,the server did some processing.After it finished,i started the server, tried to connect but nothing,no luck.Its empty :( :(
You must copy the contents of folder /dude/data

Don't copy the exported file

Image

Disable dude server, copy to your default dude folder in routeros and enable dude server

Image

Re: The Dude, work continues: v6.35rc test builds.

Posted: Wed Feb 24, 2016 10:27 am
by Seema
Yes,there is a db file already in /dude folder on routeros created by default.I copied contents of data folder to dude folder in routeros,started the server,the server did some processing.After it finished,i started the server, tried to connect but nothing,no luck.Its empty :( :(
You must copy the contents of folder /dude/data

Don't copy the exported file

Image

Disable dude server, copy to your default dude folder in routeros and enable dude server

Image
I did that first time just as you described.This morning,in my horor,i tried to connect and voala,the dude works.
How,why,i have no clue :) Took him long time to connect tho but it did.Theres a small problem with images and background and some pinging but i believe can manage that.Thank you very much for help and time!

Re: The Dude, work continues: v6.35rc test builds.

Posted: Fri Feb 26, 2016 5:55 pm
by wincdaniel
Changes in v6.35rc4 - v6.35rc9

* Fix various server crashes.
* Fix various db import crashes.
* Fix server crash on Agent configuration change.

@wincdaniel @vaidehi

We do have some hosts for which some of our servers also show parse failed status. Dev will take a look at that when he gets a chance.
Any update on this? Anything I can do to assist? Still exists in v6.34.2/v6.35rc12

Re: The Dude, work continues: v6.35rc test builds.

Posted: Mon Feb 29, 2016 8:39 am
by steven78
I seem to be having issues after the based is imported accessing the dude. The dude seems to be in a boot loop. The import completes ok but then the dude just keeps rebooting.
I can see that main partition just keeps counting down in available space unit it reaches zero thus the dude crashes. I have added an extra 8gb disk under ESXI and formatted. I can see the extra disk and dude folders on the new disk. I think what might be happening is that some files are still been copied to the main partition thus filling it up. Is this a known issue. The database import is only around 100mb.

I have tried both 6.34.2 and 6.35rc12.

Formatting the disk
/disk format-drive 0 file-system=ext3 label=data

Setting the dude database path
/dude set data-directory= /disk1/dude

Importing the data
/dude import-db backup-file=disk1/backup-2016.02.29.tgz

Re: The Dude, work continues: v6.35rc test builds.

Posted: Mon Feb 29, 2016 2:17 pm
by danayalop
Is there any way to clear the graphics files? Due to an error in the date, I have graphics and future outages that I can not delete
Captura.PNG

Re: The Dude, work continues: v6.35rc test builds.

Posted: Thu Mar 03, 2016 10:16 pm
by lebowski
Is there any way to clear the graphics files?
You might have to just delete the probe and put it back on...

In 4.3b if you copied any object the collected data for the original object gets erased before the copy, so on the device that is creating those graphs you should be able to just click copy to clear all the data instead of deleting the probe. Although deleting and putting the probe would probably be better.

I believe the intention was to clear the data before sticking it into the copy buffer but it is clearing the data of the original object. So maybe they could change this as a bug fix. BUT

Back before they stuck the xml data in to a compressed database you could get into the RRD Data and edit it if you viewed the collector in a chart. They should just re-implement this piece of code and let us fix graphs instead of having to delete and re-create the probe or copy the object.

Lebowski

Re: The Dude, work continues: v6.35rc test builds.

Posted: Mon Mar 07, 2016 4:02 am
by HiltonT
G'day Krisjanis,

How is the progress on the Agent issue? Right now, it seems to be stalled. :( Whilst I can now add Agents without The Dude Client crashing and reloading with the added Agent not showing (and therefore not having been saved), there still seems no way to scan a remote network using an Agent. This feature is absolutely essential to have The Dude a useful network tool for monitoring my client networks, not simply their Internet connections.

The Dude is looking rather promising - I just hope development is progressing behind the scenes...

Re: The Dude, work continues: v6.35rc test builds.

Posted: Thu Mar 10, 2016 7:17 pm
by syadnom
I still can't get an import done. I've tried 'import-db' which is failing, and I've tried to copy the dude.db and 'files' directory over and enabling but that just sits in the "status: applying settings: enabling: reading db object #4801" loop.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Tue Mar 15, 2016 8:01 pm
by dnelson
Is there a fix being worked on for the "Remove Resolved" button. I am running 6.34.3. I just migrated from 3.6. Something else I have noticed is that the client has to log back in after sitting for a certain amount of time. This never happened on 3.6. I have the dude running on my monitoring wall all day. several times a day I will go to change maps and the first time I try to do anything it goes back to the login screen and logs back in. Not sure why it is doing this.

Thanks for working on this software again. It is a great product. I have been running the dude for about 5 years now. I show everyone who comes by. It is a great show piece.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Wed Mar 16, 2016 10:38 am
by HiltonT
I have just downloaded 6.35rc in VHDX format, created a Gen 1 VM and tried to install and after the initial Software install portion, all I see is a constantly erroring and rebooting VM with this error message:
6.35rc29-bOrk.png

Re: The Dude, work continues: v6.35rc test builds.

Posted: Wed Mar 16, 2016 1:07 pm
by jarda
Isnt there any write protection/rights problem?

Re: The Dude, work continues: v6.35rc test builds.

Posted: Thu Mar 17, 2016 12:05 am
by HiltonT
Isnt there any write protection/rights problem?
Possibly, but not on my end. :)

It gets through this stage fine, so can clearly write to the VHDX file:
RouterOS 6.35RC bOrk.png
So, I just saw the same issue with the recently released 6.35rc30, so I will do some further testing here, but previous releases worked ferpectly well.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Thu Mar 17, 2016 12:47 am
by HiltonT
I don't have time to play too much right now to see exactly where the issue is, but I have tried 6.35RC29 and also RC30 with the same issue. I just exported and imported an old Hyper-V guest, updated to 6.35rc30 successfully, imported the current Dude database, and all is working fine.

I'll look into this issue some more when I get a chance...

Re: The Dude, work continues: v6.35rc test builds.

Posted: Thu Mar 17, 2016 5:38 pm
by pyjamasam
Not sure if this has been reported yet (I find it hard to keep track of the reported bugs vs fixes in RC versions).

I am seeing incorrect speeds displayed in links (i.e. when I hover over the link in a map and get the popup).

The bulk of my links are listed as 10mbs.
All links are either set to the fast ethernet or gigabit ethernet link types.

This also affects the link colouring (as all the links as though of to be 10mbs then anything over that - which happens all the time because they are in fact 100mbs and 1gbs links causes the links to go red)

I have found one thing though that seems to "fix" the speed displayed. Links that have a mastering type set to SNMP have the seam to have the correct speed displayed (though it might not be right as I look at it. Looks to always be 1gbs no matter what I select for the link type).

Any tips as to how to correct this (of if it is indeed a bug and needs to be submitted via a different channel) please let me know.

Thanks.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Fri Mar 18, 2016 11:03 am
by juanvi
-Solved-

Custom added functions like "ros_command("/caps-man registration-table print count-only")" are reported with problem "parse failed". Working well on Windows dude. (tile 1036 with ros 6.34.3)

Solved with changing "available" and "error" from custom probe with this guide: http://wiki.mikrotik.com/wiki/Getting_s ... and_probes
Before these probes worked well with available=1 and error="" and now need --> available=f3() <> "" and error=if(f3() <> "", "", "down") sytax for working

Re: The Dude, work continues: v6.35rc test builds.

Posted: Mon Mar 21, 2016 12:08 pm
by jarda
How much free space do I need on the disk in relation to dude db file size to make the dude database vacuum?

The dude status messages are very confusing.
In running state I run "vaccuum-db". it tells: "status:running".
Then print command tells: "disabling before vaccuum: stoped".
Thinking I have to stop the dude first. So running "set enabled=no"
Getting status: "failure: vacuuming"
After a while the status is "running" again. checking the db file size - no change.
Stopping the dude "set enabled=no".
Having status "status: applying settings: disabling: stopped". What is it? Is the stopping stopped, or is the stopping in progress? Because dude process has left the profiler, I think the dude was stopped.
Running "vacuum-db" again. The steps are counting. To which number it should count to be sure everything went ok?
After a while the message: "status: vacuuming: failed database or disk is full".

Now the point: dude.db file has 130,5MB. The disk used for dude storage has 247MB of free space. Why it is not enough? How much it should be?

Mikrotik, please, make the manual describing the dude usage in order to correspond to actual situation and covering all messages, commands and their relationship.

Sorry I am writing it again (originally here http://forum.mikrotik.com/viewtopic.php ... 97#p522497 as these notes apply to 6.34.2), but as this thread is referenced in the changelogs, I think it is better to mention it rather here...

And to write something positive/helpful to others too: Like others I had problems with importing the backup.tgz file from 4.b3 to 6.34.2. My solution that worked was to unpack the .tgz file and copy the content into dude store directory of ROS while dude was disabled. After enabling it looks like majority of the things work fine. Just the custom added functions reading oids are reported with problem "parse failed". I do not know what to do with it so far.
Ok, a month has passed and noone has problems with vacuum-db on x86? I have just made an excercise with enlargement of dude storage disk to 2GB with 1964.4 MiB of free space and still having the same error. Now it is on 6.34.3. Removing the dude, wiping the disk, new database copy, nothing helped.

Does it worth to make the same exercise with CHR? Or with latest RC? There is nothing in changelog related to vacuum so I am in doubts.

The displaying graphs or switching between the display periods takes ages, the graph window disappears or reappeares, does not respond and so. The behavior of the tray icon and the icon on the windows taskbar is also not like any other windows application - need to be the last to display the window by clicking on the taskbar icon and so on... Really still far from usable state. It is not still better than 4.0b3.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Mon Mar 21, 2016 3:46 pm
by jarda
6.35rc34, CHR. Importing dude backup occupies "unclassified" process. Should be classified...

Re: The Dude, work continues: v6.35rc test builds.

Posted: Mon Mar 21, 2016 4:28 pm
by jarda
Soo..
I did the last excercise:

1) Run fresh new CHR 6.35rc34 with dude.
2) Mount secondary 2Gb disk drive, set the dude storage there.
3) Import 91MB tgz backup file.
4) Test the dude works with the client - ok (not ideally, but obviously it works).
5) Switch the dude server off.
6) Reboot.
7) vacuum-db. Finished at step over 2.000 with the same error.

But I have noticed important thing:

The vacuum somehow uses primary HDD and while it is exhausted, the process is halted.

Why? It should use the disk dedicated to dude and not any other, especially if noone can estimate there will be enough space on system disk for such operation. At least the error message should clearly state what is the real problem.

Mikrotik, please, take it seriously and use the dude storage by default instead the system drive.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Mon Mar 21, 2016 7:10 pm
by juanvi
Good work but... We need web interface back! If only for watching would be great!

Re: The Dude, work continues: v6.35rc test builds.

Posted: Mon Mar 21, 2016 11:11 pm
by jstump
Can we also change SNMP speeds (and any other spot for this) so I can just enter 100M instead of 100000000...

All those zeroes are tedious!

Re: The Dude, work continues: v6.35rc test builds.

Posted: Tue Mar 22, 2016 4:09 am
by Cronex
Hi all,
i was move my Dude from windows server to MikroTik CCR1016-12G, Dude version 6.34.3.
All is fine, but syslog is not acceptable from devices, look like is not working
Syslog file is created but it's empty.
and after reboot i every time lost the Notification "Syslog", i recreat it and check the message by button "Test" it working.
and MikroTik CCR1016-12G not respond on 514 port. while syslog enable in menu.
in torch i see packets on 514 port from devices to mikrotik
NAT and Firewall filter not block the 514 port


on windows version of Dude it work fine

model CCR1016-12G
version ROS 6.34.3
firmware 3.27
serial 468702110059

Re: The Dude, work continues: v6.35rc test builds.

Posted: Tue Mar 22, 2016 8:25 am
by Cronex
And at additional : agrigation link from Thecus N4200PRO showing speed as 10 Mbps instead 2Gbps

Re: The Dude, work continues: v6.35rc test builds.

Posted: Tue Mar 22, 2016 5:00 pm
by julianeble
It would be great to add the feature to add more links to a map, an example is if I have a port channel to a map and want to monitor the ports separately.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Tue Mar 29, 2016 3:09 am
by HiltonT
I don't have time to play too much right now to see exactly where the issue is, but I have tried 6.35RC29 and also RC30 with the same issue. I just exported and imported an old Hyper-V guest, updated to 6.35rc30 successfully, imported the current Dude database, and all is working fine.

I'll look into this issue some more when I get a chance...
This issue has been completely resolved in (at least) RC42, maybe earlier.

Still no Hyper-V Gen 2 support, though, so I don't quite understand the Changelog in 6.35RC that says support for Hyper-V SCSI Booting has been added - Gen 1 cannot boot SCSI (not possible) and Gen 2 must boot SCSI (no IDE controllers anymore).

Re: The Dude, work continues: v6.35rc test builds.

Posted: Tue Mar 29, 2016 3:13 am
by HiltonT
Can we also change SNMP speeds (and any other spot for this) so I can just enter 100M instead of 100000000...

All those zeroes are tedious!
+1

Re: The Dude, work continues: v6.35rc test builds.

Posted: Tue Mar 29, 2016 3:14 am
by HiltonT
It would be great to add the feature to add more links to a map, an example is if I have a port channel to a map and want to monitor the ports separately.
+1

I came across the same issue the other day...

Re: The Dude, work continues: v6.35rc test builds.

Posted: Tue Mar 29, 2016 3:15 am
by HiltonT
G'day Krisjanis,

How is the progress on the Agent issue? Right now, it seems to be stalled. :( Whilst I can now add Agents without The Dude Client crashing and reloading with the added Agent not showing (and therefore not having been saved), there still seems no way to scan a remote network using an Agent. This feature is absolutely essential to have The Dude a useful network tool for monitoring my client networks, not simply their Internet connections.

The Dude is looking rather promising - I just hope development is progressing behind the scenes...
Bump...

Re: The Dude, work continues: v6.35rc test builds.

Posted: Thu Mar 31, 2016 7:37 am
by Cronex
Hi all,
i was move my Dude from windows server to MikroTik CCR1016-12G, Dude version 6.34.3.
All is fine, but syslog is not acceptable from devices, look like is not working
Syslog file is created but it's empty.
and after reboot i every time lost the Notification "Syslog", i recreat it and check the message by button "Test" it working.
and MikroTik CCR1016-12G not respond on 514 port. while syslog enable in menu.
in torch i see packets on 514 port from devices to mikrotik
NAT and Firewall filter not block the 514 port


on windows version of Dude it work fine

model CCR1016-12G
version ROS 6.34.3
firmware 3.27
serial 468702110059
Thanx - resolved in 6.34.4

Re: The Dude, work continues: v6.35rc test builds.

Posted: Fri Apr 01, 2016 1:07 pm
by wa4zlw
Hey guys....

Can you please make a change to the CHANGELOG?

Please add a date/timestamp, plus the version # for that date/timestamp) for each change? At a minimum a date/timestamp.

THis gives everyone a more clear idea of what was fixed when, etc.

Thanks leon

Re: The Dude, work continues: v6.35rc test builds.

Posted: Fri Apr 08, 2016 3:58 pm
by diasem
Feature request:
Under notification -> Run on server set to run commands direct on mikrotik like:
/tool fetch address=192.168.88.2

Re: The Dude, work continues: v6.35rc test builds.

Posted: Fri Apr 08, 2016 5:32 pm
by benjamimgois
I am running 6.35rc48 and sometimes the graphs doen´t load... Anyone else with the same problem ??

Image

Re: The Dude, work continues: v6.35rc test builds.

Posted: Fri Apr 08, 2016 6:12 pm
by juanvi
Stopped graphing once during some hours but with older rc. No know why. Now graphing without problems with 6.34.4

Re: The Dude, work continues: v6.35rc test builds.

Posted: Fri Apr 08, 2016 11:31 pm
by Basdno
The HD on the x86 system I run my ROS DUDE server on crashed today, and i feard i would have to struggle with moving the backup(Luckily I have standard regular routine of backup! ) over to the new DUDE.

So I put a SD card into an idle CCR1009 that I hadnt put into production yet to be sure I had enough storage(CCR was to replace an older RB, but that can luckily wait), and then a bit anxious I loaded the ROS6.35rc48 and corresponding DUDE package onto the CCR and rebooted.

When upgraded I uploaded my backup from the old DUDE, and typed import-db, following a couple of minutes of nailbiting while the database got imported.

Meanwhile I downloaded new client, and when it was done I filled in my credentials, and............... Voila my beloved DUDE emerges again from the dead on the new platform! :D

That was a moment of relief!!! :lol:

This was only a few mins ago, so I havent been able to test out all aspects yet, but on a quick first glance and bit of testing all seems to work as usual!

I am amazed how nice and smooth that worked out!

So my point? :

THANK YOU VERY MUCH MIKROTIK for bringing THE (AWSOME) DUDE back to life again, and making transition so painless!!! Even between system types! 8)

Keep up the good work!

Cheers

Re: The Dude, work continues: v6.35rc test builds.

Posted: Sat Apr 09, 2016 2:02 am
by HiltonT
Hey guys....

Can you please make a change to the CHANGELOG?

Please add a date/timestamp, plus the version # for that date/timestamp) for each change? At a minimum a date/timestamp.

THis gives everyone a more clear idea of what was fixed when, etc.

Thanks leon
Oh.

Hell.

Yes!

Re: The Dude, work continues: v6.35rc test builds.

Posted: Sat Apr 09, 2016 2:06 am
by HiltonT
The HD on the x86 system I run my ROS DUDE server on crashed today, and i feard i would have to struggle with moving the backup(Luckily I have standard regular routine of backup! ) over to the new DUDE.

...

Meanwhile I downloaded new client, and when it was done I filled in my credentials, and............... Voila my beloved DUDE emerges again from the dead on the new platform! :D

...

I am amazed how nice and smooth that worked out!

So my point? :

THANK YOU VERY MUCH MIKROTIK for bringing THE (AWSOME) DUDE back to life again, and making transition so painless!!! Even between system types! 8)

Keep up the good work!

Cheers
Yes, I *do* like The Dude and really am glad that dev is once again happening with it. It has a lot of potential if things like the Agent issue (that I reported and asked again about just above) is addressed and progress keeps being made. An awesome little tool it is, for sure (potentially). :)

Re: The Dude, work continues: v6.35rc test builds.

Posted: Mon Apr 11, 2016 5:32 pm
by mysz0n
I would be great if there were an option to send alerts/notifications as an HTTP request.
A similar solution is used in Multiping - works great.
or
add the ability to poll a xml file which contains the current device status

This would create the opportunity to create my own solutions based on the dude.
and save me a lot of time that I spend on network monitoring...

Please, consider adding such requests to the TODO list

Re: The Dude, work continues: v6.35rc test builds.

Posted: Tue Apr 19, 2016 9:54 pm
by jstump
Any plans to implement auto backup for device configs to the Dude server? Considering third party applications like Back-It-Up, but would prefer to have this in the Dude as well.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Tue Apr 19, 2016 9:55 pm
by jstump
It would be great to add the feature to add more links to a map, an example is if I have a port channel to a map and want to monitor the ports separately.
+1

I came across the same issue the other day...
Agreed. Would love the ability to have multiple links between devices.

Re: The Dude, work continues: v6.35rc test builds.

Posted: Sat Apr 30, 2016 12:28 am
by kmk
Hi

Sorry for posting on this old thread, but could you please make a similar thread for the 6.36rc? Having a single place to track progress and request features is awsome!

Regards
Karl

Re: The Dude, work continues: v6.35rc test builds.

Posted: Mon May 02, 2016 5:45 pm
by nemke
Any plan in future to support The Dude server for RB1100AHx2 ?
I see that is supported, and will be supporter for ARM (RB3011). So my thinking is, RB1100AHx2 is stronger, so why not supporter dude also :-)

Thank you

Posted: Mon May 02, 2016 6:33 pm
by jarda
There is no support for arm currently. Only chr, x86 and tilera are supported for now.

Re:

Posted: Mon May 02, 2016 9:34 pm
by nemke
There is no support for arm currently. Only chr, x86 and tilera are supported for now.
In 6.36rc10 it is :-)

Posted: Mon May 02, 2016 11:05 pm
by jarda
Oh. Really? Another miracle...

Re: The Dude, work continues: v6.35rc test builds.

Posted: Thu May 05, 2016 12:07 pm
by krisjanis