We have found that using SpeedFusion bandwidth bonding works great when the two LTE connections are fast, but when one LTE connection is slow it slows the entire bond down significantly.
What we would like to be able to do is setup two PepVPN connections to two different datacenter instances of FusionHub. We would set the Outbound Policy to load balance and include both PepVPN connections in the load balance configuration (and remove WAN connections, so all traffic is routed over the PepVPN connections).
That way a slowdown on one LTE provider would only affect some traffic and not all, but we would still be able to ensure all traffic passes over the PepVPN tunnels.
Basically we just want the option to include PepVPN tunnels in the load balance outbound policy. At preset they can only be used in the priority and enforced outbound policies.
Is this possible via a workaround or a planned feature?
This parameter may be found among the VPN Profile settings. It was implemented after the original post you followed and helps deal with the real-world issue of rapidly changing performance of WANs.
Hi Rick,
thanks for your info.
I have used this method, but it uses (CMIIW) the concept of Aggregating multiple wan-to-wan links as one higher throughput tunnel (we can’t determine the WAN load for the tunnel ourselves). Our customer wants to determine the connection load for PEPVPN, for example WAN 1 has a load of only 5 and WAN 2 has a load of 8.
