For context:
CCR2116 running 7.17.2
I was reading the documentation, but I am not sure if this is a normal behavior. We have a CCR2116 with about 1300 pppoe customer connections. All of these have simple queues with bursts generated by the pppoe profile. As soon as we enable FastTrack (not fastpath) by marking connections in the firewall, the queues are bypassed.
You can see a little bit of traffic in the queue, but it does not correlate to the traffic on the matching pppoe-client interface, it is significantly lower on the queue, just some Kbit/s the most, and the customer gets unlimited speed. I understand that queues make the device not FastPath elegible, for which I can confirm that FastPath is not running because of the queues. But there is no mention for FastTrack, and it does get enabled (observed enabled and packets counting on ip->settings FastTrack counter), and CPU drops accordingly, but all simple queues break.
We tested the same config on a CCR2216, and it also bypasses queues when FastTrack is enabled. All of them are configured for a single vlan filtered bridge.
It’s clearly stated in the docs https://help.mikrotik.com/docs/spaces/ROS/pages/328227/Packet+Flow+in+RouterOS#PacketFlowinRouterOS-FastTrack
FastTrack packets bypass firewall, connection tracking, > simple queues> , queue tree with parent=global, ip traffic-flow, IP accounting, IPSec, hotspot universal client, VRF assignment, so it is up to the administrator to make sure FastTrack does not interfere with other configuration!
and
Traffic that belongs to a fast-tracked connection travels in FastPath, which means that it will > not be visible > by other router L3 facilities (firewall, > queues> , IPsec, IP accounting, VRF assignment, etc). Fasttrack lookups route before routing marks have been set, so it works only with the main routing ta
And again, repeated at another place https://help.mikrotik.com/docs/spaces/ROS/pages/130220087/Connection+tracking#Connectiontracking-FastTrack
FastTrack-ed packets are bypassing:
- firewall,
- connection tracking,
- simple queues> ,
- queue tree with parent=global,
- IP accounting,
- IPSec,
- hotspot universal client,
- VRF assignment
It is up to the administrator to make sure FastTrack does not interfere with other configuration.
Silly me… For some reason I searched for the keyword queue in the manual for FastTrack, and didn’t get to that part. Just wanted to confirm if it was normal behavior, which I mostly assumed it would be because of the nature of FastTracking bypassing a lot of processes.
Thank you!!