Now the dude client is unable to connect to the server. I see “Error: Connect failed: 10061: No connection could be made becaus…”
+1 v6.34rc45
After two hours I restarted my dude server, it starts running.
In winbox, I enabled logging for debug, then I see these entries repeatedly in log:
12:43:47 ssh,debug,packet sending string
12:43:47 ssh,debug,packet SSH-2.0-ROSSSH\r
12:43:47 ssh,debug,packet
12:43:47 ssh,debug closing connection: ::ffff:xx.xx.xx.xx:49546 (4)
where xx:xx:xx:xx is the IP address of my dude server.
After I disabled “secure mode” for my dude server, I still get these entries. I do have many objects in my network that still have secure mode enabled though.
Hi!
Does anyone else experience lag problems with new Dude server?
I have 1000 devices in Dude and it’s very CPU intensive on CHR. One core goes up to 100% and than Dude client freezes. I’m trying it on Hyper-V VM with 4 cores and enough memory. On that config I was running Windows server with Dude and lots of services without problems.
Refreshing of devices is gone, I must manually click reconnect to get interface data.
Windows or Linux server version would be better. At least until you made Dude multi-threaded.
Another thing is usage of remote database server. Collecting and using lots of data on CCR/CHR storage isn’t something I wan’t to do. I want database on separate server, backup and multi RouterOS connection to it.
And API of course ![]()
Lag = yes!
My dude server runs in a Celeron box with a separate HDD for the dude database. It worked well with rc3x. I noticed that the lag start with version rc41. From Tools => Graphing, my CPU graph shows much more intensity after rc41.
Also, memory usage has been all over the place.
More of a feature request, posting here for lack of a more suitable topic.
On a single device you can add more ip addresses, but the services probe the first ip and this is used to show if the service is up or down. Can we have the probes check all ip addresses and the service is considered up or down depending on a switch so we can choose - 1 ip down - service down (and), all ip down - service down (or).
When I updated from 6.34rc45 to 6.34 final after reboot Dude was not working. It was :
[admin@Dude] > dude print
enabled: no
I had to do :
dude set enabled=yes
6.34 version is released!
http://forum.mikrotik.com/t/v6-34-current-is-released/94910/1
v6.35rc build topic
http://forum.mikrotik.com/viewtopic.php?f=8&t=104395


