Hello from North Dakota, USA!
I’m seeing unexpected results on my queue tree when fasttrack is enabled - can anyone else confirm or explain if this is intended?
I have parent queue DOWNLOAD on my LAN bridge, several child queues - set for PCQ
I have parent queue UPLODAD on my WAN physical, several child queues - set for PCQ
My upload works exactly as I expect, doing PCQ and max-limit being enforced. However, the download does NOT enforce max-limit unless I disable fasttrack, and I suspect that it is not giving the PCQ behavior desired, either.
Am I doing anything wrong by putting the parent queue on a bridge? Can you not use fasttrack with download pcq? Am I missing something? I get exactly the behavior I expect with fasttrack disabled, but CPU is much higher when doing so.
Fasttracked packets bypass firewall, connection tracking, simple queues, queue tree with parent=global, ip accounting, ipsec, hotspot universal client, vrf assignment, so it is up to administrator to make sure fasttrack does not interfere with other configuration;
I looked through that link - cool stuff. However, I’m now wondering if I’m just doing it wrong - I continued to test with and without fasttrack and it is 100% not applying to my queue tree if fasttrack is enabled. My method is to add a mangle for each LAN device like so:
I can only assume that even though I want a mangle to occur, even with fasttrack, it isn’t happening. So maybe it’s not that I’ve got my queue tree wrong, but maybe mangle isn’t the right method to use here? Any thoughts/suggestions?
Re-reading documentation and indeed, Fasttracked packets bypass firewall … etc and mangle is part of firewall. So I think maybe there is no way to use FT and QT together?