Bug #2514
closed
static routes for monitor IPs should be removed
0%
Description
Since apinger in 2.0 and newer binds to specific IPs, and the policy routing for firewall-sourced traffic bound to a specific IP takes care of proper routing, the static routes for monitor IPs are unnecessary and should be removed.
There is a related bug in that they aren't removed when a monitor IP is changed, but that goes away if the routes aren't added at all anymore.
Updated by Peter O about 12 years ago
I have just upgraded a 2.0 Final installation to "Sun Sep 16 19:35:57 EDT 2012" and everything seems to work fine now after fixing a few upgrade issues with the gateways.
To get to the point;
I see that no static routes are added for the custom gateway monitoring IP's although the log shows the opposite:
Sep 18 09:45:27 php: /system_gateways.php: Removing static route for monitor 8.8.8.8 and adding a new route through 172.21.2.1
Sep 18 09:45:27 php: /system_gateways.php: Removing static route for monitor 212.*.*.25 and adding a new route through 213.*.*.153
Destination Gateway Flags Refs Use Netif Expire
default 213.125.186.153 UGS 0 295238 em0
46.*.*.234 link#13 UHS 0 0 lo0
127.0.0.1 link#9 UH 0 797 lo0
172.21.1.0/24 link#7 U 0 1437205 em1
172.21.1.1 link#7 UHS 0 0 lo0
172.21.2.0/24 link#1 U 0 13 bge0
172.21.2.2 link#1 UHS 0 0 lo0
212.*.*.133 link#13 UH 0 3108 pppoe0
213.*.*.152/29 link#3 U 0 0 em0
213.*.*.154 link#3 UHS 0 0 lo0
213.*.*.155 link#14 UH 0 0 wan_vi
213.*.*.156 link#15 UH 0 0 wan_vi
213.*.*.157 link#16 UH 0 0 wan_vi
213.*.*.158 link#17 UH 0 0 wan_vi
213.*.*.1 212.121.121.133 UGHS 0 2156 pppoe0
213.*.*.2 212.121.121.133 UGHS 0 2149 pppoe0
217.*.*.53 213.125.186.153 UGHS 0 151254 em0
Updated by Renato Botelho almost 11 years ago
There was an attempt to remove it in the past but seems it had side-effects (see ticket #3179 and 32a9eb1873).
I've fixed the issue of not removing it when monitor IP changes.
Updated by 
Updated by