Hello, thanks pcunite for this very informative and well-explained post!
I’m using a different approach, without routing tables and mangle rules, different scope values, adapting suggestions (probably in the wrong way) from @sindy posts .
add comment="WAN1" distance=1 dst-address=1.1.1.1 gateway=(WAN1.Gateway) scope=10 target-scope=10
add comment="WAN2" distance=1 dst-address=8.8.8.8 gateway=(WAN2.Gateway) scope=10 target-scope=10
add check-gateway=ping comment="ISP1" distance=1 dst-address=0.0.0.0/0 gateway=1.1.1.1 scope=30 target-scope=11
add check-gateway=ping comment="ISP2" distance=3 dst-address=0.0.0.0/0 gateway=8.8.8.8 scope=30 target-scope=11
Few questions;
- what is the advantage of having routing tables?
- “Server that will only use ISP2” in Example1, is possible to achieve the same goal just with routing rule?
- /ip firewall connection tracking set loose-tcp-tracking=no
loose-tcp-tracking , there are reasons to disable it? Based on this topic and this article is suggested to leave it on
loose-tcp-tracking=no → Stric
loose-tcp-tracking=yes → Loose