RouterOS v4.12 released - comment

What's new in 4.12 (2010-Oct-25 10:35):

*) added support for RB493G;

Download using torrent:
http://www.mikrotik.com/download/routeros-ALL-4.12.torrent

Regular download:
http://www.mikrotik.com/download.html

Regards,
MikroTik

3 months since the last update 4.11, and we only have this update? Is 4.x death?

is this the only change? =)

seems like it is…

API logins still stay forever in Active Users…

This is not a bug, this is a remember of your hacking actions via API.. xD

there’s also a firmware upgrade … at least in the mipsbe

One would hope that it contained the OSPF fix.

because of new device: RB493G.

Yes, RB493G is mipsbe, and “added support for RB493G” is changed fw for rb493 then.. your sentences are the same ; )

What's new in 5.0rc2 (2010-Oct-27 16:20):

*) wireless nv2 - encryption support;
*) tool fetch - support ftp STOR;
*) ospf - fixed crash when working with external LSA that contain
forwarding addess;
*) ipsec - supports NAT-T drafts;
*) ipsec - added debug logging, to maintain same log verbosity as before with
'ipsec' topic now use topics 'ipsec,debug,!packet';
*) ipsec - make it work with EoIP, GRE, PPTP and L2TP;
*) support for Atheros AR9271 wireless chip;
*) added support for more Intel 82575/82576 PCI-Express Gigabit Ethernet cards;
*) added support for idle detection on RB1xx/RB5xx in /tool profile;
*) fixed Wireless manual tx power configuration for 11n rates in WinBox;
*) fixed torch;

And the Oscar goeees toooooo: TITANIC! xD

MT have a bloody horrible CHANGELOG history, I know for a fact that there is a ipv6 issue and a routing crash issue that support have told me is fixed in 4.12 yet it isnt in the change log.

Its completely unacceptable to have such bad habits like this, Whats the point of having it if its not accurate!

Agreed, its enough to drive one bonkers!

Maybe its not fixed for sure yet?

Doesnt matter, a CHANGELOG’s point is to detail changes! If they have messed around with routing then they need to say so. Its bonkers for a company like this to not say whats changed in a version. It means for us to confirm that the release is stable enough to deploy we have to retest every single feature we use before we deploy