Community discussions

 
OKNET
Member Candidate
Member Candidate
Topic Author
Posts: 237
Joined: Mon Jun 22, 2015 9:22 am

Problem with inactive recursive routes

Fri Jul 12, 2019 11:34 am

As per https://wiki.mikrotik.com/wiki/Advanced ... _Scripting :

My actual routes:

0 A S comment=Failover gwa dst-address=0.0.0.0/0 gateway=10.17.13.1 gateway-status=10.17.13.1 recursive via 172.16.217.254 ether1 distance=1 scope=30 target-scope=10 routing-mark=to_WAN1
1 S comment=Failover gwb dst-address=0.0.0.0/0 gateway=10.17.13.2 gateway-status=10.17.13.2 unreachable distance=1 scope=30 target-scope=10 routing-mark=to_WAN2

2 A S dst-address=0.0.0.0/0 gateway=172.16.217.254 gateway-status=172.16.217.254 reachable via ether1 check-gateway=ping distance=2 scope=30 target-scope=10
3 S dst-address=0.0.0.0/0 gateway=192.168.1.1 gateway-status=192.168.1.1 reachable via wlan1 check-gateway=ping distance=3 scope=30 target-scope=10

4 A S comment=Failover host2gwa dst-address=1.1.1.1/32 gateway=172.16.217.254 gateway-status=172.16.217.254 reachable via ether1 distance=1 scope=10 target-scope=10
5 A S comment=Failover host2gwb dst-address=1.1.1.2/32 gateway=192.168.1.1 gateway-status=192.168.1.1 reachable via wlan1 distance=1 scope=10 target-scope=10
6 A S comment=Failover host1gwb dst-address=8.8.4.4/32 gateway=192.168.1.1 gateway-status=192.168.1.1 reachable via wlan1 distance=1 scope=10 target-scope=10
7 A S comment=Failover host1gwa dst-address=8.8.8.8/32 gateway=172.16.217.254 gateway-status=172.16.217.254 reachable via ether1 distance=1 scope=10 target-scope=10

8 A S comment=Failover virtualhost1gwa dst-address=10.17.13.1/32 gateway=8.8.8.8 gateway-status=8.8.8.8 recursive via 172.16.217.254 ether1 check-gateway=ping distance=1 scope=10 target-scope=10
9 S comment=Failover virtualhost2gwa dst-address=10.17.13.1/32 gateway=1.1.1.1 gateway-status=1.1.1.1 recursive via 172.16.217.254 ether1 check-gateway=ping distance=1 scope=10 target-scope=10
10 S comment=Failover virtualhost1gwb dst-address=10.17.13.2/32 gateway=8.8.4.4 gateway-status=8.8.4.4 recursive via 192.168.1.1 wlan1 check-gateway=ping distance=1 scope=10 target-scope=10
11 S comment=Failover virtualhost2gwb dst-address=10.17.13.2/32 gateway=1.1.1.2 gateway-status=1.1.1.2 recursive via 192.168.1.1 wlan1 check-gateway=ping distance=1 scope=10 target-scope=10

12 ADC dst-address=172.16.1.0/24 pref-src=172.16.1.1 gateway=bridge1 gateway-status=bridge1 reachable distance=0 scope=10
13 ADC dst-address=172.16.217.0/24 pref-src=172.16.217.29 gateway=ether1 gateway-status=ether1 reachable distance=0 scope=10
14 ADC dst-address=192.168.1.0/24 pref-src=192.168.1.200 gateway=wlan1 gateway-status=wlan1 reachable distance=0 scope=10


Why route 10 is INACTIVE (thus main route 1 , wan2 related) despite 8.8.4.4 is recursively active as per route 6 ???

Image
 
sindy
Forum Guru
Forum Guru
Posts: 3811
Joined: Mon Dec 04, 2017 9:19 pm

Re: Problem with inactive recursive routes

Sun Jul 14, 2019 12:49 pm

Note that all the /32 routes have the default value none of parameter check-gateway, which means that it is enough for these routes to be deemed active that their gateway interfaces were up (and if I remember right, changing it to ping makes no difference when the gateway is in a connected subnet). The routes higher in the recursive hierarchy check the availability of their "gateway" (actually, a monitored IP address) by pinging it every 10 seconds, so they notice when the monitored IP address is actually inaccessible via the recursively found gateway.
Instead of writing novels, post /export hide-sensitive. Use find&replace in your favourite text editor to systematically replace all occurrences of each public IP address potentially identifying you by a distinctive pattern such as my.public.ip.1.

Who is online

Users browsing this forum: No registered users and 69 guests