Using Dude with many devices in differnet maps creates issue where it is hard to identify a device in dude with wrong or no password entered.
This is causing repetitive errors in the device log and damaging NAND as this is erorr/critical type of logging event.
In order to ease identifying of the local ip to which multihomed/multi-IP devices recieve this dude request, it would be good to add local IP to the log.
For example instead of recieveing this in the log:
09:47:03 echo: system,error,critical login failure for user admin from x.x.x.x via winbox
09:48:02 echo: system,error,critical login failure for user admin from x.x.x.x via winbox
09:49:08 echo: system,error,critical login failure for user admin from x.x.x.x via winbox
09:50:18 echo: system,error,critical login failure for user admin from x.x.x.x via winbox
…
for it to contain the following
09:47:03 echo: system,error,critical login failure for user admin from x.x.x.x via winbox to the local IP y.y.y.y
09:48:02 echo: system,error,critical login failure for user admin from x.x.x.x via winbox to the local IP y.y.y.y
09:49:08 echo: system,error,critical login failure for user admin from x.x.x.x via winbox to the local IP y.y.y.y
09:50:18 echo: system,error,critical login failure for user admin from x.x.x.x via winbox to the local IP y.y.y.y
…
and similar for IPV6.
Otherwise Dude ipscans regularly add mikrotik IPs from different subnets with the no/wrong password on the maps and this issue reappears easily.
Thanks