rb600 runnig the dude server BUG (ROS 3.3)

RouterOS The Dude
1

I’m not quite sure if anyone else has the seen this. But my dude server (running on RB600 ROS 3.3) cannot monitor any routeros devices.

Under device Settings I imput correct username & password but server is unable to cennect to remote (in the same subnet) ROS device neither using Winbox nor simply from server itself.

I must add that when I’m using Dude Server running on Windows PC everythng works fine.

Any ideas guys???

2

I’m getting the same problem running Dude server on RB411 with ROS3.3.
The Dude server doesn’t seem to make RouterOS connections. Here’s what I get when I try to configure a link:

  1. Is there a setting in Dude server that needs to be switched on?
    or
  2. Is RouterOS Dude server not set up to do RouterOS functions?

Next question:
Does Dude server on RouterOS save history when power is cycled?

Next question:
I exported a Dude Server/PC configuration, and tried to import it to Dude server ROS. I couldn’t get anything to work. Is there a compatibility issue in the configuration file?

3

I have the same problem running the ROS3.3 on a RB1000, monitoring a pure Mikrotik environment. I can get any info on link with RouterOS or SMTP
and in the logs of the APs, I see the failed, login from the RB1000.

Any help would be great, it is great to run dude on a routerboard, but not so good, when we cant see speeds and other things.

4

Is there no one who can help with this isue??

5

I can confirm this.
RB600 ROS3.6 runniung dude Server.
→ not able to select network Interface to be monitored by snmp.

matong

6

Great, at least we know that this problem is common. I still haven’t found any way to solve this. I’ll try to upgrade to ROS 3.7, but I believe it won’t help, because even thou ROS version is different, dude server in package has not been changed
(only package version number has changed).