We’ve been using Peplink Balances to connect multiple sites in a hub and spoke configuration and for the most part it works great but we have some issues that I’m hoping someone can provide a suggestion for resolving.
Most of our sites have an MPLS circuit that we do not inculde in the PEPVPN tunnel. The reason we do this is because real time traffic like RDP and VoIP seem to have issues when sent through the tunnel even though we have QOS enabled on the Balance routers. Therefore, we’ve been using outbound policies to route the critical traffic over the MPLS network where we can use the providers QOS. This works for us until there is outage on one of the MPLS circuits. We had an issue today where the MPLS circuit at the datacenter bounced which dropped our user’s RDP sessions. The outbound policy rules we use are set for priority and have a the secondary set to the PEPVPN tunnel but this doesn’t work since the Balance doesn’t monitor a WAN link if it’s not included in the tunnel so the traffic doesn’t fail over to the next WAN. We would ideally like to figure out a way to not drop those real time sessions.
In the past I have suggested that Peplink add the ability to create outbound policies within the Peplink tunnel but I don’t really see that being implemented any time soon. Does anyone else have a suggestion for resolving this problem?