*) ssh - use preshared key also when user name has login parameters;
*) added “:led user-led=[yes|no]” command for RB300/RB600 series;
*) graphing - bugfixes; health section restored;
*) fixed problem - /ip traffic-flow could crash router
*) fixed simple queue vlan matching
*) fixed ipv6 firewall counters
*) user manager - fixed bug related to download/upload counter overflow
in reports;
*) fixed problem - sometimes dhcp client could not renew lease
on wireless interface;
*) fixed problem - connection tracking entries could not be removed sometimes;
*) ospf - don’t install AS external routes with local address as gateway;
*) ospf - fixed bug triggered by adding and removing same AS external route
on two routers; that route could always remain in OSPF routing table;
*) web proxy - compact flash and USB disks did not show up after reboot
on slow boards, fixed;
*) fixed wireless transmit lockup detection;
I also dislike new version numbering scheme. MT has not get out of beta stage yet and it already wasted three version numbers. We will have version 4 in month or two if it continues in this way.
That is unfair.
When I bought v2 licenses it was clear that it covers substantial development time according to the way how versions progress. Not it looks like I am misleaded, and that I got much less than what I payed for.
ok, I hope your thinking is right, so we have a long way to go for a field usable version.
Its funny not only we have to guest how certain ROS function would work. we also would have to guest how a new version numbering works.
We did an upgrade from 2.9.50 to 3.0 but did we have a lot of problem with this upgrade. We found that when we upgraded, the system would only allow some clients on, and the CPU usage went through the roof.
We have just done another upgrade with a base station and fond that it is also full of problem.
Press any key within 2 seconds to enter setup..
loading kernel from nand… OK
setting up elf image… OK
jumping to kernel code
Kernel panic - not syncing: No init found. Try passing init= option to kernel.
I think Ver 3 is just fine, we should give time to MT Team to fix few bugs in Ver 3, and if they fixed their bugs for us and give that bugs free version in the web then we should be thankfull to them not to argue about it.
we upgraded some systems -rb112, rb133c to 3.1 from 2.9 and got trouble with them at once. They reboot frequently for no reason and according to log it was because of power outage (confirmed not to be the cause).
Edit: upgraded those to ver 3.2 and they now work as before
I got a new “problem” after installing v 3.2. Those running v3.2 is not discovered using winbox or neighbour viewer.. Anyone else noticed this ? winbox/telnet connects normal if I type in ip..
by default not all interfaces have discovery enabled on them in v3 for some reason , check /ip neighbor to make sure that discovery is enabled on the interface you are trying to connect to
I’m using ROS on x86 PC.
Tried to upgrade 3.0 to 3.2 via combined package, the ROS stopped responding after reboot. The only thing in console is “Loading system”.
Tried reinstalling 3.2 from CD and it didn’t help. Reinstalling 3.1 help, it works again.
Does anyone have same problem?
please both of you who has this problem, make the support output file from router when it is booting and working fine (v3.0 or v3.1), so then we could compare and look why it isn’t booting the new version. Send those files to support@mikrotik.com
, again we can’t GUESS it goes up to 3.99, sometimes it start like 3.9.1 
