Does anyone have a solution to maintain active Speedfusion tunnels on two Peplink devices in HA mode using Starlink?
It’s very easy to setup regular HA (with configuration sync) using two Peplink devices, one (or two) switches and one (or two) Starlink units. The master device sets up the Speedfusion tunnels to a remote device or Fusionhub. After failure of the master device, the slave device takes over but has to re-establish the tunnels, which takes some time.
When disabling the config sync and creating a separate tunnel with higher cost metric, it should be possible to have both tunnels active and fail over to the slave device/tunnel within a second. The only problem is that the Starlink units only allow to have only one IP address (either a public IP or a CGNAT IP) at their client side, which makes it impossible for the slave device to maintain an active tunnel. Buying an additional IP address which is terminated on the Starlink unit is not an option for Starlink unfortunately. The only solution I can think of is putting an additional small router in between each Starlink unit and the HA pair.
Or does anyone have a better idea for faster Speedfusion tunnel failover?
Or could Speedfusion tunnel re-establishment be improved by exchanging session information on a permanent base between master and slave unit? +30s is a really long time for mobile units.
