1. Introduction

1.1. What InControl 2 Is

InControl 2 is Peplink's cloud service for managing Peplink and Pepwave devices from one website. Routers, access points and switches are managed from a single sign in rather than device by device.

InControl 2 provides:

  • Configuration of many devices at once. Settings, firmware and policies are applied to a whole group, or only to devices with selected tags. Automatic roll back can return a device to its previous configuration if it loses contact with InControl 2 after a change. See 13 Settings (Group Level) and 8 Network Settings.
  • A single view of all devices. Device status, WAN state, usage, clients and events are shown together. For example, devices with a priority 1 WAN down can be listed across every group from one device list. See Organization Settings, 9.2 Device Management (Organization Level).
  • Remote access. Remote Web Admin opens a device's own settings page through InControl 2, including devices behind carrier NAT. See 16.5 Remote Web Admin.
  • Alerts. Notification profiles send e-mail, Pushover or webhook alerts for all devices in a group or only those with selected tags, with a silence period for quiet hours. See Settings (Group Level), 13.7 Notifications.
  • Cellular and Starlink data cost control. SIMs or Starlinks are pooled against a quota, with alerts as usage builds and throttling or blocking of user traffic once the quota is exceeded. See 4 Organization Reports.
  • An audit trail. The Operation Log records each administrator action with the page, the old value and the new value, and each sign in with the role, sign-in method and source address. See Settings (Organization Level), 9.7 Operation Log (Organization Level).
  • Role based access and bulk provisioning. Roles range from full administrator to viewers who see dashboards only, for the whole organization or for a single group. Devices are added from a CSV list of serial numbers and names, tagged on arrival, into new groups that copy an existing group's settings. See 9 Settings (Organization Level) and 13 Settings (Group Level).

1.2. What It Covers

Peplink describes InControl 2 in five areas. The table shows where each area is covered in this manual.

Area

What it means for you

Where in this manual

Zero Touch Configuration

Send settings and firmware to many devices at once, including SSIDs, firewall rules and policies

13 Settings (Group Level), 8 Network Settings, 7 Wi-Fi AP

SD-WAN Provisioning

Build SpeedFusion VPN links between sites with a guided setup

5 SpeedFusion VPN

GPS Fleet Management

See devices on a map, with vehicle speed and route history

Device Level Management, 14.1.13 The Location Map (route playback, GPX export), Group Dashboard, 10.1.6 The Map

Network Troubleshooting

Alerts, bandwidth and WAN quality charts, event logs and Remote Web Admin

13.7 Notifications, 11.11 Event Log (Group Level), 11.2 Device Reports (Group Level), 15.6 WAN Quality Reports, 15.9 Event Log (Device Level), 16 Device Level Tools

Mobile App

Monitor your organizations from a phone, with push notifications

Not covered, apart from the Mobile App Notifications note in Settings (Group Level), 13.7.7 Mobile App Notifications. This manual covers the website only

1.3. Before You Start

A device appears in InControl 2 only when the following requirements are met:

You need

Details

A Peplink ID

The account used to sign in. See 2.3.1 Creating a Peplink ID

An organization

A new Peplink ID is prompted to create one first. See 2.5 Creating an Organization

A web browser

Any current mainstream browser. No software is installed

A supported device

Peplink Enterprise Routers, Enterprise Mobility, Mobile Routers, Multi-Orbit Routers, Enterprise Branch Routers, Cellular Modems & Adapters, and Wi-Fi & PoE Switch products, plus FusionHub (Solo, Essential and Pro). Each product page confirms support for that model

Warranty or subscription

The device must be under warranty or covered by a subscription. A device whose SKU ends in -PRM must have an active PrimeCare or PrimeCare+ plan, which includes InControl 2 access

Network access

The device must be able to reach the internet on TCP port 5246 and UDP port 5246, and resolve names and set its clock

Both ports must be open, outbound from the device. A firewall that only allows normal web traffic (TCP ports 80 and 443) blocks InControl 2. TCP port 5246 is also the port used by Remote Web Admin and InTouch. If UDP port 5246 is blocked, the device shows as offline. No inbound port needs to be opened at the site.

