That is why I am using dude 6.46.6... :-) I just have forgotten the original reason, because otherwise I would not use such "new" version.What's new in 6.47 (2020-Jun-02 07:38):
- The Dude server must be updated to monitor v6.46.4 and v6.47beta30+ RouterOS type devices.
- The Dude client must be manually upgraded after upgrading The Dude server.
- The Dude requires "winbox" policy instead of "dude" to monitor v6.46.4 and v6.47beta30+ RouterOS type devices.
dude vacuum-db ; dude export-db disk1/dude-backup-9999-99-99.tgz
I am interested in how your CHR on 6.46.6 is working stable, we have been unable to get a CHR to work above 6.46.3 (6.46.4 where everything changed)So I did a test for you. Upgraded one of disposable devices in my lab to 6.47.2 (RB333 model, PowerPC architecture).
The result in 6.46.6 Dude:
RB333 v-6-47-2 in 6-46-6 Dude.JPG
It is accessed both the winbox and SNMPv3 protocols without any problems from dude.
Can you explain special user? We have our Ros devices winbox connectingI am not using invoking winbox from dude because I use special user with lowered rights for the the dude monitoring. Such user would be useless in winbox... And it works good without any obvious problems.
Dude is also accepting syslog messages from the devices and store them as expected.
I upgraded dude manytimes, my oldest recorded data are from 2014 or even maybe 2012.
Now I don't see any unusual problems with 6.46.6. Only those that are known for ages...
Oh, i didnt realize that is what you ment. That is how we are setup as wellThere is additional custom user group with passive rights and dude connects by user which is member of that group. Dude is not connecting with admin rights to the devices.