Dear RouterOS devlopers,
I cannot help myself but feel that the focus of Mikrotik is no longer ISP market. It feels that later products and software development is geared towards end users - LTE and such…
We have been living with numerous bugs and missing implementations for past few years. Let´s mention missing radius attributes (Delegated-IPv6-Prefix, v6 accounting), non-workin flow control on x86 platform, non-operational BFD, buggered MPLS on CHR and missing drivers (SR-IOV or anything intel in past 10 years?) just to name a few. Those are features that I expect and care for from Mikrotik. Not a support for another USB modem.
We are exclusively Mikrotik shop at the moment, but as our network grows bigger so do your requirements (not the only one here I figure). We already hit the limit with IPv6 and CHR in production and as it is now, there is no way forward. The situation forces us to look for other vendors which we absolutely hate, but it is either that or not being able to grow which we hate even more.
Don´t even get me started on mythical version 7 which is supposed to fix all our problems and most likely even bring world peace and cure cancer. For real, how long have we been promised v7? 2 years? 3 years? 10 years? I wonder if it will ever come…
I would like to ask Mikrotik to consider where they are headed. Battle over wireles is over (Mikrotik lost) and routing/switching is all that´s left.
Have you just woken up? Mikrotik does what makes the profit. I was sad for the orientation change towards home end users several years ago on this forum but uselessly. It is too late for tears now. Just take it as it is. Or take your money and make an offer to mikrotik owners…
Not to mention the Hotspot but they introduced in V6 when they introduced CRL checks…
When a sudden powerfailure occurs, the hotspot using HTTPS with local certificate does not intialize properly and manually needs to be rebooted.
BUg there since at least 1 year unfixed… Same goes for RADIUS accounting missing when system reboots and WAN is using non-typical ethernet uplink like PPP (internet link is shutdown before flushing all records)
It does seem that the home user is the market Mikrotik is targeting their products at.
Routing in v6 is severely broken, no fixes are forthcoming and there is constant promise from support of them being fixed in RouterOS v7.
The problem is, RouterOS v7 is 3 years overdue, and there is no sign of it coming anytime soon.
While Mikrotik have introduced service provider targeted hardware like the CCR, RouterOS currently lacks both the features and stability to be trusted by modern ISP’s.
examples:
BFD is completely unusable in RouterOS v6
Polling routing information via SNMP can cause routing to crash
L3VPN’s do not send NLRI updates on PE-CE BGP changes.
IPv6 recursive next-hop support is broken and cannot be used to advertise IPv6 loopback addresses.
Sadly to find out it, but i think current Mikrotikls focus is SMB/SOHO and WISP access, not BroadBand ISP (CCR could be very nice BRAS, but not IPv6 ready (radius attributes), and nor for Enterprise/ISP Core - issues with BGP (need to rebuild RIB saturation in case of BGP rebuilding), nor for enthusiasts - closed source, no kernel-integrated API (not about invoking CLI strings with POST/GET).
So i’m using it as WISP/ISP access and CE devices and it’s good. No one should upgrade in production without testing on stand.
For it’s segment Mikrotik is VERY good hardware with a bunch of possibilities (and bugs, and bugfixes, each release should be tested in lab before applying), very usefull GUI and native console.
There is a lot of pros and contras, just use it by its purpose (WISP access, BRAS, SMB/SOHO) and you will be satisfied. Forget about using it inside ISP core/aggregation (at least before ROSv7). But do not forget: Mikrotik is deaf to feature requests (by very own reason - currently our developers is busy and we not provide any possibility to closer integration).
For other cases you can use Linux - issues with interface, but you can build it by self.
And for topic starter - try Cisco XRv instead - up to 40G per core.
it’s true …
Mikrotik is best for home users…
For ISP - MR have many-many bugs … not for stable service …
no nic drivers\BGP memory leak\bug in fast-track in last version\ospf not working corectly\no igmp-snooping …
many many problems…
Mikrotik certainly not for the house, there is no support for IPTV, P2P, high speed Wi-Fi out of the box, for me personally, this device for the last 2 years of the great went is not much worse, I know a lot of very cheap devices but they are not perfect, but there is everything you need out of the box, why not respond to the requests of users, or at least behave respectfully and not to reply “let’s do it when we do” ??? you are losing tens of thousands of users and a lot of profit in this respect
I just wish they would quit releasing broken Dude servers in the current release tree. leave broken versions in the RC builds please! Its so broken it makes me yearn to go back to the windows server.
I wonder how many are in fact actively engaged in programming ROS? Sometimes I feel that they are doing only two programmers. Just a very few people.
So if a few people and no money to pay them, I suggest that the formation of any new licenses for ISPs to ensure timely repair and upgrade. I think it would be fair.
Programming is a quite difficult and time-intensive task, so it’s not likely that they are just two. And so far they did a great job. My perception is just that their roadmap has different priorities than my (everyone’s) requirements. And they have their reason to do it, therefore I just keep hoping that they will switch full time to ROSv7 development.
Unfortunately the output of a group of programmers is not linearly proportional to the number of programmers.
In fact, the curve output-vs-number often shows a dip that can sometimes even drop to zero. https://en.wikipedia.org/wiki/The_Mythical_Man-Month
Just a little note, you do also got to have reasonable expectations of features. Shure its bad a few of the bugs in ROS but I would not expect to use a CHR, CCR or anything mikrotik to be able to do the same as the ASR 9000s we use in our network. Use the right product at the right place in the network.
For me it had been better with less software features on the WISP products (but better performance and hardware features, no problem with a price increase) and just leave the core network to the big vendors like Cisco, Juniper and so on..
The frustrating thing is that up until mid 5.x release train, Mikrotik were showing tremendous promise of being able to be used for ISP core networking, introducing their own routing engine with “routing-test”, MPLS, DHCP-RADIUS and other such features, they were heading in the right direction. But then they just stopped…
Lol yep. The other fix I have found is sometimes I have to move their filters position in the chain up then back down. So say a filter is #7. I need to move it up to say #4 then back to #7 and it will start working.
When I first had it happen,I thought I just had my filter orders wrong, but have seen it happen hundreds of times since
it is back now.