The device also needs outbound DNS (UDP and TCP 53), to resolve Peplink host names, and NTP (UDP 123). The connection to InControl 2 is secured with certificates, and a device with an incorrect clock cannot validate them. Peplink publishes its cloud server addresses as the Peplink Cloud Service Public IP Address List, also available as ip_addresses.json. These addresses change as the service scales. Where the firewall supports it, allow outbound traffic to *.peplink.com by domain instead.

When warranty or subscription lapses, the device continues to route traffic and its local Web Admin remains available, but InControl 2 no longer manages it:

  • The device shows as offline in InControl 2, even while it has internet access.
  • Remote Web Admin through InControl 2 fails, for example with Connection timeout.
  • Renewal restores management once the device can reach InControl 2 again. Current expiry dates are shown on Organization > Organization Settings > Subscriptions and Licenses (9.9 Subscriptions and Licenses).

For devices released after this manual was written, see the current supported model list on the InControl 2 product page and the InControl 2 service page.

1.4. Cloud or Appliance

InControl 2 is available in two forms:

Form

Where it runs

Best for

InControl 2 cloud

Hosted by Peplink on Amazon Web Services in the United States

Most customers. No installation or maintenance

InControl 2 Virtual Appliance (ICVA)

On your own server

Organizations that must keep their data on their own systems

This manual covers the cloud service. The appliance has separate updates and setup, and some of its figures, such as data retention, differ. Peplink publishes a separate InControl 2 Appliance Setup Guide for ICVA.

1.5. Which Version This Manual Describes

This manual describes InControl 2 version 2.14. The version in use is shown at the bottom of every page.

This is version 1.0 of the manual, published November 2026.

1.6. How to Use This Manual

The chapters follow the layout of InControl 2. Every setting belongs to one of three levels: the organization, the groups inside it, and the devices inside each group. The chapters broadly run from organization to group to device. Use the table below to locate a chapter.

For day-to-day operational tasks, see 17 Common Tasks. It lists common tasks with the screen to use for each, and a troubleshooting procedure for an offline site.

#

Chapter

What it covers

2

Getting Started

Signing in, your first organization, group and device

3

Organization Dashboard

The overview of your whole organization

4

Organization Reports

Reports across every group

5

SpeedFusion VPN

SpeedFusion profiles and status, at all three levels

6

eSIM and SIM Management

eSIM profiles, SIM pools and data plans

7

Wi-Fi AP

SSIDs and radio settings, at all three levels

8

Network Settings

WAN, firewall, outbound policy and other group network settings

9

Settings (Organization Level)

Users and roles, the Operation Log (audit trail), firmware policy, subscriptions and organization-wide settings

10

Group Dashboard

The overview of one group

11

Reports

Reports for one group

12

Clients

Connected clients, for a group or a device

13

Settings (Group Level)

Device lists and bulk actions, notifications (alerts), report e-mailing, firmware policy, Bulk Configurator and every other group setting

14

Device Level Management

One device's details and settings

15

Device Reports

Reports for one device

16

Device Level Tools

Remote Web Admin, Web CLI and other tools for one device

17

Common Tasks

A task index, a troubleshooting flow for a site that is offline, a checklist for changes to many devices and a glossary

SpeedFusion VPN and Wi-Fi AP appear at all three levels, so each is covered in a single chapter.

Conventions:

  • Menu paths follow one pattern. The first word is the level: Organization, Group or Device. Next is the item on the menu bar, then the entry in its dropdown. For example, Group > Settings > Notifications means: open the group, select Settings on the menu bar, then Notifications in its dropdown. The three levels are explained in 2.1 How InControl 2 Is Organized.
  • Buttons and fields use the exact names shown on screen.

What this manual does not cover: the InControl 2 API, the mobile app, and the ICVA appliance. The manual is written for organization administrators of the cloud service, and screens are shown as an organization administrator sees them. Role permissions are described under Administration in Settings (Organization Level) (9.8.1 Administration) and in Settings (Group Level) (13.17.2 Administration), but screens are not shown for each role.

About the screenshots: organization, device and user names, serial numbers, SIM and Starlink identifiers, MAC addresses and organization codes in the screenshots are placeholders, and public IP addresses are masked as xxx.xxx.xxx.xxx. The same name refers to the same device in every screenshot.

On this page