RF: Cellular, Antenna, Satellite, Wi-Fi & GPS

Part Twenty-Two: Cellular Fundamentals

The topic

For most Peplink deployments the primary WAN is cellular, so an engineer has to understand the mobile link itself, not just the bonding on top of it. A cellular connection is a radio link from the router’s modem to a carrier’s tower on a licensed frequency band, authenticated by a SIM. Three things decide how well it performs: the carrier and band you land on, the signal quality at the antenna, and the modem’s capability. Signal is read with three numbers worth knowing, RSRP (raw received power, the headline “how strong”), RSRQ (quality relative to interference), and SINR (signal versus noise, the best single predictor of throughput). A strong RSRP with poor SINR is a noisy site, and that is an antenna and placement problem, which is why this part and the RF part that follows are read together.

Cellular generations matter for sizing. LTE (with its device “categories,” Cat-4 up through Cat-20) is cheap, low-power, and very widely covered. Full 5G NR (sub-6 GHz for Peplink) adds high speed, low latency, and capacity at higher power and cost. Between them sits 5G RedCap (NR-Light): a mid-tier 5G aimed at telemetry, retail POS, video surveillance, and IoT, with a simpler two-antenna design, lower power and cost, and moderate speeds, while still being 5G-core-ready and slice-capable. 5G Standalone (5G SA) is a fully independent 5G core (no 4G anchor) that unlocks ultra-low latency, higher device density, private 5G, and network slicing.

Network slicing is the carrier splitting one 5G network into isolated virtual slices, each tuned for a use case (a high-bandwidth slice for video or medical imaging, a low-latency slice for real-time control, an IoT slice for thousands of sensors, a priority slice for public safety, a broadcast slice for live events). The carrier provisions a slice to the SIM; the Peplink router then rides that slice like any cellular WAN, and SpeedFusion can still bond it with others.

How it works on Peplink

A Peplink router has one or more cellular modems, and each modem takes a SIM. Peplink gives you several ways to feed those modems, and knowing them is core to the role:

• Physical SIMs in the device — the 4FF nano or 2FF mini cards, often with a primary and a redundant slot.
• SIM Injector / SIM Injector Mini — a separate appliance holding up to 8 SIMs, connected over PoE and extendable up to ~100 m, so the SIMs live in a reachable rack while the router (or a Dome) sits where the signal is. The FlexModule version scales to 56 SIMs for EPX and SDX Pro.
• SIM Extender — moves a SIM slot from one side of a device to the other so you can change cards without pulling the unit from a rack.
• eSIM — Peplink eSIM is an on-demand data-plan service: a router with an eSIM chipset connects to local networks worldwide, with remote provisioning for mass deployment and global pooled plans. BYO eSIM lets you load up to two of your own carrier eSIMs (consumer eSIMs) for quick swapping. eSIM needs firmware 8.4.0+, the device registered to InControl, an active internet connection and CarePlan, and the carrier’s activation QR/EID. The number of eSIMs a device can hold equals its number of modems, and each eSIM stores up to two profiles.
• Remote SIM / FusionSIM — SIMs served from elsewhere on the network.

You manage and monitor every SIM, physical or eSIM, from InControl, including bulk eSIM activation across many devices and switching a device between Peplink eSIM, BYO eSIM, remote SIM, and FusionSIM. InControl also has a Cellular Site Survey tool that scans and reports the cellular environment before you commit a deployment.

Why it matters

The cellular decision is usually the deployment decision. Carrier diversity (different carriers on different modems) is what makes bonding and failover real rather than theoretical, two SIMs from the same carrier share the same tower and fail together. eSIM and pooled plans turn “a truck roll to swap a SIM” into a remote click and make cheap multi-carrier backup practical. RedCap is the right, lower-cost radio for the flood of IoT and POS endpoints that do not need full 5G. And when a customer asks for a guaranteed lane (a hospital’s imaging traffic, a transit agency’s CAD/AVL), 5G SA with a carrier slice is now a real answer that Peplink can sit on top of.

