Hello folks,
I’ve been experiencing some problems with OSPF. Almost every time something gets changed or removed (ip/ospf entry change, router id change), the router loses its routes and it’s unable to reload them, the only thing that helps is a reboot.
Unfortunately, recently with some new routers added, it started happening by itself without a change and sometimes even affects more routers around. There seems to be no difference between router versions, we are using versions 2.8.26-28 and 2.9.6-7. A router just loses its internet access, telneting to it, all the routes are lost and it needs a reboot. Of course, losing the routes affects all the routers connected to it, making part of the network completly unavailable and thus it’s a major problem.
Does any of you know an effective solution for this problem or what is causing it?
Thanks in advance.
Michal.
More of a coverup than a fix, but you could try having the scheduler run something like this from time to time (2.9, 2.8 would be similar, but slightly different):
:local Counter 0
:local MagicMinimum 1000
:foreach Route in [/ip route find ospf=yes] do={:set Counter ($Counter +1)}
:if ($Counter < $MagicMinimum) do={
:local Nets [/routing ospf network find disabled=no]
:foreach Net in Nets do={/routing ospf network disable $Net}
:delay 5
:foreach Net in Nets do={/routing ospf network enable $Net}
}
:delay 60
:set Counter 0
:foreach Route in [/ip route find ospf=yes] do={:set Counter ($Counter +1)}
:if ($Counter < $MagicMinimum) do={/system reboot}
Changing “MagicMinimum” to match your expectations of normal.
Actually, this would be better (don’t know what I was thinking with the loop):
:local MagicMinimum 1000
:if ([:len [/ip route find ospf=yes]] < $MagicMinimum) do={
:local Nets [/routing ospf network find disabled=no]
:foreach Net in Nets do={/routing ospf network disable $Net}
:delay 5
:foreach Net in Nets do={/routing ospf network enable $Net}
}
:delay 60
:if ([:len [/ip route find ospf=yes]] < $MagicMinimum) do={/system reboot}
So this really is a mikrotik issue. I hope we will see some progress from
the developers soon, we do need the ospf to be functional.
Thanks a lot for the script eflanery.
Best Regards,
Michal.
rip, I understand that you are pissed off, but dont spit on them so badly. After all, Mikrotik is a very good piece of software … just need more tuning. Look at the new versions that are coming really fast. Every new version includes something new and better…
At the end, I still have the same winbox crashing problem for too long time 
You are not the only one who waits for bugfixes
While I have not seen incoming429’s issue, I would agree that the OSPF bugs are amoung the most frustrating and long running.
MT is a great value, and an amazingly flexable and easy to work with system. But things like this have really held us back from widespread deployment. When a routing protocol (and thus, for all intents and purposes, the router itself) crashes just because a few hundred interfaces dissapear, customers get mad. When customers are mad, life is not fun.
Yeah! Thats right
A little offtopic…
We have sometimes near 200 online customers on Mtik PPPoE. Imagine my anger when a pissed off customer calls, and shouts that he have some problem with internet… I opens winbox to check is he logged in, to see what is his IP address from the pool, to try to ping him, check his queue etc… Then Winbox CRASHES … “Please hold on, I have a small problem in checking your online status…”
Or, when trying to insert a new firewall/queue rule, and just starting to type in the values, and winbox just closes… Then again, and again and again…
SF Horror story, isn`t it?
how do you manage to crash winbox? we have only seen one problem with it, and it is fixed in 2.9.8 so I hope you don’t have this anymore
Yes, I DO have it 
This crashing was starting after upgrade from 2.8.27 to 2.9.6. After upgrading to 2.9.7 the problem is still there.
I have to do nothing in winbox to crash it. It crashes even if there is no open window in it at all. True is that then, winbox lasts longer. Sometimes upto 5 minutes. If I open for example Ip>Firewall, it crashes almost instantly.
There is nothing wrong in my computer, the problem is in the router. Here is an explanation why I am think so: If me and my work mate connect from two different computers on the same router, BOTH winboxes crashes in the same time! This is not a coincidence, this happened more than 20 times just yesterday.
I wrote to Mtik support, and got the following answer:
Hello,
We have fixed the crashing isse, which was caused by sudden
disconnection of winbox. now it won’t crash when disconnection
happens, but why it happens you must find yourself - maybe some
firewall rules or other problems
Best regards,
Normunds Rustanovics
Mikrotik
Well, 2.9.8 is still not available for download, I hope that this will fix crashings, but not the disconnects.
After this reply from support, I was still clueless, added the following, and moved it to the top:
chain=srcnat src-address=x.x.x.x action=accept
chain=srcnat dst-address=x.x.x.x action=accept
x.x.x.x is the address of my router.
No changes at all
I also bet that connecting to my router will kill anybodys winbox, so I set up a demo account on it, and sent the ip to mtik support. I tested it out, it crashes with demo user logged in also. As far as I can see, Normunds did not try to connect to it yet.
Normis, maybe you wanna try?
The bigger network, the bigger horror. I have 2500 customers network routed in 1/3 by mikrotiks. It’s very cool when it work, espetialy a box with 10 atheros cards 
I have found another little OSPF bug:
It seems that when static route is marked as dead by Check Gateway, OSPF is still redistributing it to other OSPF routers as valid.
Yes, I DO have it
no you don’t, you don’t use 2.9.8 yet, so you can’t know. as I said, wait for 2.9.8
OK, I`ll wait Will see what 2.9.8 will bring regarding this problem.
Thank you for answer
Can anyone else help me with a problem very easy to reproduce, but MT tech support continuously denies it’s existence?
If you have more than one IP address on an interface (try for example 5), only the last one (sometimes two) gets redistributed after MT reboot!
Best regards,
Everything is OK, finally!!! The bug is solved I have no problems with winbox as it did not crashed for more than 40 minutes! On 2.9.7 it crashed after max 2 minutes.
THANK YOU!