The Dude, v6.36rc test builds.

RouterOS The Dude
1

As The Dude is still in testing stage I suggest moving on to v6.36rc builds for those who experience issues with previous builds.

Known issues in v6.36rc39(reported for fixing):

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

Higher priority problems:

  • …
    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;
  • Add new notification method that allows to use ROS tool sms.
2

Changes in v6.36rc11 and prior v6.36rc builds:

*) arm - added Dude server support;
*) Fixed - Client crash on version upgrade, if client had previously already connected to some server;
*) Fixed - Various server crashes. Reported in following support tickets:
2016031666000464, 2016032366000987, 2016033066001025, 2016032266000283

3

Hi

Thank you for bringing The Dude back to active develpment, it is an awsome tool!

Now to my feature request. I have two RouterOS devices behind a CPE in the following setup:

CPE: 203.0.113.200 (and 192.168.88.1 on the LAN side)
hAPac01: 192.168.88.11
hAPac02: 192.168.88.12

Now I do a port-forward on the CPE so I get:
203.0.113.200:8292 → 192.168.11:8291
203.0.113.200:8293 → 192.168.12:8291

Now I want to add three devices in The Dude, monitored as RouterOS devices, but I am unable to add more than one device (the CPE) as there are no way of specifying what port The Dude should use to connect.

Could you please implement a feature so that we get the option to specify what port to connect to? I know this brings with it a lot of complications with regards to ping and so forth, but would another option be to specify a sub-device? Then you’ll know that it is behind the other device, and only reachable on port xxxx or zzzz?

4

Good day,
i began to test new dude on ccr 1036, so far i see when i restart (dude or all ROS) snmpv3 passwords are gone (private, md5,des), i have manually write them again, mmm maybe a little slow when i login… same behavior on 6,34,4 and 6,35,1

5

@kmk

This problem was originally intended to be avoided by using Dude agents in those remote networks. Somehow I don’t think that such option will get implemented. I haven’t seen many NMS that allow this kind of option.

@Percanta

Tried on one of my test server. In there snmp profile info didn’t seem to go missing. Is that the only section where your dude server loses configuration?

6

Good day

i was doing some test and passwords arent losing but i have to push button “apply” on snmp profile window, i tried to wait if maybe some delay after reboot but 3 hours and nothing change, i have to push “apply”. there are password but its not applied …
i have 2 ccr 1036 and same result, the config came from 4beta3. another things work good.
regards

7

Feature request: syslogging to have severity levels

Got my mikros sending remote syslog to dude at info level. Gets very spammy looking at syslog in the dude when i can’t filter on severity

8

@Percanta

How I tried it:

  • Created new snmp profile on dude server.
  • Rebooted server host.
  • Reconnected with client.
  • Tried to run snmpwalk on some device with v3 private snmp profile.

First try failed but on second try device seems to answer without issues.

@craigroser

Possibly we could add that filter, after some syslog section reworks that are planned.

9

Good news!
Btw, it will be so nice to can use hostnames for devices, not just IP addresses, because in that way we can add devices what are use DDNS (for example your IP-Cloud future), when IP Address is changes on the device…

Happy to hear news from you guys! :smiley:

10

Search RB or other devices, does not work in SUBMAP
Search only works in SUBMAP

on version 3.6 works OK

11

Any ETA when " * Add new notification method that allows to use ROS tool sms." will be available in RC builds?

12

Changes in v6.36rc13 and prior v6.36rc builds:

*) Functions - Optimizations/Rework (work in progress) mostly background changes.


@abis

DNS name usage for SNMP servers has already been reported as feature request.

@autostoper76

Which exact filter/search option do you mean?

@padrecc

No ETA on that feature yet.

13

Main reason we wait to use the new Dude. We’re running the old Dude on a PC with UPS and UMTS-Stick so we get alarmed even when the whole Network/Power goes down. This cant be done with SMS Providers as there are a lot of components need to work to send the SMS.

14

Any word on adding SNMP Trap capability?

15

Please upgrade the embedded version of Winbox to 3.4 in the Dude.

16

+1 for snmp trap functionality

17

Thanks for continuing to develop DUDE

Question, I’m finding that DUDE on multicore routers runs only a single core at 100% - even with MultiCPU checked - tired on various models.

Anyone have a solution ?

18

Changes in v6.36rc16:

*) Refactored functions (background changes).
*) fixed - Various memory leaks.
*) fixed - 100% load on one cpu core by dude process on server startup in some cases.
*) The Dude admins now rely on ROS users. User requires dude policy to connect to server.
*) The Dude now uses ROS log. Requires dude topic to be added in log rules.
*) Removed data based commit interval change option in server settings.
*) Added comment option for servers in client loader window.

Notes:

  • Old logs will not be transferred to new log.
  • Log viewing option will at some point be returned in client.
19

@ScottReed @nimbo78

SNMP trap receiver just in feature requests stage.

@themenace

Sounds like one of the bugs that should be fixed in latest build.

20

Folks,

I do not know if I’m going blind, but I see any more mib, image, … let alone upload any file. What is going on?

Regards,

Vagner Felipe Becker