I have a Tailscale subnet router that’s running on a separate host that’s being used to access my LAN. I’m having the same issue with Parsec traffic, where it’s seeing traffic from the host, but not Parsec traffic. If I try accessing my LAN through the Tailscale subnet router while I’m outside of my network, the mangle rules don’t see that traffic. I need to prioritize traffic for Tailscale clients accessing my LAN and also Parsec traffic.
/ip firewall mangle
add action=mark-connection chain=prerouting new-connection-mark=priority passthrough=yes src-address-list=PriorityClients
add action=mark-packet chain=prerouting connection-mark=priority new-packet-mark=priority-packet passthrough=no
add action=mark-connection chain=prerouting connection-mark=no-mark new-connection-mark=normal passthrough=yes
add action=mark-packet chain=prerouting connection-mark=normal new-packet-mark=normal-packet passthrough=no
Specifying the destination address or source address directly in the mangle rules doesn’t make a difference, and this happens with the IPv6 rules as well. I’ve also tried specifying connection-mark=no-mark on the first rule and connection-state=new on the first and second rule, but that just prevented it from seeing any traffic. Fasttrack is disabled.
Edit: Found my problem, and the solution was very simple. Apparently by default mangle rules only look for TCP traffic by default, not both TCP and UDP, which is what initially thought until I read the docs. Parsec and Tailscale were sending traffic over UDP, which resulted in my mangle rules not seeing it.