I’m sure most of what I listed will eventually be implemented.

After letting RouterOS languish for a decade, they’re getting back on track and it’s looking very promising. I’ve made numerous suggestions over the years and I have to give credit where credit is due. This is just the stuff I can think of off the top of my head. I’ve been using RouterOS for a long damn time (since version 3, IIRC). Netwatch tool has no knob for handling flapping I won’t hold this one against them though. No EIGRP (yes, there are use-cases for this the protocol has been open source). Scripting language lacks types (ie there should be types and methods for handling IP addresses as IP addresses and not strings (so I don’t have to write an insane amount of regex or rely on someone else’s library to do it) No commit/rollback (like JunOS or IOS XR) semantics in the CLI or APIĬAKE support is a mess.

Please use what is becoming de-facto standard I’ll probably end up having to write a YANG adapter for myself) No YANG configuration modeling (yes I know they have a REST API now no, I don’t care.

No iOAM (it’s in the mainline Linux kernel, even!) I’ll just give you the list of stuff I’ve asked them for or wished for.

Mikrotik routeros vpm setup