The iptables solution doesn't apply to Mikrotik equipment since they don't run Linux.
The Mikrotik Neighbor Discovery Protocol (MNDP) is enabled by default on newly created IPIP interfaces. And since there is such an interface for each mesh partner, they are probable programatically generated by a script. So the correction has to be be done in that script, to explicitly disable MNDP for each newly created interface.
But really, isn't this a kind of overreaction to one 149 bytes long packet every minute?
Marius, YO2LOJ
-----Original Message----- ...
Maybe we should recommend some outbound firewalling for such known nuisances?
To reduce traffic, drop neighbor discovery and smb as well as MikroTik Neighbor Discovery Protocol on tunl0 (optional, but a good idea):
iptables -A OUTPUT -o tunl0 -p udp --dport 10001 -j DROP iptables -A OUTPUT -o tunl0 -p udp --dport 137:139 -j DROP iptables -A OUTPUT -o tunl0 -p udp --dport 5678 -j DROP