Starlink and Cellular Bonding for Remote Connectivity

Combine a satellite connection such as Starlink with 4G LTE, 5G or wired Internet links. Mushroom Networks bonding algorithms adapt how traffic uses the available WAN paths as their capacity, delay and loss change. Use a peered tunnel and a reachable relay when you need packet-level bonding across connections.

ADDRESSING THE NETWORKING NEEDS OF SATCOM

Satellite and cellular links can provide complementary connectivity at remote offices, temporary sites and vehicles. Their performance changes with coverage, congestion, obstructions and the conditions of each service. Measure the paths at your location and choose the equipment and relay configuration for the applications you need to run.

LEO systems such as Starlink and GEO satellite services have different path characteristics. A mixed-link deployment needs adaptive traffic management, suitable routing and enough usable capacity on the surviving paths when a link becomes unavailable.

Bonding satellite modems

Bonding for Increased Throughput

In peered mode, a bonding tunnel can send packets from one session across multiple WAN paths and reassemble them at the relay. Achieved throughput depends on the links, router, service profile and relay path; it is not a fixed sum promised for every application.

Self-Healing for Automated Optimization

Adaptive algorithms monitor changing WAN conditions and adjust packet-level path selection automatically. Resilience depends on reachable WAN paths, sufficient remaining capacity and an available relay.

Transparent Integration with Existing Infrastructure

Connect the satellite handoff to a Mushroom wired WAN port and place your local devices behind the Mushroom LAN or your existing firewall. Select which application traffic enters the bonding tunnel and confirm the routing at the relay.

Satellite + cellular deployment guide

How to combine Starlink with 4G LTE or 5G

Build a hybrid connection around the applications you need to keep running. The following workflow separates the physical connections, tunnel configuration and application checks.

Logical traffic path for peered satellite + cellular bonding

Your devicesLAN or existing firewall
Mushroom routerPortabella or Truffle
WAN pathsStarlink Ethernet + cellular connections
Peered endpointCloud or customer-hosted relay
ApplicationsInternet services or remote site

Starlink supplies the wired WAN handoff. Embedded cellular modems in Portabella, or external cellular routers on Truffle WAN ports, supply additional paths. The relay reassembles traffic carried by the configured bonding tunnel.

Choose the equipment

Equipment for satellite plus cellular connectivity
Deployment	Mushroom equipment	Connection requirements
Portable or remote site, 4G LTE	Portabella 4000i family	Four embedded modems in 4000i; three in 3000i or two in 2000i. Connect Starlink to the wired Ethernet WAN port.
Portable or remote site, 5G	Portabella 4000i 5G family	Four, three or two embedded 5G modems with 4G LTE fallback. Confirm regional modem and carrier compatibility.
Vehicle or rail deployment	Portabella 4000it (4G or 5G)	Four embedded modems. Confirm the chosen configuration’s power input, connectors, installation and applicable certifications.
Fixed site with Ethernet WAN equipment	Truffle family	Use Ethernet handoffs from Starlink and external cellular routers. Select a model with enough WAN ports for the planned connections.

Also allow for the correct Starlink kit and Ethernet handoff, active cellular plans, suitable antennas, power for all devices, and a cloud or customer-hosted relay when using peered bonding. Compare the current wireless model configurations.

Connect and configure the paths

Bring each connection online separately. Check the Starlink service and each cellular modem before combining them. Verify SIM activation, regional modem support and antenna placement.
Use the Ethernet handoff for your Starlink kit. Standard Actuated kits require the Starlink Ethernet Adapter. Kits with native Ethernet use the manufacturer’s specified port and cable. Follow the Starlink third-party router instructions for the installed hardware.
Configure the wired WAN. Starlink’s third-party router guidance uses DHCP. Verify the acquired address, gateway and working Internet access in the Mushroom WAN status view. Keep the local LAN addressing distinct from the upstream networks.
Choose the Starlink router mode. Use bypass mode where Starlink recommends it for the kit and network design. Bypass disables the Starlink router’s Wi-Fi; local clients then need the Mushroom LAN/Wi-Fi or an existing access point.
Configure the peered tunnel. Use the supplied cloud service configuration or configure the customer-hosted endpoint and client. Match credentials, endpoint addressing, firewall rules and the required software/service options.
Route the intended traffic into the tunnel. An “up” tunnel alone does not mean every application uses it. Verify application routes or the firmware-specific capture-all policy, and confirm the return path at the relay.

Understand the relay and IP behaviour

Choosing a mode for satellite and cellular paths
Mode	Traffic behaviour	What to verify
Standalone load balancing	Distributes separate sessions across available WAN links.	A session uses its selected WAN path. A path change can require an application to reconnect.
Peered data bonding	Distributes packets within a session across the tunnel’s eligible WAN paths.	The relay must be reachable and the application traffic must enter the tunnel. Confirm capacity, routing and service options.
Cloud static IP / inbound services	With the appropriate BBS configuration, a cloud static IP is mapped to the device through the tunnel.	Confirm the IP service, port mapping and firewall policy. Direct traffic outside the tunnel still follows the upstream WAN addressing.

Starlink’s default IPv4 service uses carrier-grade NAT (CGNAT), which prevents direct unsolicited inbound IPv4 connections. Its optional public IPv4 policy depends on the service plan and is not a truly static address. A configured Mushroom cloud static IP is a separate relay service; it does not change Starlink’s IP policy.

Validate the deployment at your location

Record the exact router, modem and Starlink kit, firmware, carrier plans, relay location, tunnel profile and encryption setting.
Establish a baseline for each WAN separately: usable uplink/downlink capacity, latency, packet loss and the application’s behaviour.
Test a single-session transfer through the peered tunnel, concurrent transfers, an active call and a live stream where relevant. Monitor which WAN paths carry the traffic.
In a test setup, disconnect or degrade one WAN and observe the application, tunnel status and remaining capacity. Also test the expected behaviour when all paths or the relay are unavailable.
For inbound access, verify the configured cloud IP and firewall policy from outside the local network. Keep a record of the test conditions and results.

Different paths may share power, a cellular tower or upstream infrastructure. Bonding adapts to changing paths; it cannot supply capacity when no usable WAN-to-relay path remains.

Can Starlink and 5G be bonded without a relay?

They can be used together for standalone load balancing. Packet-level bonding of a session requires a peered endpoint, supplied by the cloud service or hosted by the customer.

Will the combined connection always deliver the sum of the link speeds?

No fixed combined rate is promised. Link conditions, router and service limits, path delay, tunnel overhead and relay reachability affect the result. Validate the applications on the intended connection mix.

Configuration references

Discuss your deployment

TESTIMONIALS & AWARDS

“It [Streamer] worked perfectly, right out of the box. I watched the bandwidth status during the event and monitored our traffic and usage and we had zero downtime and as such, no chances of any critical data being lost.”