Unfortunately, not everyone is so lucky. Allow me to sum up my frustration with metarouter.
About two months ago I received request for recursive DNS resolver with DNSSEC validation. MikroTik is clearly not going to provide anything like that in near future, if ever. No problem, OpenWRT with Unbound running as MR would be perfect solution.
As I was new to MR and not expecting any problems, I started with installed ROS 4.5 or so (at RB450G). Router didn't stay alive for long enough to even allow me to finish the configuration. I upgraded to latest and greatest stable ROS at the time (4.16), but nothing changed. I went through forum and found this thread. Oh well, just my luck that I must get the only model that does not work well, I thought. So the resolver went to other computer that was fortunately also running 24/7.
Another case where MR would be useful came up yesterday. This time with brand new RB493G and ROS 4.17 (I understood that it was mostly RB450G with problems, so why not). And really, it was much better. Except for one strange MR lockup at the beginning (I pretended that I didn't see it), it appeared stable. There were no other problems for the whole time I was playing with it (around three hours). Then I left it running. Today I connected to host router again and oops, there was reboot by watchdog timer in the log. I talked to colleague who was sitting near the router and he said it was beeping (= rebooting) the whole day. Great. So I upgraded ROS to 5.0rc11, just to lose all hope, when first reboot came two minutes after starting MR. The only difference is that instead of "watchdog timer" the reason is now called "cause 1". The router is going to production use tomorrow, without MR of course. I don't have the nerve to explain to customer, that everything under fifty reboots a day is ok.
In both cases the routers were basically idling. Just doing the role of NAT router for three users and 4 Mbits in first case. And completely nothing in second. Installed packages were near the bare minimum (advanced-tools, dhcp, ipv6, ppp, routerboard, security and system). I could probably get rid of advanced-tools and not sure about routerboard, but if I had to touch anything else, I could as well throw out the whole ROS, because those features are required. But anyway, why should the number of packages influence anything? Even if I had every single existing package installed, it should still work.
I could also blame my OpenWRT images, I mean, they were self-compiled, not tested by anyone else, it's possible that there's something wrong with them. But then again, it's not guest OS that's crashing, it's host system. I'm no virtualization expert, but if guest system in VirtualBox on my desktop computer crashed host system, I'd say there's something horribly wrong with VB. Is it any different with MR?
Workarounds like disabling watchdog timer are no solution. If I undestand it correctly, it may sometimes prevent unnecessary reboots, but can also cause the router to freeze completely, which is unacceptable.
I wish myself more luck next time.