Manually Prioritise Speedfusion Tunnel

We are currently using Peplinks to connect multiple sites for a company into their datacenter. The Datacenter Balance then uses OSPF to advertise the sites IP addresses from the speed fusion tunnels sites to the rest of the network (there will be potentially over 120 remote sites). Although we have the datacentre pair in HA, we have been asked to provide failover to an additional datacenter using a separate Speedfusion tunnel. This again uses ospf for routing. However, although we can prioritise via outbound policy which speed fusion tunnel the traffic goes down, as both tunnels are up, the traffic from one speed fusion tunnel is advertised into the other and then creates incorrect routing at the backup datacenter. (I have included a diagram). If we could prioritise/cost which tunnel to use and the secondary only came up if the primary was down, this would stop any potential transit issues and also resolve the external OSPF routing issues.
The customer uses multiple WAN links but we cannot send one to datacenter 1 and then the other to datacenter 2 as they want to make use of all wan links for the speed fusion tunnel in use.

SpeedFusion routing is automatic, however by clicking on the “?” to the right of the rules table you can choose expert mode and place the rule above normal SpeedFusion routes.


We have requested this feature some time ago, in our case we use Layer 2 Speedfusion and any rules or routings do not apply!
Hopefully, if by the time we don’t get tired of waiting and switch to another brand, someday Peplink will listen to our requests.

Charris Lappas

Hi Charris,

Engineering team is reviewing for L2 SpeedFusion. Stay tuned.

I got your idea, this is in fact DR site support for PepVPN w/ SpeedFusion. We have received similar requests and are giving this feature more priority, please stay tuned.

Implementing a backup site relying on Layer 2 PepVPN w/ SpeedFusion is not that feasible, for example, when the primary link failed, and connection swapped to the backup L2 site, all the devices running on Layer 3 using IP will need to wait until their entry in ARP table expire and renew the MAC address after that. Also some other issues may arise after the failover happens on Layer 2.

What is the expected use case for this? as you have said this is requested some time ago, could you please share the forum link for us to get a better overview of the request?

This is exactly what we want to have all WAN links forming one tunnel and if the endpoint fails we can them create a speedfusion tunnel to a different endpoint therefore forming the relevant tunnels and the correct routing. It is for DR. Would we have timescales on this as my Customer was promised this by the Local Peplink sales 2 years ago.

We have this feature targeted to next major release after firmware 6.2, however there is no exact date of release yet. Thank you very much for your understanding.