Hi,
Could anyone test if this issue is still present in the latest RouterOS v6?
Hi Kurt,
To the best of my knowledge v6 is still currently running the old routing code base - I’m not willing to put v6 into my main production network at this point to test it.
I do know there were plans from Mikrotik on a new routing-test package but haven’t seen or heard anything of late. Maybe support@mikrotik.com can assist in this case?
Yes it is still an old code, but we did some major fixes.
Thanks for your reply.
But what about the bug this thread is about? Is it fixed?
Hi! Why not all fixes submitted in changelog?
I can not see routing fixes in latest http://forum.mikrotik.com/t/routeros-v6rc10-pre-released/63651/1 (6.0rc10)
or in http://forum.mikrotik.com/t/5-23-released/63180/1 (5.23)
or in the early changelogs…
it’s because MikroTik’s ‘changelog’ is not always ‘fixlog’, unfortunately
Okay, but how we can know about all fixes? It is important!
We are very confused by developers point of view…
We should learn about fixes in telepathy mode?
not telepathy, but laboratory mode 
Cool! So many useless work for finding hidden surprises…
We need to test ALL releases instead reading changelogs…
Like Russians say: “Find something, do not know what”.
[irony]Very very important know about LCD displays improvements instead routing fixes [/irony]
you should test only current release for your needs - they don’t fix old releases. if something is not working - you write to support@mikrotik.com and wait for response. they will say when they fix what you need
I would like to know that too…
I tried to reproduce bug in lab without success, someone get?
During lab testing yesterday I was able to reproduce (but its not consistent) - will try push v6rc11 to the units and see if I can get it to break again
This bug has cost me customers in the past and we’re now considering alternatives ourselves. Its just been there too long without meaningful interactions sadly.
Let me know about your tests with v6rc11 
Well, I`m not sure if my post can be considered as forum rule breaker but by the way. There it goes.
To start, I would like to say that Mikrotik products are great, just their SUPPORT on routing package is not good enought, sadly.
Looking for a solution to my problem related with that bug and time took by mikrotik or solve it, I started a test on low cost router running vyatta, called EdgeMax Lite and results are great so far! IMPORTANT: Low cost, not a core router and no full bgp table, no MPLS, but with ipv6, ospfv3 and ospf.
Once mikrotik releases their new routing package I will be happy to come back and try it again!
Same problem here. We are connected with two BGP Speaker’s (BGP1, BGP2) and when BGP2 goes down we are unable go out across BGP1. Because of Mikrotik’s cache the thing keep trying to send across BGP2. BGP2 has the full route table and BGP1 has only the default route.
Device is CCR1036 with RouterOS version 6.0rc13.
I can confirm (partial) what you are seeing. Our CCR (RC13) is connected to several peers. As soon as I shutdown the session to one peer (with active route), the route disappears completely from the Route List, even though I get this route over serveral(!) other peers too.
All routes which get into the main routing table will never be replaced by routes learned from other peers. Even if one resets the peerings. The router has to be restarted (restart of the BGP instance won’t help)… 
- Mat
The problem that developers are not knowing what to do, and do not want to pay a professional trained to solve problems. Ai is that of trying to hit, so more are missing.
How to use a CCR 1036 as BGP and traffic of 300mgs?
For CCR 1036 not even have 20% of the stability of a RB1100.
What’s new in 6.0rc14:
*) route - automatically repair FIB inconsistencies;
I wonder whether it will fix those ‘stuck routes’…
Finally, let’s test it.
Enviado de meu GT-N7100 usando o Tapatalk 2
Yep, I noticed that too a few days back. I’m going to test it later this week since we can reliably produce the problem.