MNDP is broadcast so visible to everything within the layer 2 network, it doesn't provide information as to where it is within the network. I see. If I'd want to see these packets using tcpdump, which filter would I need to apply? Or, put differently, where can I read the network definition of MNDP...

First, let me repeat part of what I said, in case some readers might have missed it: I have MNDP enabled on all SwOS devices. I do not have any ROS devices. Which means: I do not have RouterOS, on some devices by choice, on most devices because they are of the CSS variety which is not capable of run...

As for doing automated advanced management without a CLI, there might be two ways:

As I just figured out, there actually is a third way:
c. Through the Javascript API that the web management console of SwOS already uses.

You mean link this? MTU in RouterOS

Yes, exactly like that.
The only odd thing here is that it is buried inside the RouterOS documentation, but is not referenced from the SwitchOS docs, and neither from the specs of the individual products.

I have MNDP enabled on all SwOS devices. I do not have any ROS devices. Inquiring minds would like to know: - How can I see what MNDP actually discovers (I'm trying to get a switch topology map out of this)? - How hard would it be to support LLDP as well? - Is it somehow possible to see what RSTP tr...

It's something close to two seconds, I believe.

The ONLY thing needed here is a statement from Mikrotik regarding the maximum MTU physically supported by the switch-chip hardware in various devices.

Would it be too much to ask for Mikrotik support to step in here and share some thoughts on this?

Actually, SwOS already has an API. All we need is documentation for it (or reverse engineer it). To wit: URL: /link.b The Authorization header uses a token to keep the session going. The payload appears to be JSON (with a misleading text/plain MIME-type). In that JSON payload I can already recognise...

The argument against https support, I support: just keep your config access on a VLAN that is secure, then http is fine. The argument to upgrade to ROS I do not support: not all devices are capable of that. As for doing automated advanced management without a CLI, there might be two ways: a. Through...

I do not know the answer (though I'm guessing that it's the version that's pre-installed piggy-backed on RouterOS or something).
What I do know, is that I actually pressed "Upgrade" there, and then it upgraded to v2.13 (without the p).

Would adding a capability to log remotely via UDP to a syslog daemon be too much to ask in SwOS?
I.e. I'd settle for entering the IP address of the loghost, and possibly requiring it is accessible through an ARP request.