I ahve the same scenario in having a primary ISP and a secondary ISP for backup (much slower) and am just starting to program and eventually move to the HEX unit (in test/developmnet)
Does the Mikro hex series have the concept of trunks?
In other words, one defines the interfaces within a trunk ie wan1 and wan2, then defines the type of load balancing between the interfaces in the trunk.
be the load balancing option of Failover or sometimes called active/passive, load sharing by connection, load sharing by percentage of load etc…
Then when making routing rules one can say.
All traffic from the office staff, next hop is the trunk,
All traffic from Peter, next hop is wan1
All traffic from server, next hop is wan2
etc…
All those devices requiring access 24/7 (failure occurs in WAN1 get routed to WAN2).
All those devices that are perhaps transient and get specific WAN flow to wan1 but no need for failover…
All those devices (perhaps email traffic) that need specific WAN flow to wan2 …
2-ISP: dst-adress=0.0.0.0/0 gateway=2-ISP (probably the name is pppoe-out1) distance=2
This is enought to get failover, but in my case, I optimized this using NETWATCH to check (each 10s) if 1-ISP is UP, if don’t, it will disable my route (defined above) from 1-ISP, when it’s UP, it will be enable again.