Tier 1 gateway not switching back after failover

[gniting]

Re: Multi-WAN gateway failover not switching back to tier 1 gw after back online

The last post on the thread above is 2 months old and the thread itself is over 3 years old. The problem still persists. To summarise:

• WAN-1 is Tier 1
• WAN-2 is Tier 2 (expensive metered cell hotspot, so should only be used for WAN-2 failure conditions)
• One Gateway group with "packet loss or high latency" as trigger (http://take.ms/wQPAR)
• Default gateway is marked as this gateway group (http://take.ms/fG9m7)
• State killing on gateway failure is "checked"
• Running pfSense 2.4.4

When WAN-1 goes down, the failover happens seamlessly but even when WAN-1 is back online and this online state is known to pfSense (confirmed via pfSense dashboard), traffic keeps routing through WAN-2 until I go hit "save" somewhere (without changing anything) and then everything switches back to WAN-1.

Since WAN-2 is a metered cell connection, I'd like for it not to be used once WAN-1 comes back online. Any way to achieve this programatically because it does not look like the auto switch back to WAN-1 is a feature that pfSense supports.

[Panja]

@ibbetsion

Sorry for replying to a (almost) 4 year old topic.
But I'm having the same issue. Running pfSense v2.6.0 and having multiple VPN WAN interfaces in a failover. Once tier 1 is back online after an outtage it does not switch back to tier 1 and stays on tier 2 or 3.

Created a topic myself as well:
https://forum.netgate.com/topic/171368/multi-vpn-wan-failover-gateway-group-no-auto-switching-back-to-tier-1

Did you ever find any solution to this?

[gniting]

@panja I posted a solution, see this post.

[Panja]

@ibbetsion

Many thanks! I'll have a look at it. Cheers!

[madfuzker]

Same problem led me here. Hard to believe this is still a hack!