WAN1 (StarLink) is set up as the primary and WAN2 (DSL) my backup on a Peplink Balance 2.
This works well, except I would like for all of the traffic from a specific VLANB to use WAN2 (backup), to keep low priority traffic off the main WAN1. However, when I assign an Outbound Policy (Enforced) to the VLANB subnet, it does not work unless WAN2 is also set to be Primary. I can see via Real Time Stats that when WAN2 is primary, the VLANB properly routes through WAN2, but when WAN2 is Secondary then no traffic is sent.
I also tried setting both WANs as Primary, but assigning low bandwidth to WAN2. This seemed to slow down the connection for VLANA, though, and real time stats show traffic flowing through WAN2 from VLANA which are not meant to use WAN2 (except in case of backup).
Is the correct way to achieve this to create a 2nd outbound rule? Perhaps an Overflow rule for VLANA so it uses WAN1 until saturated? That doesn’t seem to capture my requirement, though. To be clear, I’d always like VLANA to use WAN1 and VLANB to use WAN2… unless WAN1 is down, in which case VLANA should fall back on WAN2.