Hi,
It might be good if you could join and split connection marks.
Or have multiple.
So for example you can have part of the connection mark being for QOS value, and part of it being for a Policy Routing setting.
And not have to search through Qos*Policy values to find the bit you want.
Perhaps if at runtime they are numeric values some bitwise and/or operations.
You would need to be able to specify what value each of your connection marks takes.
For policy routing must be used /ip routes rules than mark connection…
Do not misuse just because can be also used…
Mostly yes, but there are some cases where it needs state.
eg. Dual Wan, where there are inbound port forwards on both links,
(heading to the same internal IP address/port)
Want to keep return traffic leaving through original inbound interface.
QOS is getting more important, perhaps a dedicated QOSTracking
mark, to free up the Connection mark for other tasks.
For the Dual Wan case above, I guess often you could have the internal server listening on 2 IP addresses
So the Wan1 port forward would go to IP1, and the Wan2 port forward would go to IP2.
Then the /ip routes rules would work mostly
+1, just like mwan3(bitwise mask)