Page 1 of 1

Recursive Failover with public IP check

Posted: Tue Oct 08, 2019 8:04 pm
by danihill
Good evening all,

I am about to configure Recursive Failover on my CCR with dual WAN. The reason I am making this configuration is because my primary ISP connection has many hops before the main router and the gateway i use is not the gateway of the main router. This means if any link between my gateway adn the main router fails i do not detect the drop with a standard ping check.

This is what I am planning to do:

/ip route
add dst-address= gateway= scope=10 comment="Validate Primary"
add gateway= distance=1 check-gateway=ping comment=Primary
add gateway= distance=2 comment=Secondary

By doing this it should check my gateway by checking if the internet is available by doing a ping to Google DNS server.

This is all good, but does anyone know how many pings have to be lost before it disables the gateway? I am worried that sometime you can loose a ping to google and i dont want it to be changing over every time one or two pings are lost to Google DNS...

Re: Recursive Failover with public IP check

Posted: Tue Oct 08, 2019 9:17 pm
by Sob
check-gateway (arp | ping; Default: "") - Periodically (every 10 seconds) check gateway by sending either ICMP echo request (ping) or ARP request (arp). If no response from gateway is received for 10 seconds, request times out. After two timeouts gateway is considered unreachable. After receiving reply from gateway it is considered reachable and timeout counter is reset.

Re: Recursive Failover with public IP check

Posted: Wed Oct 09, 2019 10:12 am
by danihill
Many thanks.