pfSense

If I understand this correctly, when a link goes physically down, freebsd will reset the routing table.
When the link comes back up the static routes need to be added again.

I think I removed the system_routing() function in the rc.newwanip at the time as it caused the filter reloads to get stuck in a loop. This was caused by apinger writing out it's configuration and immediately causing a filter reload which can be caused when a member is moving.

Seth Mos wrote:

If I understand this correctly, when a link goes physically down, freebsd will reset the routing table.
When the link comes back up the static routes need to be added again.

I think I removed the system_routing() function in the rc.newwanip at the time as it caused the filter reloads to get stuck in a loop. This was caused by apinger writing out it's configuration and immediately causing a filter reload which can be caused when a member is moving.

What I am seeing is that the link goes down, and then for some cable modems, I will get an internal ip of 192.168.100.2 but the static route to the monitor IP is not added to the routing table so now all the monitor pings are going out WAN. The system will think WAN2 is up.

In addition, the static routes for DNS entries are not added to the routing tables on link member changes.

Patch added to 7.2 / 2.0 and 8.0 / 2.0 that will prevent FreeBSD from removing the routes associated with a interface that is is down. This should prevent the monitoring ips from being removed, etc ensuring that we can keep correct track of links state.