I can't get Starlink to work with SpeedFusion even though it works and is online (says not available - link failure, no data received)

Product Discussion Peplink Balance
1

I have a Balance 310 Fibre 5G and have Fibre as WAN1, Starlink as WAN2, and 5G built in as WAN3.

All 3 connections work and show online, and I can route traffic over them no issue.

However, I cannot get SpeedFusion to work at all. I have FusionHub deployed on Azure and I created a mesh VPN using InControl2 including all 3 WAN and keeping them as priority 1. The Fibre and the 5G both show online and work fine, but Starlink does not.

When I go to Status > SpeedFusion it shows the tunnel, and it shows:

Fibre (Green) showing transmit and receive
Starlink (Red) saying Not available - link failure, no data received
5G (Green) showing transmit and receive

I have tried connecting WAN2 from the Balance directly to the Starlink’s PoE bypassing the Wifi (I have the circle dish), and I have also tried adding the Starlink wifi back on, and connecting that to WAN2 on the Balance using NAT, and neither works, they both always say “Not available - link failure, no data received.”

I’ve delete and recreated the tunnels but no luck.

In case it helps at all, I have the same issue on a BR1 Pro with Starlink and cannot get it to work through SpeedFusion. Also, FusionHub is hosted on Azure.

Is there anything else I can try or something that needs to be enabled to make Starlink work? Again, it works 100% for Internet, it’s just through SpeedFusion that it’s not working.

2

Sometimes I have found that CGNAT and Speedfusion have odd interactions, try changing the port to a couple of numbers higher… lots of people are on 4500 for Ipsec NAT-T so I go up to 4503 etc… I haven’t seen the problem with Starlink… (4501 works fine)… but I did see similar problems on Verizon LTE… Changed the port and it connected right up.

If that isn’t it, you need packet captures to see which side is getting dropped.

3

I finally got it working by opening all inbound and outbound ports in Azure and then it immediately connected. Thanks!

4

I seem to be getting this intermittently on my starlink, (I have speedfusion on TCP, 443).

I suspect it’s something like a stuck CG-NAT session causing it not to re-connect as downing the startlink interface for a few seconds usually fixes it.

Ideally though it would be better if it could recover by itself
20x 8.3.0 build 5293