Field note

Match the SIM strategy to the deployment: physical SIMs for a fixed single-carrier site, a SIM Injector for many SIMs or for Domes mounted away from the rack, and eSIM for anything mobile, global, or needing fast backup. Affordable backup is real, at the time of writing a Peplink NA/EU starter eSIM plan runs about $6.58/month equivalent (20 GB for a year). And remember the cross-reference to Part Twenty-Three: most “the cellular is slow” tickets are actually antenna, placement, or cabling problems showing up as low SINR.

Part Twenty-Three: RF & Antenna Fundamentals

The topic

Every cellular, Wi-Fi, and many satellite links ride an antenna, and the antenna and its cabling often matter more than the router. The fundamentals are few but decisive.

Gain, measured in dBi, is how much an antenna concentrates energy in a direction. It is logarithmic: roughly every +3 dBi doubles the effective power, and higher gain always means a narrower beam. Omnidirectional antennas radiate 360° in the horizontal plane, so they give a stable signal while moving and are forgiving to aim, at the cost of lower gain and picking up more noise from all directions. Directional antennas (panel, Yagi, dish) put their gain into a narrow beam, giving longer range and rejecting off-axis noise, but they must be aimed and are easily knocked out of alignment. As a rule: omni for mobile and for unknown tower directions; directional for fixed, long-range, point-to-point shots.

VSWR (Voltage Standing Wave Ratio) measures how much transmit power the antenna reflects back instead of radiating. A safe range is roughly 1.5–2.5; a too-high VSWR wastes power and can permanently damage the modem’s transmitter. Efficiency is how well the antenna actually converts RF energy to and from the electrical signal, typically 30–90% depending on band and design. These three interact: a “high-gain” antenna with poor VSWR or low efficiency performs worse than a modest, well-matched, efficient one, so a number on a spec sheet is not the whole story.

Frequency and attenuation set expectations: higher frequency attenuates faster, longer distance attenuates more, and physical surroundings (hills, buildings, trees, walls) attenuate heavily. This is why a 3.5 GHz 5G band that is blazing across a parking lot can be useless three walls deep, and why band choice and placement are part of antenna selection.

How it works on Peplink

Peplink’s connector types are worth memorizing because mixing them wastes a site visit: most indoor routers use SMA, the MBX Mini and HD4 5G MBX use QMA, and antennas and cables also come in N-Type. The antenna line spans omni and directional models across cellular, Wi-Fi, GPS, and combination units (for example the MAX series, Mobility 82G, and maritime antennas), with combination antennas housing several elements under one radome for vehicles and vessels.

The installation checklist is the part that actually fixes signal in the field. Do: keep cable runs short, use high-quality low-loss cable, minimize the number of connectors, place the antenna for a clear, unobstructed view (ideally 360° for omni, on-axis for directional), and select the right antenna for the band and use. Don’t: use passive splitters, run long or low-quality cable, stack up connectors, or bury the antenna in a blind spot. Every connector and every meter of cable is loss, and loss at the antenna can’t be recovered downstream.

Why it matters

This is the single biggest gap between an engineer who can quote SpeedFusion overhead and one who can actually make a site work. A customer with “great gear and terrible speeds” almost always has an RF problem: a high-gain omni pointed into a hillside, a 30-meter run of cheap coax, three barrel connectors, or a directional antenna 20° off the tower. Understanding gain, VSWR, efficiency, and attenuation lets you diagnose that in minutes and specify the fix, and it ties directly back to the cellular signal metrics in Part Twenty-Two.

Field note

When a link underperforms, suspect the RF chain before the router: check VSWR is in range, shorten the cable, drop the splitters, and confirm the antenna actually sees the tower or sky. For long fixed shots, a directional antenna aimed carefully beats a bigger omni. And match the connector to the model (SMA vs QMA vs N-Type) before you order, not on site.

Part Twenty-Four: Satellite & LEO Fundamentals

The topic

