pfSense » pfSense Plus

I can reproduce this for the most part. I set WAN1 for the Tier1 interface and WAN2 for the Tier2 on a 4100 (identical ports to the 6100). The the gateway group's Trigger Level is set to Packet Loss and the Tier1 GW's high packet loss threshold at 100%.

I can physically unplug the wire from WAN1 and:
- Status > Gateways then immediately shows Pending when I refresh the page.
- Status > Interfaces shows No Carrier because it's disconnected.
- System > Routing > Gateways shows it's failed over to the Tier2 gateway.
- Diagnostics > Routes shows the default route is now out WAN2.

If I log into the switch on the other side the wire from WAN1 and disable the VLAN on the switch port, WAN1 has no working upstream route but does still have a physical link:
- Status > Gateways will take a minute or so to reach "Warning, Packetloss: 100%" and then Pending, though showing Pending was inconsistent.
- Status > Interfaces shows the interface is up (expected since it's still plugged in)
- System > Routing shows it's NOT failed over and the Tier1 gateway is still the system's default gateway.
- Diagnostics > Routes shows the default route is still out WAN1.
- If I then unplug WAN1 and plug it back in, it fails over to Tier2 as default gateway and the default route changes to via WAN2. Those changes persist until I restore the VLAN back to the switch port. Within about 10 seconds, the firewall then fails back to the Tier1 gateway.

If I set the high loss threshold to 99% and unplug WAN1, I get the same result described above. No change. The second exercise however quickly fails over to Tier2, the default route is out WAN2, and Tier1 moves to "Offline, Packetloss: x%" which eventually climbs to 100%.

I see the reason for opening the report but as a side note, if you want failover when a member is detected completely down there's a Member Down trigger level in the gateway group settings for that circumstance. No need to adjust the loss thresholds.