Peplink Integration
If your field encoders connect through Peplink routers (bonded cellular, typical for ENG/live-event bonding), OmniBridge can pull each device's live status straight from your Peplink InControl2 account — WAN connection status, real cellular signal strength, PepVPN/SpeedFusion tunnel health, and which local devices are connected — right alongside your routing matrix. It can also automatically figure out which Peplink device a given source is coming through, without you having to tell it by hand every time.
This is a licensed add-on. See Pricing for current cost — it's priced the same as the other protocol add-ons and included automatically in the Pro bundle.
Setup
You'll need an InControl2 account with API access and a Client ID/Client Secret pair — these come from Peplink's InControl2 portal, not from OmniBridge. Once you have them:
- Open the Setup tab.
- Find the Peplink InControl2 credentials section and enter your Client ID and Client Secret.
- Save. Once saved, the page shows "Connected as
<Client ID>" instead of the entry form — a "Change" action reveals the form again only when you actually want to change credentials.
A new Peplink tab appears in the main navigation once credentials are saved and valid.
What you see on the Peplink tab
Every Peplink device on your InControl2 account shows up as its own card:
| What | Details |
|---|---|
| WAN status | Per-interface online/offline status for every WAN this device has. A cellular WAN that's currently Standby (not the active link) still shows if it's carrying real signal data — it isn't hidden just because it's not the primary connection right now. |
| Cellular signal metrics | RSSI, SINR, RSRP, and RSRQ, straight from InControl2, for any WAN that's a cellular modem. |
| PepVPN tunnel status | Per-tunnel RTT, cumulative TX/RX bytes, packet loss, and tunnel state (only tunnels that are actually ACTIVE are shown — a Standby tunnel reports every field as zero, which isn't useful to display). |
| Connected clients | A collapsible list of the device's currently-connected LAN clients (manufacturer, MAC, IP, connection type). If a client has a web admin UI reachable on port 80 or 443 — checked live from your own browser, not the server — its entry becomes a link that opens it in a new tab. |
Automatic source matching
Each Peplink device card has an optional CIDR field — set it to that
device's local subnet (e.g. 10.99.3.0/24). Once set, OmniBridge
automatically matches any SRT/UDP source whose connecting IP falls
inside that subnet to that device: the source's tile on the
Operate tab shows a "via <device>" badge, and the matching
device's own Peplink-tab card shows which source(s) it's currently
serving. No manual per-source configuration needed once the CIDR is
set — this re-evaluates on every new connection, not just once at
setup.
A device with no CIDR entered is simply never matched against any source's IP — this isn't an error state, it just means automatic matching is off for that device until you set one.
Troubleshooting
| Symptom | What's going on |
|---|---|
| Peplink tab doesn't appear | Either credentials haven't been saved on the Setup tab yet, or this license doesn't include the Peplink add-on — check Pricing. |
| A device shows no signal metrics | Only cellular WANs report RSSI/SINR/RSRP/RSRQ — a wired/Wi-Fi WAN genuinely has nothing to show there, that's not a bug. |
| No "via <device>" badge on a source that really is behind that device | Double-check the device's CIDR field actually covers the source's real connecting IP — if the source is itself behind NAT/a VPN, the IP OmniBridge sees may not be the LAN IP you expect. |