Hi All,
Diving through the forums we find a lot of useful information regarding Speedfusion for Hot-Failover using back-up cellular systems. We are however in a somewhat reversed situation, where we find we are getting difficulties creating a truly stable network.
We are using a MAX BR2 Pro on a vessel. We use both cellular modems as our prime connection, and have Starlinks as a backup system. Cellular data is quite a bit cheaper then the Starlink in our case. So ideally we use this as long as possible. Previously the crew would change the priorities of the systems (Cellular prio1 / Starlink prio2) by hand when working in areas with spotty / intermitted cellular connections. It’s difficult to ‘gauge’ when the cellular is good enough again to switch back, leading to a lot of ‘overuse’ of more expensive Starlink data when truly good cellular was available.
For this reason, we are now trialing SFC, hoping it can be a good source of switching for us.
We have the following setup:
All WANs on Prio1 (cellular1/2 and Starlink)
We have cellular setup to check for at least 3 signal bars, and healthcheck is set on Smartcheck
.
Outbound Policies are set up to enforce traffic over the SpeedFusion Connect tunnel.
SpeedFusion Connect setup with:
We want to use cellular as long as it is a good and usable signal, hence bonding and dual models. However we want hot-failover especially for the personnel on board so they experience ‘seamless’ connection so they do not have to switch by hand.
So far this is working quite well, however we still get reports from the vessel that there are moments when the connection is quite poor. We suspect the cellular signal is not being rejected fast enough.
Does anyone have any experience with such a setup who could shine some light on good settings / health checks for cellular systems in such a scenario. We do not mind switching away before the signal truly degrades (and thus losing a bit of ‘cheaper’ data) as automatically switching back will save us enough of more expensive Starlink Data that this will end up being cost-effective.
Looking forward to any tips / tricks / best-practices people can and are willing to share with us!