QoS on Speedfusion

[KPS]

Hi!

I found some old posts about the limitations of Speedfusion and QoS.
Can you tell me something about the status of that feature?

If I classify “Remotedesktop-application” as “high-priority”: Will it have priority in the PepVPN/SpeedFusion-tunnel?

Thank you for your advice

KPS

[Erik_deBie]

We have introduced the possibility to configure multiple Speedfusion(sub-) tunnels between two Peplink routers with different profile settings (WAN priorities, WAN connections used).
After configuring these tunnels you can configure outbound policies to prioritize traffic.

Outbound policies within a PepVPN or SpeedFusion tunnel

Outbound Policy for SpeedFusion Multiple SpeedFusion Tunnels Between two Locations One of the new features from Firmware 7 onward is the ability to create outbound policies within a PepVPN or SpeedFusion tunnel (further referred to as SF tunnels in this document). With this feature, you have even more control over the way your network traffic is prioritized and routed. [image] Until now you could create one SF tunnel to a remote location, but with this new feature you can essentially create …

[KPS]

@Erik_deBie

We have introduced the possibility to configure multiple Speedfusion(sub-) tunnels between two Peplink routers with different profile settings (WAN priorities, WAN connections used).

Hi Erik!

Thank you for your answer. I have already used that feature, but how can I priorize traffic like RDP-traffic with multiple tunnels? I can just distribute sessions over the tunnels.

[Erik_deBie]

Hi KPS,

It depends a bit on your configuration if the desired configuration is possible.
This feature was created having in mind that we have the ability to mix and match WAN connections used in the PepVPN profile.

If you have multiple WAN connections (WAN 1, 2 and 3, with WAN 1 being the most reliable, fastest connection and WAN 2 and 3 slower lines used for redundancy) you can create seperate PepVPN profiles that use different WAN connections.

For example:

PepVPN profile 1: uses WAN1 with the highest priority and WAN 2 as backup
PepVPN profile 2: uses WAN 2 with the highest priority and WAN 1 as backup
PepVPN profile 3: uses all WAN connections that are available

If you have a situation as above you could create an outbound rule for traffic matching TCP port 3389 and UDP port 3389 to use PepVPN profile 1, and other traffic could use another profile.
Traffic that you want to prioritise will then use your faster, more reliable WAN connections and you could use slower WAN connections for other traffic with less priority (backups or print jobs for example).

This is only beneficial in situations where you use multiple WAN connections, the more WAN connections you have available, the more options it gives you.
It doesn’t work in the traditional sense of QoS where you can send different traffic simultaneously through the VPN tunnel and add a different priority to each type of traffic.

[KPS]

Hi!

Thats nice, but that doesn’t help me in most cases. Having only one “high-quality” connection in most branch-offices, i would need the feature to priorize the traffic through the tunnel dependent on their “service” or “source/destination”.

[jfickeis]

Hi,
is there any plan to implement the traffic Priorization within the Speedfusion-Tunnel in the near future?
we also require this feature.