Dude 6.46.5 does not keep winbox connection alive. It floods logs of all ROS devices on network with connect / disconnect message. Cca every minute Dude connect and disconnects to devices, which are marked as RouterOS. I did not see this behavior prior 6.46 version
Does this problem have somebody else please?

Mine does the same, all logs are flooded

We have the same problem. ROS 6.47.

I believe it's because of the "label refresh interval" in dude.

I've tried to remove all ROS output on labels, but no effect.

we have the same since we have upgraded to 6.47.1.

seems Dude change the way to communicate with monitored device. It login, collect data and then close...

the monitord device has now polution about login/logout....

Hi,

Any news about this topic ? Tried many settings but dude continues to disconnect/reconnect to devices.

Best Regards

Anybody that can shed a light on this issue. All my logs are filled with logins and log outs now.
On top of that, I have also many login failures from "admin" with the same IP address (the Dude) as the successful logins.
But this administrator "admin" doesn't exist in my network. I tried all possible Dude settings, pollings, services etc. that could try to access router with this "admin" but I can't find it.
It happens network wide.

It drives me nuts. Not only are all my router's logs useless, only login and outs attempts succeed and not.. I even see in the log of the Dude itself some "admin" tries to login... how's that? It's all ROS (mine is running 6.47.7) on CHR but since when can a ROS device try to login to itself? And gets denied? (because it is an admin that is not in the admin list...?)

Drives me nuts. Asked around with many but nobody seems to know....

Our logs are also insanelly flooded after upgrade to 6.47.. You can't really find anything historical and useful there anymore.. only thousand or so login/logout entries.
I'm surprised how MikroTik has this ability tu ruin things for yeeeeears now :)

Downgrade....6.45.9 From march 2020 last good for dude.

Yes, I already did that.. All the graphs are with saw-like spikes :) Completely useless... This is graph for 100M link: I don't feel anything in 6.47.x. I thought it will solve this issue: But it didn't.. Everything >3Gbps in Dude graphs looks like this :)

I confirm, 6.45.9 is the last stable version for Dude.
With newer versions Dude server doesn't keep connections, doing login/logout on polling intervals.
If monitored ROS device is located in remote area with poor connection (big latency), Dude is not able to establish connection (hangs on status "connecting", and never falls back to "timeout"). So no automatic retry occurs.
Toggling "secure mode" in device setting doesn't help.

I’m also on that version. Indeed no reconnects every half a minute, everything else works fine too. I have currently set label refresh time to 0:08, and that graph successfuly displays everything up to 5Gbps. Didn’t try custom probes yet. I’ve heard there are success stories with 64bit counters.

I am on dude 6.47.8 without any problems ...
(Max connection speed is 1GB/s here)

just my 2c

I am on dude 6.47.8 without any problems ...
(Max connection speed is 1GB/s here)

just my 2c

Than try run dude on multi-core CCR. No old single core MIPS.

dude is running on a dedicated RB750Gr3 which has a 4-core cpu ...

dude is running on a dedicated RB750Gr3 which has a 4-core cpu ...

Good news works with MMIPS 4 Threads. NO 4 core https://mikrotik.com/product/RB750Gr3.
Are u 100% sure monitoring any mikrotik device ? No snmp just ROS protocol ?

my RB750Gr3 says cpu-count 4 ... I am monitoring all my MT devices with both ROS monitoring and SNMP ...