Using routes to force a connection

I have 2 WAN feeds.

I have fail over set up… where I just got stuck was the modem was still up so the system did not fail over to the second connection.

So I need 2 things to work.

I need the router to figure out…
Hey Ether-1 doesn’t actually go anywhere. Lets Flip to Ether-2.

Next up…

I have a web based power switch with autoping.
I love this thing… I have it set up at every Single WAN connection job to ping 8.8.8.8 every minute. If it fails to reach 8.8.8.8 5 times. It cuts the power to the modem and waits for 60 seconds. Then it powers the modem back on and resumes checking if it still can’t reach 8.8.8.8 it will repeat this after 5 missed pings.

So I need a way to force any query to 8.8.8.8 to only go out one interface… Ether-1
I figure a route would take care of that?
Or do i have to use Mangle first and then a route?

Input would be great.

Thanks

Okay to solve your first issue… I use these two filter two solve two of my issues. Both of these seem to be your first issue..

Rule 1 adds the check gateway function to a dynamic route
Rule 2 drops the route if it gets an IP within range 192.168.100.0/24… Normally if the modem has connectivity it is a public address. If it does not get a public address it assignes itself a 192.168.100.x address that goes nowhere so the rule drops it. (Naturally you will need to tweak this IP range for your modem settings)

/routing filter
add action=accept chain=dynamic-in disabled=no invert-match=no set-bgp-prepend-path=“” set-check-gateway=ping
add action=discard chain=connected-in disabled=no invert-match=no prefix=192.168.100.0/24 set-bgp-prepend-path=“”

Sorry didn’t see this for a while.

Interesting idea.

The issue is more when the cable modem locks up… it doesn’t always reboot and go back to that address of 192.168.100.1.

but I think I see some applications where something like that might be a building block. Thanks