Hello everyone, first of all sorry about my bad english
Here my actual problem, I use a CCR1036-12G-4S in the v6.45.5 exclusively to running the dude. After a while the routerOS just stop accepting connection, Dude/winbox/ssh all return connection refused but the mikrotik still ping without problem and i think its running just denying any type of connection.
Someone have some clue about that?
Thanks in forward and best regards
We just updated all our dudes as well to the 6.46.4 with the same issues. Cant see past the CCR with the same os version. was working correctly with 6.45 X versions
Have the same issue here, all devices updated to 6.46.4 and can no longer access devices behind a unit via The Dude.
getting error
std failure: not allowed (9), next attempt at 11:15:35
Just upgraded Dude to 6.47beta35
we are seeing std failure: not allowed (9), next attempt at 08:48:02
We have upgraded our routers to 6.46.4
Just had another look at this problem and it looks like the user groups are broken. we have the option for “DUDE” ticked but for it to work we also need “winbox”
Getting the same. After upgrade to 6.46.4 things seemed to work fine. Then I started noticing spikes in graphs up to 2 gig on a 1 gig interface. Then the log file had issues with timeout process 20. Rebooted. No fix. Export DB to backup and save off line. dude db is at 2 gig. Backup at 700 mb. Cleanned db. Changed server settings to collect less historic data. Clean DB.
Now in Devices - it has connected to all devices monitored, but they disappear, then re-appear. Isn’t working right. Others seem to have better luck running in on CHR in VM. Maybe I’ll try that since the 1100 AH designed to run the dude doesn’t seem to be stable.
MIKROTIK - PLEASE HELP!!!
– Edit - After this post I began further digging. - Set LABEL refresh from 1 minute to 5 minutes. This seemed to help as well. Maybe there are just too many requests with 300 devices for this to function properly.
On my Dude I had the same problem that Gabriel experienced, the difference is I have the Dude on a CHR. I had to make a copy of the CHR and the Dude db and then create a new CHR. After this is working fine with well over 500 devices.
@andyhenckel - I would recommend a virtual version, you can upgrade specs as needed.
Problem is with DUDE on actual devices is that SD-card access is slow, very slow. USB is slow as well.
The best platform for DUDE is CHR.