Multi-WAN failover trigger not honoring trigger selection

[pjw]

I currently got my multi-WAN configuration running.  Each WAN uplink is to a separate ISP, and have separate physical ports on the box.

I have selected "Member Down" as the trigger in the gateway group to fail over to the second WAN.  What is happening is my latency spikes on my one gateway when it's saturated/under load, and it eventually fails over due to high latency (blow past the high water mark).  But the packet loss is still 0.0% as reported by OPNsense.  It seems no matter what I set it to, it is always marking the gateway failed due to high latency.

Anyone else have thoughts on how to tweak this to truly trigger on packet loss?

[tracerrx]

System=> Gateways=> Single=> Your Gateway Edit => Advanced

Click "Help" and it will show you the defaults for latency and packet loss.  You can tweak all the values here.

[pjw]

System=> Gateways=> Single=> Your Gateway Edit => Advanced

Click "Help" and it will show you the defaults for latency and packet loss.  You can tweak all the values here.

Hi tracerrx, thanks for the reply.

I have gone into those menus prior to posting and tweaked some of these values.  However, the issue is my Gateway stats showing RTT, RTTd, and packet loss, is showing 0% loss.  The trigger to mark the gateway down is set to Member Down in the Multi-WAN config.  But the firewall is marking the interface down when the latency spikes very high due to link saturation, however packet loss is still showing 0%.

Does Member Down mean something different than total packet loss?