The first label connection and marking packet have traffic overflow problem, even if the direct labeling the same two connection, the first not pass, second will flow, but relatively few. Direct marking packets are not flow overflow problem.
My version is 6.10.
I would suppose that is traffic that is not part of the connection but rather “related” traffic.
Difficult to understand.
Per the documentation, the connection states are:
established - a packet which belongs to an existing connection
invalid - a packet which could not be identified for some reason
new - the packet has started a new connection, or otherwise associated with a connection which has not seen packets in both directions.
related - a packet which is related to, but not part of an existing connection, such as ICMP errors or a packet which begins FTP data connection
http://wiki.mikrotik.com/wiki/Manual:IP/Firewall/Filter
If you want to be sure to mark all interesting packets and want to use the connection tracking efficiencies then you can mark the connection with a passthrough, then mark the packets that are part of that connection without a passthrough then mark any remaining packets without a passthrough.
I have three lines, second-and third-line did a pcc, do pcc always remaining after the relevant part of the default route line to go up, not even made a packet to flow straight down the plant, we should get these flows where to go.
I don’t understand what your trying to communicate. Pasting a config snippet may be helpful.