hi,
Does Fasttrack affect marking of Packets done by mangling?
Im using mangle to mark these type of traffic:
1. valid work traffic(to company servers and the return traffic) - Unrestricted
2. Downloads - 5Mb
3. Uploads - 5Mb
I am using a queue tree to setup traffic limiting on the routerboard.
I noticed that if fasttrack is disabled I actually limit the download and upload to 5Mb, once i enable fasttrack the traffic exceeds the limit that ive placed.
So does fasttrack skips the mangling by fasttracking the packets?
-
-
jonathan2493
newbie
- Posts: 25
- Joined:
Re:
Packets belonging to fasttracked connection go around the firewall so nothing is applied by firewall to them. Queues including.
any suggestions/workarounds regarding mangling and queues?
Re: Re:
Sorry I can't offer an answer to your query as I can't figure it out for my similar requirement.
I abandoned Fasttrack (for the time being) due to required QoS for my VoIP. I think the concept of Fasttrack is fine by itself. And MikroTik's effort is to be commended.
However, traffic on a freeway at times (borrowing a metaphor) does slow down for one reason or another. Hence the need for QoS (when required).
From my memory, Jarda made a point about the ability to apply Fasttrack for a specific requirement or area rather than an overarching application as originally introduced.
And I am not sure of its latest status.
Cheers
I abandoned Fasttrack (for the time being) due to required QoS for my VoIP. I think the concept of Fasttrack is fine by itself. And MikroTik's effort is to be commended.
However, traffic on a freeway at times (borrowing a metaphor) does slow down for one reason or another. Hence the need for QoS (when required).
From my memory, Jarda made a point about the ability to apply Fasttrack for a specific requirement or area rather than an overarching application as originally introduced.
And I am not sure of its latest status.
Cheers
Re: FastTrack and Mangling
Why do you look at fasttrack as global feature for all the traffic - it is not.
Fasttrack-connection is essentially exactly the same as mark-connection/packet.
With one you mark specific connections for queues.
With other you mark specific traffic for fast bypass.
i use fasttrack for all client communication to internal servers, and use queues for client Internet connections at the same time.
Fasttrack-connection is essentially exactly the same as mark-connection/packet.
With one you mark specific connections for queues.
With other you mark specific traffic for fast bypass.
i use fasttrack for all client communication to internal servers, and use queues for client Internet connections at the same time.
Re: FastTrack and Mangling
Sometimes I am returning to fasttrack back to try to utilize it. But until I am under the performance limit of the routers, there is no reason to use fasttrack so much. I have some very selective rules in firewall prepaired for switching the fasttrack on for some kind of traffic (typically local traffic and torrents), but I still have them off. Anyway, I appreciate this option because I see it very useful. At least like a toy for me so far.
Re: FastTrack and Mangling
Hello, I have a problem with fasttrack and mange rules.
I have a mangle rule to mark all packets (mark routing) from selected IP sources to route it differently (ip route to 0.0.0.0/0 with routing mark set shall go to a different router)
Whenever I switch on fasttrack, it seems either the special route or the mangling stops working
lg
Stefan
I have a mangle rule to mark all packets (mark routing) from selected IP sources to route it differently (ip route to 0.0.0.0/0 with routing mark set shall go to a different router)
Whenever I switch on fasttrack, it seems either the special route or the mangling stops working
lg
Stefan
Re: FastTrack and Mangling
That is the whole point of FastTrack:
https://wiki.mikrotik.com/wiki/Manual:IP/Fasttrack
"Fasttracked packets bypass firewall, connection tracking, simple queues, queue tree with parent=global, ip traffic-flow(restriction removed in 6.33), IP accounting, IPSec, hotspot universal client, VRF assignment, so it is up to administrator to make sure fasttrack does not interfere with other configuration;"
https://wiki.mikrotik.com/wiki/Manual:IP/Fasttrack
"Fasttracked packets bypass firewall, connection tracking, simple queues, queue tree with parent=global, ip traffic-flow(restriction removed in 6.33), IP accounting, IPSec, hotspot universal client, VRF assignment, so it is up to administrator to make sure fasttrack does not interfere with other configuration;"
Re: FastTrack and Mangling
Somehow I don't get it completely....
Referenced page says:
IPv4 FastTrack is active if following conditions are met:
* no mesh, metarouter interface configuration;
* sniffer, torch and traffic generator is not running;
* ****removed****no active mac-ping, mac-telnet or mac-winbox sessions****removed**** restriction removed in 6.33;
* /tool mac-scan is not actively used;
* /tool ip-scan is not actively used;
So fasttrack should be active, but why are the mangle rules affected?
How I understand the fasttrack is, that a new TCP (or UDP) connection runs through the firewall, but then the established connection bypasses the firewall. This gains performance.
My mangle rule should establish a connection to the different router, then when established everything could run through fasttrack (bypass the firewall).
Problem is only that it does not work. everything works fine, when the fasttrack rule is disabled, When I reenable it the packets go to the default router
Referenced page says:
IPv4 FastTrack is active if following conditions are met:
* no mesh, metarouter interface configuration;
* sniffer, torch and traffic generator is not running;
* ****removed****no active mac-ping, mac-telnet or mac-winbox sessions****removed**** restriction removed in 6.33;
* /tool mac-scan is not actively used;
* /tool ip-scan is not actively used;
So fasttrack should be active, but why are the mangle rules affected?
How I understand the fasttrack is, that a new TCP (or UDP) connection runs through the firewall, but then the established connection bypasses the firewall. This gains performance.
My mangle rule should establish a connection to the different router, then when established everything could run through fasttrack (bypass the firewall).
Problem is only that it does not work. everything works fine, when the fasttrack rule is disabled, When I reenable it the packets go to the default router
Re: FastTrack and Mangling
Routing marks are not applied to packets when FastTrack is being used so the policy based routing can not work in such configuration.
Re: FastTrack and Mangling
How is it with updating the documentation? Would avoid others to fall into the same trap
Re: FastTrack and Mangling
This is already documented. I did reference wiki page few posts ago:
viewtopic.php?f=2&t=102031&sid=7f25ec36 ... c3#p615768
viewtopic.php?f=2&t=102031&sid=7f25ec36 ... c3#p615768