After WAN fail(over), WAN doesn't come back
-
I'm not sure what is going on here, as this worked until just a couple of weeks ago.
Long ago I set up failover between 3 WANs. Since then I got rid of one of the WANs (I mention this part because it seems to have occurred at the same time, whether it is correlation or causation I don't know yet) and now I have 2 WANs. Failover and all my route rules all work fine. But the situation is that when one WAN comes back and is available, my pfSense firewall continues to see that WAN as failed due to packet loss. If I reboot pfSense, both WANs start working again.
Also, even more strange, when the secondary WAN is down, the primary (for my desktops/laptops anyway) is slow. I don't see any reason why the failure of the secondary WAN would cause the primary to slow down, but it does.
Let's see if I can provide all the info you need...
Primary is weighted as "1", secondary is weighted as "2", again for the LAN serving my desktops/laptops.
I'm running version 2.6.0.release
NIC in the pfSense machine is an Intel 4 port NIC, EXPI9404PTL, and no it's not a clone, it's real
In Routing, my primary ISP is marked as the default gatewayI will also mention the same thing happens if I disconnect my primary ISP, everything fails to the secondary, but it's slow and when I reconnect the primary, it stays offline.
Anything I missed that I need to add to this description?
-
@robh-0 Nobody?
-
@robh-0 What happens if you restart the dpinger service instead?
There are situations where the pings are responding properly (do you have a monitoring IP configured?) and a dpinger bounce will help that.Are all your shared gateway rules switched to the new gateway group or did you simply update your original failover group to reflect the change?
Lastly is it a case of some but not all of the traffic is routing out WAN1 after fail-back? If so that's a states issue and they will reset when the states clear out for the WAN2 connection.