no, you also have the ability to download older version. just pick from "Select software type" dropdown

But you can only download the versions that you display there.
e.g. 2.9.51, 3.13 and 3.17

I'd need other versions as well, not to say the complete list of it.

Is there some way to download previous versions of RouterOS (perhaps through MikroTik's ftp server or sth)? In the download page you are only given the opportunity to download the latest one.

WinBox Loader v2.2.13 works ok with non-default (8291) ports on RouterOS v3.x, while, on the other hand, design problem still remains with v2.2.13 and RouterOS v2.9.51 The solution to use two different versions of WinBox Loader is something to consider and definitely provides help, but shouldn't Mik...

Some of my mik RBxxx routers, sometimes have a ton of "system info account user xxxx logged in from [dude ip address] via winbox" log entries.... I'm facing a similar problem with a MikroTik v3.16 router. I'm using WinBox Loader v2.2.10 in order to login to router's IP 10.3.36.1 from my P...

The latest version of Winbox (ver 2.2.13) allow you to specify port. Just download it off any router running ROS ver 3.2 and above. This is so not true. Winbox v2.2.13 does not succeed to login in MikroTik 2.9.51 when using a non-default port, while on the other hand Winbox v2.2.10 is OK with that....

Is it possible to add WOL functionality from within MikroTik RouterOS? What would be of great importance, is to be able from within our router, which is running RouterOS e.g. v3.x, to wake-up a remote WOL-supporting computer. E.g. etherwake is a tool in Linux that performs exactly the above function...

The latest version of Winbox (ver 2.2.13) allow you to specify port. Just download it off any router running ROS ver 3.2 and above.

This is so not true. Winbox v2.2.13 does not succeed to login in MikroTik 2.9.51 when using a non-default port, while on the other hand Winbox v2.2.10 is OK with that.

Any recent advances on this? BGP timers have proven to be a bit of a matter again with MT 2.9.26

This has already been done. We will try to isolate the 2.9.24 routing-test in just some routers under our control, and monitor the behavior with regards to the floating "zombie" prefixes. You will have more feedback on this. In the meantime, please take a look in the supout.rif that we hav...

if any of you wants us to fix this, contact support before you uninstall and downgrade. we can't fix it if we don't have any reports of the problem The abnormal situation lures on most routers in our network, regardless if one node has downgraded/uninstalled routing-test package. The above is not a...

[Taking the devil's advocate part:]

What if MT version 2.9.24 with routing test (running on some of our routers) IS actually the cause of the problem?

Please investigate a bit on this. It's really annoying to use an unstable BGP implementation (will that be routing-test or not).

As I have noted above, we are running various versions of MT inside our network (each router announces it's own C-class), ranging from 2.8.X, to 2.9.24 with routing-test package (minority). Personally I use 2.9.6 in my router. Therefore it's not a matter of a single router's MT version, since the an...

We have been using MT 2.9.x and 2.8.x at AWMN (Athens Wireless Metropolitan Network - http://www.awmn.net ), and we have come to notice the following: While manually adding a new network (/24) into BGP routing table, by issuing: routing bgp network ... etc the new route would appear at all routers (...

1 more vote for OLSR

Shouldn't it be nice to have routerOS package fixed to properly support prefix-lists, rather than using the routing-test package? IMHO

It is more than certain that prefix lists do not work with 2.9.x RouterOS versions.