Set Up Peplink With Starlink: BR1 Pro 5G Planning and Failover Checks

Equipment & Accessories

This checklist uses the Peplink BR1 Pro 5G as a planning example for Starlink with cellular backup. Exact hardware revision, firmware and enabled features matter. It is not a universal click-by-click configuration for every Peplink product.

Establish the two working connections

Get Starlink online with its correct power equipment and approved Ethernet handoff first. Identify the terminal and follow Starlink's instructions for any adapter or bypass arrangement. Keep a record of the working configuration before adding another router.

Activate the eligible cellular plan and verify the BR1 Pro's cellular connection independently. Check the exact regional modem version, antennas and SIM configuration. A second connection that has never been tested is not a dependable backup.

Connect the network deliberately

Follow the BR1 Pro hardware guide to connect Starlink's Ethernet handoff to the designated WAN port. Connect your test computer on the LAN side. Do not join upstream and downstream ports to the same unmanaged switch.

The MAX manual documents DHCP for an automatically assigned Ethernet WAN address. Use the connection method appropriate to your actual service and installation. Keep the Peplink LAN subnet distinct from upstream management networks.

Change the administration password and use current supported firmware through the manufacturer's documented process. Save a configuration backup and note how to regain local access before experimenting with routing.

Build ordinary failover first

Set the preferred and backup connection priorities using the manual that matches your firmware. Configure supported health checks and observe normal behaviour before deliberately interrupting a link. Avoid copying aggressive thresholds from an unrelated installation.

With other users informed, disconnect only the accessible Ethernet WAN lead at the router to simulate loss of Starlink. Test a new browsing session over cellular, reconnect Starlink and verify recovery. Then test the actual work applications: an existing call or VPN may need to reconnect when the route changes.

Keep SpeedFusion a separate decision

Ordinary WAN failover is not the same as bonding or a protected SpeedFusion tunnel. Confirm device entitlement, compatible endpoint or service, data use and the exact feature you need before enabling it. Do not assume buying the router guarantees uninterrupted calls or that two links will double a single download.

Record hardware, firmware, WAN names, priorities, test results and rollback steps. If a rule or route is unclear, ask the supplier or network installer before deploying it at an unattended site.

The related bonding demonstration is a particular setup, not a guarantee of performance. No subscription prices or service-plan recommendations are maintained in this guide.

Sources and further reading

Independently written Starlink Tips guide, reviewed 1 November 2026. Thumbnail: original AI-generated conceptual artwork, not an equipment, wiring or measurement diagram. Follow current instructions for your exact hardware.