I need a copy of the all_packages zip for 2.9.12 OS for the RB-230's If someone has an archive, would you please email to me or send a url if they know where it might live?
2.9.13-14 has caused a lot of trouble with our network and OSPF
email:
phil@aircanopy.net
thanks!

I need a copy of the all_packages zip for 2.9.12 OS for the RB-230's If someone has an archive, would you please email to me or send a url if they know where it might live?
2.9.13-14 has caused a lot of trouble with our network and OSPF
email:
phil@aircanopy.net
thanks!

I have: routeros-x86-2.9.12.npk and routeros-rb500-2.9.12.npk
If you want them, send me an email to joseiacosta at cibernetcom dot com dot ar


Regards

--
José Ignacio Acosta
Cibernet Comunicaciones / Mikronet
Joaquín V. González
Salta - Argentina
http://www.mikronet.com.ar
http://www.cibernetcom.com.ar

MT has an archive just change http://www.mikrotik.com/download/all_pa ... 2.9.14.zip to http://www.mikrotik.com/download/all_packages_2.9.X.zip

Thank You!

would it not be a good idea to place a little link to the archive on the download page?! ;-)

there is no actual reason for suggesting downgrading, except if there are some really majour problems. we do not suggest downgrading

Err...this?

http://forum.mikrotik.com//viewtopic.php?t=7070

it says you should not upgrade if you use dynamic routing. it does not say you should downgrade

Hmmm.
Lets see, I have about 12 RB232's and 3 RB500's. Since 2.9.13 OSPF has been problematic. We upgraded to 2.9.14 to FIX the issues from 13 and our OSPF crashed and any router with more than one ospf partner in our case 9 of them had flapping interfaces and would not form adjacencies and did not pass traffic.

This means for my network that over 2000 customers did not have service. We spent the better part of a day thinking it was hardware, and then when new hardware did the same thing, we decided to roll back to 2.9.12 on the core 532's and they stabilized.

The next morning, ALL of my RB232's running 2.9.14 were down so we had to power cycle each tower so they would come back up then we downgraded to 2.9.13 as I did not have a copy of .12 for the 232.

This morning AGAIN one of the hub towers with four attached towers or 600 customers was down again and the interface on the neighbor router showed 12000 state changes in four hours. We bounced it and it is now downgraded with 2.9.12 we pulled from the archive page.

I would consider every tower on my network failing after the 2.9.14 release a significant reason to change.

I appreciate the support from this forum and I thank those that contribute, but even Mikrotik sent a warning about 2.9.14 yesterday and the 532's, but we have this issue across the board.

I am now downgrading every router to 2.9.12 when it was last stable and we are planning to remove the mikrotiks from our network and move to something that can handle the load we place on the hardware.
Again I thank everyone for their support.
Phil

If you upgrade your entire network to the bleeding edge you should expect problems. What happened to testing things on your network before you roll them out? We never put a new version into production without fully testing it in development first. It's common sense, even with Microsoft or Unix OS you do the same.

Sam

It is indeed common sense to test new software releases before applying them to your network but to do this thoroughly you need a complete replica of the network including traffic load. This is not practical.

Release 2.9.14 was not marked as a beta release and it is software which is bought and paid for by it's users. Mikrotik would do better to have identified the problem, sent an email to all licensed users and provide an easy to find link to 2.9.12 with instructions on how to perform the downgrade. As it is, IMHO, they are trying to pretend there is a very small problem and doing little to remedy it. This is not helpful and will lead to a loss of confidence in the product as indicated by pbwalsh.

I agree and accept that it is my responsibility to test software before a roll out. On the other hand when a release appears so soon after another release with IDENTIFIED routing problems it is a safe assumption (one that I will never make again) they have been resolved even though not specifically listed in the changelog.

While I accept responsibility for the outage I hold Mikrotik squarely responsible for propagating known bad software. They have enough of a user community to have a beta test before general release.

My solution to roll back to 2.9.12 has stabilized our network. The previous comment that it will be fixed in the .15 release is absurd. Equally absurd is the idea that somewhere buried on the website forum it was posted to not update if you are using a dynamic protocol. Is there a large ISP in the user community that is NOT using some type of dynamic protocol?

The routing issues should have been addressed before .14 especially when they are fully aware of the issue regarding dynamic routing.

I understand that Mikrotik is not Cisco, but they are by far the best product in the small router market and the industrial marriage with the routerboard is the reason that we chose them in the first place.

I hope that Mikrotik will improve their release process and make some changes to the website to allow users to quickly find archival software and be clear about issues that they are aware of with the os in the changelog and patch accordingly.

Again I appreciate the support in this forum and thank Mikrotik for a great product.
<end rant>
Phil

we are working hard on fixing all the routing issues, it is top priority now. wait for further announcements

In my opinion, Mikrotik should little bit revise its testing procedures and give more information to users about changes between versions. I think nothing serious happens, when some minor errors are found in new releases, but it is not possible to release version with here described errors.
I am programmer so I know it is not always simple task to release new version of software, but from user point of view I must say that I do not want to be involuntary tester of every new release.
I had similar problems when upgrading from version 2.9.8 to 2.9.9 and 2.9.10. There was problem with IPSec and there was even no mention about changes in IPSec in changelog, I supposed no problems during upgrade and oops. This experience forced me to have two Routerboards at the table and test every new version, but why should I do it?
Please do not take my post as attack, Mikrotik is great product, but there are always things to improve...