5 Nov
2018
5 Nov
'18
3:54 a.m.
Possibly a router not having updated the script to 3.2
after upgrade to
ROS 6.41 and later.
Yes, that would be the reason for sending MNDP broadcasts.
Actually I don't mind that those are sent, it can be useful as it provides the info
I gave in the first post. But of course it would be nice when system->identity is
changed e.g. to the callsign so it is easier to contact people when something is wrong.
However, the main issue is that it is using a public IP that is not in the gateway list
so these packets cause a log message and are dropped here.
Likely the public IP has changed without the owner noticing it or without him realizing
that he needs to update the portal entry.
(of course this can be avoided when using a DNS name in the portal and some dynamic DNS
update script, or even simply "IP Cloud" when this MikroTik is directly in the
public IP)
Rob