Starlink pairs really well with Peplink, whether as a primary link with cellular backup or as one leg of a bonded/failover setup. Peplink is a Starlink Authorized Technology Provider, and recent firmware adds real integration: management, telemetry, and obstruction handling all from your Peplink and InControl2. The trick is getting Starlink into "bypass mode" cleanly, understanding its CGNAT behavior, and turning on the advanced features. Here's the practical guide.
Get Starlink onto a Peplink WAN port
- Make sure you have an Ethernet feed from Starlink. Gen 3 hardware has an Ethernet port; Gen 2 (rectangular dish) needs the Starlink Ethernet Adapter.
- Connect that Ethernet to a WAN port on your Peplink and confirm the WAN comes up and passes traffic.
- Once it's working reliably over Ethernet, open the Starlink app and enable Bypass Mode ("Bypass Starlink Wi-Fi router"). This disables the Starlink router's Wi-Fi and routing so your Peplink is in charge. The dish will reboot, and this reboot can take longer than usual.
Understand CGNAT (this matters)
Standard Starlink Residential uses carrier-grade NAT (CGNAT), so your Peplink WAN typically gets a private 100.64.x.x address, not a public IP. Consequences:
- Inbound connections from the internet (port forwarding, hosting a server, some VPNs) will not work directly, because they're blocked at Starlink's NAT.
- The fix is SpeedFusion (or SpeedFusion Connect): your traffic exits from a Peplink endpoint with a reachable address, which gets you around CGNAT and gives you stable remote access. See our SpeedFusion Connect article.
- Some Starlink Priority/Business plans offer a public IP option if you truly need one at the dish.
Enabling advanced Starlink features and telemetry
To unlock the Peplink-Starlink integration (management controls, telemetry, and obstruction handling), tell the Peplink which WAN your Starlink is on:
- Go to Network > WAN > Starlink (on firmware 8.6.0 or above this is labeled Orbit WAN).
- Click Edit.
- Select the interface your Starlink is connected to (for example, the WAN or VLAN WAN the dish is plugged into). On 8.6.0+ the Orbit WAN screen lets you map Starlink (and OneWeb) to the correct WAN connection.
- Save.
Once mapped, the Peplink can pull Starlink data and expose the management controls described below.
Management and telemetry through InControl2
With Starlink integrated, you can manage the dish without touching the Starlink app:
- Reboot, stow, and unstow your Starlink from InControl2 with a click, and sync those actions across multiple units at once.
- View Starlink telemetry through InControl2's WAN Quality Report, so you can see all your dishes in one place instead of checking each unit in the Starlink portal or app.
- Bond multiple Starlink units within the same network using SpeedFusion for extra resilience or more bandwidth on larger and critical deployments.
Ride through brief obstructions
Starlink can drop momentarily due to obstructions (trees, buildings) or weather. Firmware 8.5.0 and later add an "Ignore Obstruction Outages" option (shown as "Ignore Outages" on the Orbit WAN screen). Enabling it prevents the Peplink from immediately marking the link down on brief interruptions, so it holds the connection instead of flapping. This is especially useful on mobile deployments.
A note on GPS (currently in flux)
Firmware 8.5.0 introduced GPS support over Synergy WAN, which let a Peplink use Starlink's GPS for location and asset tracking. Be aware, though, that Starlink's provision of GPS/location data to third-party equipment has been in flux: Starlink announced plans to sunset this capability and subsequently walked that back. Because it may change again, treat Starlink-sourced GPS as subject to change and, where accurate positioning matters, rely on the Peplink device's own built-in GPS (on models that have it) as the primary source.
What about OneWeb?
Starlink isn't the only low-earth-orbit (LEO) option Peplink supports. On the same Orbit WAN screen (firmware 8.6.0+), you'll see a OneWeb section alongside Starlink, and the setup follows the same pattern:
- Connect the OneWeb terminal to a Peplink WAN (or VLAN WAN) port, then go to Network > WAN > Orbit WAN > Edit and map OneWeb to that interface.
- The same integrated benefits apply: use it as a backup or bonded link with SpeedFusion, and manage/monitor it through InControl2.
OneWeb is typically an enterprise/managed offering rather than a consumer service, so provisioning is handled through a OneWeb provider. The Peplink side, however, is configured just like Starlink on the Orbit WAN screen. If you're running both Starlink and OneWeb, you can map each to its own WAN and bond or fail over between them.
Other configuration tips
- Set the WAN health check to ping a reliable host or use DNS lookup, so the Peplink detects a satellite outage quickly and fails over.
- Starlink is excellent for download but has variable latency and periodic brief drops. Bonding it with cellular (or OneWeb) via SpeedFusion, with WAN Smoothing, smooths out real-time traffic like video calls.
Designing a Starlink-plus-cellular or multi-orbit setup for a boat, RV, or remote site? Llama Networks does this often. Reach out to sales[at]llamanetworks[dot]com.