Need to mention in/out interface in mangle for QoS?

Is it an essential need to classify the incoming router’s interface or src Ip for filters in mangle - forward chain that mark connections for further packet marking before the Queue tree will limit and prioritize the different class data streams?

I have none of both options put in my rules and the QoS looks to be working fine. But I am not sure.

Any advices?

Not if your classification doesn’t refer to/care about the traffic direction.

hmm…

The packet marks generated by the above mentioned mangle filters are used in a Queue tree, which is for both directions different. So I have two parents, one on the outgoing interface going up, and one on the outgoing interface going down. But the child queues use the same package marks for their process.
Would it now make a difference?

Is my understanding right that if mangle in forward chain would label a packet the first time the connection passes the router that when the return traffic passes the router again packets get the same packet mark automatically because connection is in tracker and the first time it was already decided that this connection gets this specific mark?

If we would not have set a src address or initial incoming interface the package that comes back is not only given a packet mark because it is already in the conn. tracker (see above) but is marked again because it runs again through the forward chain and its filters? This way the package is marked twice the same?

That’ll work.