I have a CCR1009 still getting kernel crashes with GCM encryption. (6.33rc3)
105547111 - Sorry, but I did not understand your question. Mangle rules are fixed in 6.33rc version. It means that fix will be included in 6.33 full version.
Hi Strods,
I meant what about version 6.32 is the dropping of mangle rules going to be fixed in the re-release of 6.32 or is a faster track to 6.33 going to happen?
I’ve got devices on 6.32 I don’t want to touch until either a 6.32 re-release with fixed mangle rules, or a 6.33 final. I couldn’t imagine a 6.32 would be re-released with the mangle dropping issue still left, but I’m asking to be sure…
6.33rc3 seems to be stable version…
Mangle rules fix is included in v6.32.1, released today
i am on 6.33rc1 now
looks like all is ok
6.33rc4 is released.
New fixes:
*) ppp - fixed ppp interface stuck in not running state;
*) ipsec - fixed kernel failure when packets were not ordered on first call;
*) upnp - randomize action urls to fix “filet-o-firewall” vulnerability;
6.33rc4
Thank you. Fixed that.
I would very much like to see the re-added feature to download the upgrade package manager, and so by default withdrew only stable version of the RC version but as it is now.
In an earlier Verich it was quite good and I do not understand why this is so changed, for us it’s a problem, because we have a lot of scripts that we have to change too.
For example, this is totally dysfunctional in the latest version:
/system package update check-for-updates; /system package update upgrade;
okoun - All you have to do is change “/system package update upgrade” to “/system package update install”.
If you did set channel to current, then upgrade process for you will go same as always.
[admin@mikrotik] > /system package update install
channel: current
current-version: 6.32.1
latest-version: 6.32.1
status: Downloaded 87% (13.8MiB)
and install again, again and again… same version
[admin@admin] > /system package update install
channel: release-candidate
current-version: 6.33rc4
latest-version: 6.33rc4
status: Downloaded 71% (11.2MiB)
and last rc version… again downloading and installing same version.
/system package update check-for-updates;
/system package update install;
This script in scheduler will update again and again the same version.
During the same version will remain on disk packages and the next update with a different version take full disc.
Why do not you give the option manually selecting your own server. I do not want your last version. On own DNS server changes the DNS record (upgrade.mikrotik.com) on your own web server.
Add the option to enter your own url and show all the system directories on the web server. Each can then choose which version locally will be used depending on what you recorded on your own web server.
Issue: IPv4 - router locks up and must be power cycled when adding or removing an IPv4 address.
Notes: We are not changing the IP we are using to connect to the router. Occurs over WinBox and SSH. Works fine on 5.26.
Affected Versions: v6.33rc4, v6.30.4, v6.32.1, v6.32
Hardware: hEX Lite
Next step on our side: Test above on RB750, x86 hardware. Test on versions between 5.26 and 6.29.
6.33rc5 will be released today!
New fixes:
*) CAPsMAN - fix 100% CPU usage when trying to upgrade RouterOS on CAP;
*) ethernet - added support for new ASIX USB Ethernet dongles.
fixed:
*) update again and again the same version ??
wake up 
USB Ethernet add, but support for new Intel chips do not add? OMG!!
It is easy to add USB devices and modems. Not so easy to add new Kernel.
Same issue as before, “ether1 excessive broadcast/multicast”.
See attached image below.
Using a CRS112-8G-4S Firmware v3.23
Has this issue been looked at yet? 
Back to v6.30.4 yet again.. 