just add connection-mark=no-mark to fastrack rule............

I am using routing marking, so a correct way to implement the idea would be
Works fine.

Another difference between v6 and v7 is that in v7 a routing mark (in IPv4) makes the router do only lookups in the specified table. In v6 it was just a hint, and other routing rules and the main table were still in use. Not in v7. So your alternative routing table must be complete. You may need to...

You state re-transmissions then the question is your network sending out the request, or the other side because it did not got an acknowledgement from you? Secondly did you see any traffic hitting the MTU rule I gave? With this one you don't need to state a wished MTU and it will adapt to the MTU s...

Keep in mind, changing MTU may not have an immediate effect... Connections are tracked and devices have caches of PMTUD. And also setting too low have introduce new problems. But with @msatter this sounds like MTU issue, someplace... Might want to post your full config. Still could be firewall, but...

When TCP connections are taking long or even not complete then think of MTU problems. For that I have the following rule in Mange: add action=change-mss chain=forward comment="WireGuard & IKEv2 Sync" in-interface-list=PMTU-IN log-prefix=MSS new-mss=clamp-to-pmtu \ passthrough=yes prot...

Hello. I'm trying to migrate my config of address list-based routing from RouterOS v6 to RouterOS v7. Here's my RouterOS v6 config: /ip/firewall/address-list> add list block_bypass /ip/firewall/address-list> add address=example.org list=block_bypass /ip/firewall/mangle> add action=mark-routing chain...