Satellite is now a first-class WAN type, and three flavors show up in the field. LEO (Low Earth Orbit) constellations, Starlink and OneWeb, deliver broadband-class speed and usable latency from satellites a few hundred miles up. GEO (traditional VSAT, Ka/Ku-band) sits far higher with much greater latency. And Iridium, an L-band constellation, gives low-bandwidth but truly global, weather-resilient connectivity that works when everything else, including LEO, is down.

The defining quirk of LEO for a Peplink engineer is motion: the dish roams across many satellites over the course of a day, and each handover can cause a brief drop or latency spike. On its own that breaks real-time apps (Zoom, Teams, live video) and at worst causes short outages. This is exactly the kind of impairment SpeedFusion exists to hide.

How it works on Peplink

West Networks is one of 60-plus Authorized Peplink & Starlink solution providers, and Peplink integrates LEO deeply:

• Starlink + SpeedFusion fills the roam-induced gaps by bonding Starlink with 5G/LTE (and other Starlinks), so a handover on one path is covered by another and real-time traffic stays smooth. You can scale from one Starlink to twenty, using them as primary internet, as failover behind fiber, or in a backpack/command-vehicle for go-anywhere connectivity.
• Multi-Starlink bonding reaches gigabit class: a mining customer (Heathgate Resources) bonded multiple Starlinks to a Peplink router with a SpeedFusion tunnel to a FusionHub in their corporate cloud and reached ~1.3 Gbps down / 250 Mbps up for 250+ workers; HYROX Chicago 2025 bonded six Starlinks with cellular failover for a live event with zero downtime; Royal Caribbean uses it at sea. SpeedFusion Boost (Part Eight) is what keeps a slow link from dragging the bond down on these high-latency paths.
• InControl manages the constellation: native Starlink support shows status and controls in Device Details, lets you Stow/Unstow by geofence, ignore obstruction outages so a momentary block doesn’t flap the WAN, track Starlink events in WAN Quality Reports, and group multiple units under shared Starlink Data Pools (a shared monthly data limit at the group/org level, firmware 8.5.2+). Firmware 8.6.0 adds native OneWeb support with the same kind of visibility.
• Iridium is the last-resort backup: when LEO, cellular, and terrestrial all fail, Iridium Certus carries the traffic that absolutely must get through, alerts, SCADA telemetry, GPS positions, messaging, and you can run InTouch over Iridium (Part Twenty-Seven) to remotely recover a site whose primary WAN is down.

Why it matters

LEO changed what “remote” means, sites that had no good option now get broadband, but only if you tame the roam. The engineer’s value-add is knowing that raw Starlink is not enough for real-time work and that bonding it (with cellular or with more Starlinks) plus Boost is the design that delivers. At the top end, multi-Starlink bonding is a genuine gigabit MPLS-alternative for mines, ships, and events. And for life-safety and critical-infrastructure customers, Iridium as a thin always-there backup is the difference between “degraded” and “dark.”

Field note

Always enable “ignore Starlink obstruction outages” on bonded Starlink WANs so a two-second tree block doesn’t tear the link out of the tunnel, and use Starlink Data Pools to keep a fleet’s bill predictable. Pair LEO with at least one diverse path (cellular or a second constellation) for anything that can’t blink, and reserve Iridium for the must-deliver lane rather than bulk traffic.

Part Twenty-Five: Wi-Fi & AP Fundamentals

The topic

The access side of a Peplink network, the Wi-Fi that users actually touch, is as much a part of the deployment as the WAN. The fundamentals here are the AP Controller, SSIDs, mesh, and wireless authentication. An SSID is a named wireless network; a single AP can broadcast several (staff, guest, IoT), each mapped to a VLAN so the segmentation from the wired side carries onto the air. Wi-Fi generations matter for capacity: Wi-Fi 5 (802.11ac) and Wi-Fi 6 (802.11ax) are the relevant ones, with Wi-Fi 6 adding efficiency in dense client environments.

