Dude just not graphs itself

[mooteel]

Hmm…
Absolutely not sure here, but wouldn’t it be more secure, or more precise to just include the loopback interface (lo) to the LAN list?
I believe this is the interface that would be used to monitor itself.
When I did, it started monitoring right away…

@RadAPl

I don’t think this is your problem but I have discovered a very similar issue where the host Dude server can’t monitor itself. You also see many login attempts from itself. I discovered a firewall rule to block access from interfaces not in the LAN list was the problem -

/interface list member
add comment=defconf interface=bridge list=LAN
add comment=defconf interface=ether1 list=WAN
/ip firewall filter
add action=drop chain=input comment="defconf: drop all not coming from LAN"  in-interface-list=!LAN

If I changed the !LAN to WAN the Dude could monitor itself.