QoS inside the PepVPN is also a critical requirement we have. We are using a single primary WAN site-to-site with one failover WAN (cellular). We need to prioritise TCP traffic above UDP going across that VPN regardless of whether the primary or the failover WAN is being utilised. (primary and failover WANs will not be used simultaneously).
I’ve had no luck getting the outbound policy to work with multiple sub-tunnels. If I create two sub-tunnels in the same PepVPN profile (at both routers) they will establish fine. I then, for simplicity, put in an enforcing outbound policy to push all outgoing data through the second sub-tunnel (not the default), however no traffic will flow across anything but the default sub-tunnel. I assume this is because we only use 1 physical WAN at a time, is this expected behavior? Will this only function with multiple simultaneous WAN connections? We are utilising MAX BR1 ENT modems running 7.1.1 firmware.
Regardless, even if it did work, I don’t see how outbound policies can prioritise the data over a single WAN, unlike QoS within PepVPN should?
Will the update coming with 7.2.0 work with our scenario above? when is the release of 7.2.0 slated for?