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.
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.
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.
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).
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.
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