I noticed when the second “fastrack” rule is enabled the L7 filter rule does not work.
But when I disable the “fasttrack” rule the L7 filter rule works good and its DROP connection to the “mikrotik” site.
What is wrong with that rules?
Does the “fasttrack” rule not work or have a higher priority than the first L7 rule?
People just keep asking similar questions over and over and over again here.
Please learn what fasttrack does first. Here’s the link to the documentation: http://wiki.mikrotik.com/wiki/Manual:IP/Fasttrack.
Then come here and ask specific questions if any remain.
Ass you see, my fasttrack rule is placed at the END of the list and The L7 rule is placed at the TOP of the list.
So the L7 rule should works firstly and DROP that connection but that does not happen, connection is not DROPPED.
When I only remove L7 filter from that rule or disable “fastrack” rule everything works correctly.
Fastrack will catch the traffic and will bypass the rules what ever you do. You can only switch it off or split the traffic like I did.
Using the fasttrack in Rules obstruct the dectection the package that contains the IP (name) I want to filter. I have now split fasttrack in what direction the NAT is going. I want to detect incoming packets so I changed fasttrack to only accelerate the traffic I have generated, by setting the “connection-nat-state=srcnat” in fasttrack-connection.
Any packets that coming from outside will be exempted from acceleration and the RAW will now be able to catch the package that is further up in the package stream.
This was a learning experience for me and my first impression was wrong because I did not see that fasttrack did his work but made the interpretation of the RAW line difficult.
Can the fasttrack rule catch the traffic even it is the last rule at the list?! … and the other rules like L7 are ignored (even is the first one on the list)?
It is not clearly for me, so thanks for your patience.
That is correct. When you use fasttrack, the initial connection setup packets get processed by rules
and a connection tracking entry is setup, and from then all traffic shortcuts all checks.
Because L7 rules look at the content of traffic AFTER this initial setup, they cannot be combined with fasttrack.