Outbound policy management in InControl2

Outbound policy management in InControl2 allows you to upload a configuration file saved from a device, view or optionally change the rules’ schedule, and then apply these policies to one, or multiple devices.

To configure the Outbound Policies:

Configure the outbound policies on the web admin interface of one of your Peplink routers.

When applying rules to sets of devices only WAN connections with matching names (eg WAN 1) will be active.

For example, to apply a rule that forces certain traffic to “WAN 1”, each selected device also needs a WAN connection called “WAN 1”.
For devices without a “WAN 1” the rule will be excluded.

The same logic applies to policies applied to PepVPN profiles.

Download the configuration file from the router containing the Outbound Policies that you want to apply to other Peplink routers in your organization.

In the correct InControl2 organization select: Group settings > Network settings > Outbound Policy.

Tick the box to Manage the Outbound policies on Balance and Max devices.

Click the “Import Rule Set from Configuration File” button.

A window will pop up showing all the Outbound policies available in that configuration file.
This will create a new Outbound Policies Rule Set when saved.
Before saving select the options to enable or disable individual outbound policies.
Select if the rule set should be applied to All Balance and Max devices or a selection of your devices using ‘tags’.

After being saved the rule set will be available from the main Outbound Policy section in InControl2.

This feature is available in InControl since version 2.5.1


Hi Erik!

Thanks for detailed information.

Any suggestion when using both SpeedFusion Configuration and Outbound Policy through IC2 and with the need to enforce specific traffic into a PepVPN?

I mean… We have star topology (FusionHub is the hub and BR1s are endpoints). We configured SpeedFusion tunnels using IC2. We also want to use IC2 to configure outbound policies for all the end points to enforce specific traffic into the pepvpn.

The issue is that the Outbound Policy configuration through IC2 asks for the PepVPN tunnel name. But the PepVPN name is automatically/dynamically assigned by the SpeedFusion profile and each tunnel has its own pepvpn name.

Best regards!

1 Like

Hi Hector,

The PepVPN tunnel name is automatically assigned a default value during creation, but you can change this value under the “Advanced Link Settings” in the PepVPN management wizard.


Thanks for your answer James!

Actually, I was looking for even an easiest way :slight_smile: maybe an option to name all the remote tunnels with the same name at once? This way we can add an Outbound Policy Rule Set to send traffic into the PepVPN

I understand that this might sound like a trivial request… but people always want easier :slight_smile: And as Distributor, we need to hear every request.

1 Like