Hello,
I’m am using Router OS 6.29.1 at the moment with fasttrack enabled. This evening I found out that simple queues like the example below are not working when fasttrack is enabled. When disable the fasttrack entry in the firewall the queue works fine.
/queue simple
add max-limit=1M/1M name=queue1 target=192.168.1.254/32
Is this normal or is it a bug that will be fixed later?
Best regards,
Patrick
It is normal. You cannot have both.
Fasttrack if for speeding up traffic. Queue is for slowing it down.
Why do you want Fasttrack, if you are limiting speed?
The only possibility is if you mark specific traffic to not be queued, but to be fasttracked. Then separately mark the other traffic that needs to be Queued.
But normis, wouldn’t be great to have fasttrack until the speed limit is reached and then start to apply queueing to slow the traffic if necessary? I know that it doesn’t work that, but there is just need to count the traffic that could be done virtually by side and not in packet processing queues, I would say. Then we could have both at once…
Thank you for the replys.
I have informed me a bit more about fasttrack.It makes sense that queue’s are not working when fasttrack is enabled.
I’ am going to try normis advice.
Hello,
Is there a possibility to have fasttrack enabled and limit user by IP? We are using simple queues to limit users in speed for what they have payed for, but we like fasttrack because it is eating much less cpu (installed ros today 6.30.1) and is really significant.
Thanks for reply.
You can also use Switch to reduce CPU speed, then traffic will not be processed by the CPU. In the Switch config you can assign bandwidth limitations.
You can then configure Fasttrack for other traffic.
Screenshot 2015-07-16 12.56.03.png
If you are using queues of any kind you need to inspect a packet, classify it , and place it in a queue, so that you know when speed limit is reached , queue is full and you an start dropping the packets (limiting speed).
Fasttrack is all about skipping those processes, that is where that speed comes form.
It is like “face control” in the nightclub 
Fasttrack is friends and celebrities that are known to guard that get in as soon as face is recognized.
Queues are regular people in the line that you stand in to get in the club, and in the end they will check your ID, bag and pocket content, and might be discarted
You can’t have both, you can’t have celebrity approach with deep pocket and bag inspection at the same time, can you?
The current implementation is not optimal.
It should implemented in such a way, that Fasttrack gets disabled only for such traffic which cannot be fasttracked (due to simple queues, firewall rules etc…). The presence of simple queues for certain targets should not disable Fasttrack for everything else.
It is so. The fasttrack goes around the queues not that the queues would be going around the fasttrack.
Simple queues should override fasttrack for specific IP/Interfaces where it is applicable.
Then exclude those ips from fasttrack first.
We have multiple queues running and I would like to enable fast track for just one user. How do I go about doing that? Would that be done by using the source ip? Or is fast track for everybody or nobody?
Fasttrack is action in firewall rule. So make whatever condition you want, put that action to it and see.
Too much of a hassle, really, not elegant and is just a duct tape solution to a bad design decision.
Maybe learn a bit about the principles how fasttrack works. And yes, I agree that it doesn’t look so much straightforward.
You guys are surely right, I have a personal “philosophy”: if I have money/need for high speed link I’ll spend some bucks for a horse powered device (rb1100, ccr,..) 
I don’t use fasttrack on production, I only made some tests on lab stuff; surely a great tool on certain conditions but IMHO limited to “home/single user” use.
On other side, I was now thinking to test fastrack to completely bypass queue (best priority ever) for voip traffic ..I’ll give a spin 
Tried that - did not work.
I have excluded the IP range I want to queue form Fasttrack, but did not get the expected result.
Some config fault probably. Try opposite way. Switch fasttrack off, check the queues are working. Add fasttrack only for selected ips and check the others are not influenced.
how to disable fast track?