For those that had confirmed bug reports, please check if the issue is resolved.
What’s new in 6.29rc22 (2015-May-19 13:38):
*) fasttrack - correctly close fasttrack connections;
*) firewall - fixed sector writes rising starting since 6.28;
*) tile - fixed fasttrack;
*) snmp - fix rare bug when some OIDs where skipped;
*) ssh - added aes-ctr cipher support;
*) mesh - fixed kernel crash;
*) ipv4 fasttrack fastpath - accelerates connection tracking and nat for marked
connections (more than 5x performance improvement compared to regular slow
path conntrack/nat) - currently limited to TCP/UDP only;
*) added ~fasttrack-connection~ firewall action in filter/mangle tables for marking
connections as fasttrack;
*) added fastpath support for bridge interfaces - packets received and transmitted
on bridge interface can go fastpath (previously only bridge forwarded packets
could go fastpath);
*) packets now can go half-fastpath - if input interface supports fastpath and
packet gets forwarded in fastpath but output interface does not support fastpath
or has interface queue other than only-hw-queue packet gets converted
to slow path only at the dst interface transmit time;
*) trafflow: add natted addrs/ports to ipv4 flow info;
*) queue tree: some queues would stop working after some configuration changes;
*) tilegx: enable autoneg for sfp ports in netinstall;
*) health - fix voltage on some RB4xx;
*) romon - fix 100% CPU usage;
*) romon - moved under tools menu in console;
*) email - store hostname for consistency;
*) vrrp - do not reset interface when no interesting config changes;
*) async - fixed ppp server;
*) sstp - fixed router lockup;
*) queue tree: some queues would stop working after some configuration changes.
*) console - allow ‘-’ characters in unknown command argument names;
*) snmp - fix rare bug when some OIDs where skipped;
*) fixed CRS226 10G ports could lose link (introduced in 6.28);
*) fixed FREAK vulnerability in SSL & TLS;
*) ipsec - allow to specify custom IP address for my_id parameter;
by becs » Wed Apr 29, 2015 9:07 pm
In current implementation (6.29rc15) FastTracked (and FastPathed) packets will not be accounted in Traffic Flow.
But.. there are possibilities to extend FastPath/FastTrack feature set in the future.
At the moment, please, test basic FastTrack functionality, and report back if you encounter any issues.
Thanks 105547111 for hints, I’m not using fasttrack now ..and fast path on bridges was already there from ages. So something have been changed/updated on fast path implementation so that .. .. bla bla ..
ffernandes, Neilson - If you are using bridge but use-ip-firewall is not enabled, then Queues will not be limiting bridged traffic: http://wiki.mikrotik.com/wiki/Manual:Interface/Bridge http://wiki.mikrotik.com/wiki/Manual:Packet_Flow_v6
paoloaga - These were two separate fixes where issues were triggered in different ways
LynxChaus, Petzl - Please write to support@mikrotik.com. It must be something specific with your configuration/topology. Send supout files and we will inspect them
105547111 - Please als owrite to support@mikrotik.com. Did it start with upgrade?
bajodel - Where it is not counted? Have you checked your bridge settings?