I have the following configuration: my ISP mounts an antenna on my roof and goes with UTP to his router on my rack. This router is my gateway, so I connect to it from my my Mikrotik with an UTP patchcord.
The problem is, that what usually fails is the wireless connection between my ISP’s router and the world, and not between Mikrotik and ISP’s router.
So when the wireless connection fails, the local router would always reply to pings, so Mikrotik thinks the gateway is reachible (which is in fact true…).
In this situation, how can I trigger switching to a failover ISP if the gateway is all the time treated as “reachible”?
Best approach would be your ISP routing being in bridge mode, and you getting the public IP on your own router.
If this is not possible, simplest way would be tracerouting which your ISP router gateway, and using Tools > Netwatch to enable on Up / disable on Down your default route going through your ISP.
Sorry, forgot a crucial detail, I’m afraid I didn’t completely explain myself you’re right jarda, that way is never going to come back up…
@frytex: Don’t know how is your failover implementation, are you load-balancing or wish just to failover to a backup ISP just if main one is down?
Say your main ISP LAN ip is x.x.x.x, so that you have a default route with X metric through it.
Say your backup router is y.y.y.y, so you have another default route through it with higher metric than the previous.
What I meant was:
Locate the next hop from your ISP router by using traceroute, let’s suposse is z.z.z.z
1.- Create a specific route to z.z.z.z through x.x.x.x
2.- Add Tool >Netwatch entry:
When your ISP router next hop is unreachable, the Netwatch down script will disable the default route through your ISP router, and your backup router default route will enter active state, being used even with the higher metric.
As there’s a specific route in place to z.z.z.z, netwatch ill be able to check if it comes alive even its default route being disabled, and enable back the default route through it.
Instead of monitoring the router next hop, a non-essential access internet IP could be used.
you’re right jarda, that way is never going to come back up…