Version 6.34.5 has been released in bugfix channel.
You can see changes since previous bugfix version (6.32.4) by looking through changelog starting from 6.33 and up to 6.34.5. http://www.mikrotik.com/download
Changes since 6.34.4 version:
What’s new in 6.34.5 (2016-May-27 11:52):
*) dude - (http://wiki.mikrotik.com/wiki/Manual:The_Dude_v6/dude_v6.xx_changelog);
*) dude - in order to connect to dude server user requires dude policy to be enabled;
*) bonding - do not corrupt bonding statistics on configuration changes;
*) bonding - fixed crash when vlan parent mtu is higher than bonding mtu;
*) cloud - do not write minor status changes to storage;
*) ethernet - do not allow mtu to be higher than l2mtu and l2mtu to be higher than max-l2mtu (reduce automatically on upgrade if it was wrong before);
*) ipsec - better flush on proposal change;
*) ipsec - fixed crash on policy update;
*) log - fixed reboot log messages;
*) lte - do not allow to set multiple modes when it is not supported;
*) queue - fixed interface queue type for ovpn tunnels;
*) rb3011 - fixed port flapping on ether6-ether10;
*) rb3011 - fixed time keeping;
*) switch - fixed compact export;
*) tile - fixed performance regression on switch chip (introduced in 6.33rc18);
*) winbox - show voltage in Health only if there actually is voltage monitor;
*) wireless - fixed issue when CAPsMAN could lock CAPs interface;
If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.
Hmm.. it seems that logging doesn’t use/regognize time zones anymore.
Every timestamp in logs are now in GMT time.
I’m quite sure that it worked before upgrade (from previous bugfix).
[admin@hap-lite] > /log print
..
09:49:16 system,info,account user admin logged in from X.X.X.X via ssh
…
[admin@hap-lite] > /ip cloud print
ddns-enabled: yes
update-time: yes
public-address: X
dns-name: X
status: updated
kmok1 - We have managed to reproduce problem like this and are currently working on a solution;
Marino - We are not being able to find any issues with routing marks on any of our policy routing configuration tests. Please generate supout file on your device while problem is actual and send it to support@mikrotik.com
I have the same issue as Marino does. Basically, with the previous stable RouterOS version, I had a few statically added default routes over different gateways, all of them ping-checked and with a different routing mark. After the upgrade I can see them all as incative, even though all of them are pingable. When I remove the routing mark from the static route (so the route goes to the “main” table), the route becomes pingable again. I can see that on a x86 (VMWare) and a mipsbe (951G).
0 A S dst-address=0.0.0.0/0 gateway=172.16.80.1
gateway-status=172.16.80.1 reachable via lo1011_network80
check-gateway=ping distance=1 scope=30 target-scope=10
All routes coming from RIP went inactives today. I saw RIP receiving updates every 3 mins as usually and routes were also visible in main routing table, but without A-flag (only Dr). I added one of the routes as static route, and it worked immediately.
It is quite surprising how it is possible that the same bugs that where seen in 6.35.1 were also introduced in this release while it is called a bugfix release!!!
Exactly the same problem here on RB2011UiAS-2HnD and CCR1009-8G-1S-1S+, both upgraded from good old RouterOS 6.33.5. I thought that 6.34.5 should be very stable upgrade, but instead of that - lost connection
the same problem as v6.35.1 have…