Advanced Routing Failover without Scripting

[KOK]

Thank you for your answers!
I stll have some doubts:

@Chupaka

Well, if you create routing tables (by setting routing-mark on routes), you need to send traffic to them: either by marking in Firewall Mangle or by IP → Route → Rules.

I don’t have too much experience with marking Packets, I understand the concept a little bit tho.. some time ago I used it to some queues.
Can a packet have 2 routing marks? If not, I don’t get it then, what would be the point of marking packets with routing mark? wouldn’t that be something like a Load Balance to split the traffic between the two WANs? Or, How should I manage it so all traffic goes to one route or the other when the check gateway fails?

@Chupaka

It won’t break anything, and it prevents traffic to Host1 going via another route. I don’t remember the details of that bug, but I prefer to keep this rule in place

Thanks, I’ll include that!

@Chupaka

What is better: a car or a bike? I think, it depends on your task Recursive routes are “automagic”, but there are limits (like you cannot use it with interface routes, including “gateway=1.2.3.4%ether1” in case you have the same gateway IP/subnet on two uplinks.

Roger That!! I think “automagic” recursive routes will do the job, and also I did used it some years ago to failover between links to a set of servers, not the whole internet. In that time, I didn’t used routing marks tho.

Another comment:
I remember having some troubles back then with the check-gateway=ping, and if a remember correctly, what I did was that I set the pref. source field with the specific IP address where the check ping should be generated.
Just out of curiosity, and based on your comment.. I don’t know if that its an alternative to

@Chupaka

“add dst-address=Host1 type=blackhole distance=20”

Thank you again for your help!
SN