Wi-Fi Mesh lets APs link to each other wirelessly instead of every AP needing an Ethernet drop, extending coverage and filling dead zones, and giving redundancy if one AP’s uplink fails. Mesh runs on 802.11ac and above, and the APs must share a Mesh ID and shared key on the chosen band to join. WDS (Wireless Distribution System) is the underlying bridging that carries this. Compared with a traditional single-AP layout, mesh tolerates obstacles and odd layouts with far less cabling and planning.

How it works on Peplink

Most Peplink routers include an AP Controller: enable it and the router manages Peplink/Pepwave APs directly, with WLAN info appearing on the dashboard. You define AP Profiles (one profile carrying multiple SSIDs, radio settings, channels, scan intervals) and apply them to APs, individually or fleet-wide from InControl, which can also push SSIDs by tag and hand end users a QR code to join. Captive portals provide controlled guest access, open or authenticated, with a redirect/splash page, configurable in the router UI or centrally in InControl. For enterprise authentication, Peplink supports 802.1X with a RADIUS server, and firmware 8.6.0 adds RadSec (RADIUS over TLS) so authentication traffic is encrypted across untrusted or cloud-connected networks. Guest isolation keeps guests seeing only the internet, never each other or the router’s admin UI, and rogue-AP detection flags unauthorized APs.

Why it matters

A Peplink site is rarely just a router, it’s a router plus Wi-Fi, and an engineer who can bond five WANs but can’t stand up segmented SSIDs, a guest captive portal, and mesh coverage can’t actually deliver the site. Mesh in particular is the practical answer to “we can’t run cable there” in warehouses, events, outdoor venues, and older buildings. And because SSIDs map to VLANs, the Wi-Fi design is where the segmentation and security story from the wired side either holds together or falls apart.

Field note

Map every SSID to a VLAN and keep guest on an isolated VLAN with a captive portal; never bridge guest onto the LAN. For mesh, confirm the Mesh ID and shared key match on the right band and keep wireless hops to a minimum, each hop costs throughput. Use 802.1X/RadSec for staff networks in regulated environments, and manage AP profiles centrally so a hundred sites get identical, correct Wi-Fi.

Part Twenty-Six: GPS & Location Services

The topic

Many Peplink routers are GPS-equipped, and location is a feature, not just a status read-out. The core capabilities are positioning, dead-reckoning, geofencing, fleet tracking, GPS forwarding, and using GPS as a time source.

How it works on Peplink

GPS-equipped routers (MAX, MBX, BR1 Pro 5G, BR2 Pro, the Dome Pro line, PDX, and others) report position continuously. GPS Dead-Reckoning keeps that position accurate when the sky view is lost, in a tunnel, urban canyon, or parking structure, by estimating the current track from the last known position, heading, speed, and distance, so the dot keeps moving instead of freezing. GPS Forwarding sends the router’s location to external systems (a dispatch or AVL platform) by IP, either directly or through InControl. Geofencing draws virtual boundaries on a map and triggers actions when the router crosses them, sending an email or HTTP/HTTPS notification, enabling or disabling a Wi-Fi AP, or (for Starlink) stowing/unstowing the dish. Fleet tracking logs travel history, GPX, with speeds, distance, and moving time for each vehicle. And because the router already has a precise GPS clock, it can act as an NTP source, removing the need for a separate time server at the site.

Why it matters

For any mobile or fleet deployment, location is half the value of the product. Dead-reckoning is what keeps tracking usable through the tunnels and downtowns where vehicles actually go. Geofencing turns location into automation, a vehicle that auto-stows its Starlink when it leaves the yard, or a unit that enables guest Wi-Fi only on-site. GPS-as-NTP quietly solves the “everything needs accurate time” problem for logging, certificates, and 802.1X without extra infrastructure.

Field note

If a customer needs reliable tracking through obstructions, specify a dead-reckoning-capable model, a non-DR unit “loses the dot” exactly where it matters. Use geofence actions to cut manual steps (stow Starlink, toggle Wi-Fi) and forward GPS through InControl so the location plumbing is centrally managed rather than hand-wired per device.