Oh no.... i've just find in my old gitted commit the 4th september 2025, i've enabled the dhcp snooping on the bridge and just read your answer and read the doc that don't say anything about dhcp snooping : Connection tracking - RouterOS - MikroTik Documentation
So just disabled dhcp snooping and counters increase
[admmikrotik@router70a] > /ip/firewall/filter/print stats
Flags: X - DISABLED; D - DYNAMIC
Columns: CHAIN, ACTION, BYTES, PACKETS
# CHAIN ACTION BYTES PACKETS
;;; special dummy rule to show fasttrack counters
0 D forward passthrough 44 398 941 51 874
So for all : it's not a problem with this release, but maybe doc not up to date/complete
It's "in the documentation" but you have to chain things together . Here is the part that describes FastTrack:
Where it says that:
Traffic that belongs to a fast-tracked connection travels in FastPath
also with the FASTTRACKED? -> YES -> FASTPATH arrow in the diagram.
And under Requirements:
FastTrack is active if the following conditions are met:
...
bridge FastPath is enabled if a connection is going over the bridge interface;
Then if you scroll up to the section that described FastPath:
You'll see one of the conditions for the Bridge FastPath handler working is:
bridge dhcp-snooping is disabled.
Which means if your FastTracked traffic involves interfaces related to a bridge (including VLAN interfaces over a bridge interface), and DHCP Snooping is enabled, then those connections even marked with FastTrack will not be able to use FastTrack (because FastTrack cannot use the bridge FastPath for them).
Yes you're right, i've upgraded this evening and i was pretty really really sure FT was working.... i use mkt since so long time, it's like ntp.... don't verify, it work for sure, this can't be wrong. LOL
Aside from the documentation, I have a much bigger problem with this output. How is one supposed to troubleshoot or understand it properly if ROS is giving such misleading information?
It is more or less a result of people enabling every (new) option they see, without overseeing the consequences. "dhcp snooping yeah that sounds nice, let's enable that" without actually needing it.
I see fasttrack as a solution to achieve higher speeds on underpowered routers. Not typically required in the same place as where dhcp snooping would be desired. You can always buy a faster router that achieves the desired speed without fasttrack, and never see the potential issues with it.
(I always disable fasttrack first thing I do except on very trivial configurations, because I rather spend a little more on a router than spend time and pull my hairs out working with fasttrack)
My device is hAP Ax2 and I had serious issues with the ethernet. Connectivity was lagging, speedtests were in the range of 10mbps while on the wifi I had the full 300mbps of the FTTH connection. But it wasn't on the first day I installed the update. Now I have reverted to the long stable and performance is back.
Maybe the issue returns on day 2. You said 7.22.3 (?) was working ok on first day. So it may be unrelated to ROS version and/or ROS at all. Could be external factor as well.
It was definately the mikrotik device. I replaced with my ISP's router and everything was ok. And definately not an internet issue, since I was having problem accessing lan devices and Winbox connecting to mikrotik through ethernet. Today I installed 7.23 and everything is up to speed now. If the issue returns I'll come back with more data.
. Here is the part that describes FastTrack:
