pfSense

Subject should say "Wan Fail Back"

Changing anything in the web interface to do with gateways makes the system failback but this is a manual process.

Also, the Wan interface is set as the default in the web interface before testing.

Could be the same thing I see on my wan2. When I look in /tmp/rules.debug gateways hasn't recovered. In a shell script I reload filters with /usr/local/sbin/pfSctl -c 'filter reload' to correct it.

I see in the logs "Filter Reload" when wan comes back up. I've also ran the PfSctl -c 'filter reload' manually and it will not switch back to tier1.

More detail is that I have wan set as default, priority is 1 and it is tier1.

When I stated that it will fail back with dhcp that was with me pulling the cable. If I leave the link up and down the monitor ip then it will not come back up.

For anyone watching this bug report, i've created a workaround until it gets officially fixed.
create a file /root/failback.php with the following code:
include("/etc/inc/system.inc");
include("/etc/inc/interfaces.inc");
include("/etc/inc/gwlb.inc");
include("/etc/inc/util.inc");
include("/etc/inc/config.inc");
system_routing_configure("wan");
exec("/usr/local/sbin/pfSctl -c 'filter reload'");
?>

then in /etc/inc/gwlb.inc
change the line:
command off "/usr/local/sbin/pfSctl -c 'filter reload'"
to
command off "/usr/local/bin/php /root/failback.php"

Correct me if I'm wrong, but this appears to only resolve the issue of bringing the WAN back up if you physically unplug the cable and plug it back in. This doesn't solve the issue if apinger detects the WAN is down and fails over.

If apinger marks a gateway as down as soon as it is up it will mark it as availble and the pool will switch to it for sure.

I have not seen any report of this not working and if you claim so please provide the system logs on this.
Also a description of how your system is setup.