Mangle Routing Mark for mt's builtin VPN Clients ?

(mikrotik Routerboards on both sides of this connection)

Side A is running MT’s PPTP Server and L2TP server (both builtin Mikrotik, on this device’s single, public IP)

Side B (at a different location) is running PPTP-Client and L2TP-Client to Side A. (this all works great)

On Side B im looking to use Mangle rules to add a routing mark to the L2TP-Client (so that via /ip route add gateway=X.X.X.X routing-mark=“MT’s L2TP-Client Mark” i can then route the L2TP-Client via a different GW / Device).

Can anyone help on the proper /ip filter mangle rules to add so i can mark a Mikrotik’s Builtin L2TP-client ?

(ive been trying similar to: /ip fire mangle add chain=prerouting proto=udp dst-port=1701 action=mark-routing new-routing-mark=“MT’s L2TP-Client Mark” but have had issues)

thanks!

EDIT:
I decided to email MT support and got this helpful, quick reply from them:

“You should have rules which puts routing mark on 1701 for L2TP and another routing mark for 1723 TPC and GRE 47 traffic.”

I had only been marking for 1701 UDP and proto GRE, so i will re-test with also marking for 1723 TCP and will update this thread later in the week when im onsite with this particular MT)

Im posting solution/results incase someone has this same question in the future.

again, my goal is, on a MT with several outgoing L2TP-Clients ( /interface l2tp-client (s) ) , to be able to route one specific /interface l2tp-client via a different gateway (and thus via a different provider/ISP - in this case an 4g/LTE modem vs a DSL modem for all the other L2TP-Clients)

tks MT support!