A Peplink router is only as good as the WANs you feed it — and “a WAN” is rarely just a cable from an ISP. These seven technologies are the different ways a Peplink can take in, hand off, share, or shape a WAN connection: absorbing another router’s radios, slipping invisibly into an existing network, turning a VLAN into a WAN, passing a public IP through to a firewall, routing real address space without NAT, mounting SIM cards that live in another room, and managing satellite dishes as first-class connections. Each page tells you what the option is for, how to set it up, and where it bites.
Synergy Mode
One router absorbs the WANs of others — cellular radios and all — onto a single dashboard, policy, and SpeedFusion config.
Open →
Drop-in Mode
Slide a Balance transparently into an existing network — same subnet, firewall untouched — and add bonding around gear you can’t change.
Open →
VLAN as WAN (Virtual WAN)
More WAN inputs than physical ports: fully-fledged WANs on VLAN tags, on WAN or LAN interfaces, via the Virtual WAN license.
Open →
IP Passthrough
Hand the carrier IP straight to your firewall — the Peplink becomes a transparent modem. Single IP or a passed-through block.
Open →
IP Forwarding
Route real public subnets instead of NAT-ing them — per-WAN routing modes for servers, routed blocks, and NAT-allergic designs.
Open →
Remote SIM & SIM Injector
SIMs live in the rack; routers mount them over the network. Domes, masts, and fleets without ladder-based SIM swaps.
Open →
Orbit WAN: Starlink & OneWeb
Native satellite management — dish telemetry in the dashboard, outage-tolerant health checks, and satellite+cellular bonding.
Open →
Not sure which of these fits your problem? Start with the symptom: “I need more WANs than I have ports” → VLAN as WAN or Synergy. “I can’t touch the existing firewall” → Drop-in Mode or IP Passthrough. “My servers need real public IPs” → IP Forwarding. “The SIMs are in the wrong place” → Remote SIM. “The sky is my WAN” → Orbit WAN. Or just talk to an expert.