In our system, if I make a tools-ping on a non ROS device, the device writes authentication failure-s in their log file. I have noticed this in several type of devices. I think it’s only since we upgraded to 3beta8 (not sure maybe it is from 3beta7 too).
So the question: What is doing dude when I make a tools-ping, any else than pinging the device?
Thanks
Anybody?
Mikrotik guys/girls? 
Isn’t that for PING FROM device?
No.
I ping it from server.
For example this is an APC Smart 3300 UPS:
One ping makes this nine log entries.
The SNMP read community is good (I display runtime and input voltage in Dude, and that works correctly)
After spending a whole day with testing, downgrading, upgradeing, packet monitoring I found the reason.
When I make Tools-ping or Tools-traceroute in Dude, the dude makes an SNMP request for the SysName to show it in the Name field of the ping/traceroute window. But: The dude tries ALL of the SNMP profiles on the devices, which is set in the Settings-SNMP page. Even if the SNMP is set to no-snmp on the device.
Maybe the solution will be (in the next version:)): determine the sys name from the Name field of the device page, or try request it on SNMP only with the community set by the profile.
This problem obtains is 3b7 and 3b8 too.
thanks for the report, i will forward it to the people involved