What’s new in 6.32.1 (2015-Sep-07 13:03):
*) RB911/912 - fixed lock-up;
*) RB493G - fixed reboot loop;
*) firewall - do not lose firewall mangle rules on start-up;
*) defconf - fix default configuration for routers without wireless package.What’s new in 6.32 (2015-Aug-31 14:47):
*) trafflow - added support for IPv6 targets;
*) switch - fixed port flapping on switch ports of RB750, RB750UP, RB751U-2HnD and RB951-2N (introduced in 6.31)
*) ipsec - added compatibility option skip-peer-id-check;
*) flash - fix kernel failure (exposed by 6.31);
*) bridge firewall - add ipv6 src/dst addr, ip protocol, src/dst port matching to bridge firewall;
*) RB911/RB912 - fix SPI bus lock after fast led blink;
*) ipsec - fix potential memory leak;
*) bridge firewall - vlan matchers support service tag - 0x88a8;
*) ippool6 - try to acquire the same prefix if info matches recently freed;
*) crs switch - allow to unset port learn-limit, new default is unset to allow more than 1023 hosts per port;
*) x86 - fixed 32bit multi-cpu kernel support;
*) chr - add hotspot,btest,traffgen support;
*) revised change that caused reboot by watchdog problems introduced in v6.31;
*) ipsec - use local-address for phase 1 matching and initiation;
*) ipsec - fix transport mode ph2 ID ports when policy selects specific ip protocol on initiator;
*) certificates -fixed bug where crl stopped working after a while;
*) ip accounting - fixed kernel crash;
*) snmp - fix system scripts get;
*) hotspot - ignore PoD remote requests if no HotSpot configured;
*) hotspot - fix kernel failure when www plugin aborts on broken html source;
*) torch - add invert filter for src/dst/src6/dst6 addresses ;
*) bonding - add min_links property for 802.3ad mode;
*) snmp - get vlan speed from master interface;
*) hotspot - fix html-directory path on small flash devices;
*) mipsbe - make system shutdown work again;
*) lcd - fixed parallel port LCD display support on multi-cpu x86;
*) bridge - fixed use-ip-firewall-for-vlan in setups with multiple bridges;
*) ipv6 - fixed DHCP-PD client skips some steps when renewing lease;
*) upnp - fixed protocol port selection for upnp protocol comunications;
*) firewall - fixed limit and dst-limit options.
*) winbox - fixed wireless interface l2mtu (VirtualAP and WDS interface creation in winbox)
*) winbox - fixed multiple firewall rule moving in Winbox 2
*) simple queues - restrict all changes in dynamic simple queues
What about these other bugfixes of the latest .33 RC? They are not present in .32.1. Will they be included in a future .32.x release?
*) RB532/RB564 - fixed no link after ethernet disable/enable;
*) tile - fixed occasional deadlock on module unload;
*) ipsec - fix sockaddres buffer size on id generation for ipv6 address;
*) mesh - fix router lock-up when interface is added/removed;
they will be in v6.33 as the RC name suggests.
Only critical issues were backported to 6.32.1
In addition to the closed topic http://forum.mikrotik.com/t/v6-32-released-version-temporarily-removed/91003/114
I happened to notice in System - Resources that one of the spare RB750UP devices has 250MHz CPU frequency instead of the normal 400MHz.
I do remember that just loaded ROS (twice) and upgraded firmware, but did not change CPU frequency manually.
Somehow it decreased itself, which led to a noticeable increase in the configuration file saving time and increased loading CPU by everyday Simple Queues/Firewall payload.
But I still can’t believe that this strange CPU frequency self reduction will result in congestion device by management process or provoke a reboots or crashes when creating supout.rif – that was a real bug, IMHO.
Please look if somebody noticed this issue too.
Ansy, if the Kernel has crashed in a specific way, the CPU could be lowered.
You can just set it back. We will fix this issue so that it goes back to the original value. Thank you for reporting it.
Are the ones below not critical? The first may require a reboot or site visit to fix, the second speaks for itself.
*) RB532/RB564 - fixed no link after ethernet disable/enable;
*) mesh - fix router lock-up when interface is added/removed
Besides, you said the point releases are to include bugfixes, not features. Bugs are not only the critical ones, right? How hard is it to backport these fixes anyway?
Are you sure that those changes doesn’t break any other boards or feature?
have you tried them in ALL possible configurations?
fixes that breaks other stuff happened too many times before, you do not have to look too far - latest example was v6.31 and v6.32 release.
If this is the case, then you are right.
The torrent file PLEASE…
Please, understood, not all routerboard need or have internet access to do an auto update…
BR
Just want to make sure I understand the release cycle…does this mean no new fixes will be added to 6.30.4 and that 6.32.1 is the latest bugfix?
*) ipsec - fix potential memory leak;
I can confirm this.
CCR1036, multiple site2site tunnels. The point where I upgraded from 6.31 seems obvious 
CCR_memory_leak.jpg
Thanks!
-Chris
No. Version name does not indicate the release chain. v6.30.4 is still the bugfix release.
v6.32.1 is the current one, because it includes also a lot of other changes (see v6.32 section of the changelog)
RouterOS will start showing the package chain in v6.33 so you will know what you have installed
my RB450G has below warning, is it normal or bug?
ether2-master-local excessive broadcasts/multicasts, probably a loop
Snap1.jpg
previous v6.30.4 doesnt have such problem.
pls help to solve it. thanks
I’m having the same issue. It stops when I revert back to v6.30.4
-tp
Good to hear…We have had a lot of success and stability with 6.30.x bugfix so far and hope to see it around for a long time as the most “stable” production version of RouterOS in the 6.x release family.
Please, put all the fixes of errors that occur in 6.30.4 to 6.30.5. Especially the RB532/RB564 - fixed no link after ethernet disable/enable
Make at least one version that will safely work! Let it be 6.30.
Thank you.
It could happen that some fix to 6.30.4 implies a significant change, so it does not belong in Bugfix directly.
So does it implies that there will never be stable ros version? Right?
+1
…the same here… on my home router (RB 2011UAS-2HnD)
Since it was flooding my log I reverted back to 6.30.2.
… and YES I am absolutely sure I have NO loop in my network…!
6.30.x would be stable, but for certain fixes you would have to move to 6.32.x when it is stable and in Bugfix too, then 6.30.x could be abandoned.
At that point 6.33.x would be Current.
I guess the stable branches would not have to be abandoned too soon to ensure that the following one is really good and provide certainty to people who otherwise had no problem staying on the “broken” stable branch.
Note that it would even be possible that 6.32 is deemed unfixable in some other way and never enter Bugfix, so you would either have to wait in 6.30.x until 6.33.x enters Bugfix, or if your problem is too critical, try Current.
I think that for backporting of difficult fixes, rc versions not tagged as Bugfix on the stable branch would be needed. This would actually be a good idea for every release on the stable branch.
I guess for simplicity they would not have to be labeled rc, just not tag them as Bugfix immediately, but there should be a way of easily but safely seeing them on the upgrade page.