OK, this is really starting to become an issue, the workaround I have is:
3 ;;; Needed For Wan2
chain=prerouting action=mark-connection new-connection-mark=Even
passthrough=yes in-interface=ether2 - WAN2
4 chain=output action=mark-routing new-routing-mark=Even passthrough=no
But this is not ideal. It will not catch all UDP streams and mark their routes, or server to client outbound traffic as it is only matching an incoming connections, not outgoing. Basically this only enables a ping reply from the internet to wan2
It gets Better - Interface matching is only allowed in the "prerouting" and "output" chains, so if you try "forward" etc you get routing mark only allowed in .....
The only way we can match out interface/mark route (the only way the routeros will accecpt it) is
chain=output action=mark-routing new-routing-mark=Even passthrough=no
out-interface=ether2 - WAN2
but this mangle rule doesn't even catch anything!
Im now pulling my hair out. We really need forward/interface/mark route. SIP wont work over our WAN2 until this is resolved.
Can we please have the ability to add a routing mark to the forward chain matching the outgoing interface. like in 2.9.51
chain=forward action=mark-routing new-routing-mark=Even passthrough=no out-interface=WAN2 dst-address=0.0.0.0/0
As already mentioned the purpose of said rule enables all traffic bound to go out WAN2 to have the correct routing mark applied. Fairly important.