I actually just miss one "feature" in RouterOS 5/6 and it would be awesome to have this in 7: IPv6!
The current state of IPv6 in RouterOS 6 is maybe partly usable for home users, soho applications, etc. But in no way is it safe or depending on the configuration even possible to use MirkoTik for service provider applications with more than one router.
The reason I put feature in "" is because you cannot name it feature when they officially support ipv6 and 50% of all protocols and services are not or only partly working for ipv6, then those are bugs!
Just to name some missing "features" / bugs in IPv6.
- IPv6 bgp recursive next-hop. This is a must for any redundant IPv6 service provider backbone! static routes are no alternative!
- ipv6 blackholing - there must be a way to blackhole the prefix I announce to my upstreams. I simply don't want any TTL exceeded and routing loops! unreachable routes are no alternative!
- efficient ipv6 routing table lookups on cli (e.g. /ipv6 route print where dst-address=188.8.131.52/24)
- testing of ipv6 functions and protocols prior to release! basic stuff like VRRP working in one release and then totally unusable in the next release.... come on...
besides IPv6 it would be really great to have working VRF implementation
and be able to use it to separate the management plane
from the production / customer traffic. currently there aren't any really VRF aware management services like ntp,netflow,ssh,winbox,etc.
In general, I really suggest that MikroTIk reconsider their strategy about software releases and pricing. I would be happy to pay 50% more for the bigger routers like CCRs and in return have a more stable software, means that they differ between bug fix releases and feature releases and also test and bugfix before a release. I mean I totally understand that new features sometimes show bugs not before production use, but stuff that's there for years and suddenly don't work in a 6.x release, come on, you can do this better!