The least used Algorithm.
Yes if a WAN fails sessions on that WAN will terminate and need to be rebuilt, new sessions get sent over the other active WANs.
This is used to connect to your own remote appliances. So between your device and another physical device at another location, or between your physical appliance and a virtual FusionHub appliance you can install in the cloud.
I have an old FusionHub setup video here that you might find enlightening https://www.youtube.com/watch?v=ZxZBWloVizM
Hotfailover is the consequence of having more than one active WAN link in priority 1 on the dashboard, AND then having those healthy WANs used at the same time inside of a Speedfusion VPN tunnel (or SFC tunnel), AND then sending your traffic over that VPN link.
If speedfusion has more than one active WAN in simultaneous use, traffic flowing over it can hot failover between those WANs.
Have more than one WAN, enable SFC and you’ll have hot failover.
WAN smoothing duplicates traffic, it is not hot failover. You consume double the bandwidth to ensure a sent packet gets to the other side. Used when WAN links have lots of packetg loss.
If a WAN fails it will be seamless, but when WANs are healthy you are burning data on both WANs and so reducing your total available bandwidth for user traffic by half. You don’t want this. Although you might enable it for VoIP traffic alone since that is very low bandwidth and it ensures the traffic gets through.
Adaptive FEC is the best thing in the whole wide world. It helps with Starlink + Cellular connections. Turn it on.
I always leave it at 150ms
Excellent. That enabled hot failover between the two P1 WANs.
You might have a primary tunnel with Dynamic Weighted bonding and adaptive FEC, then a subtunnel just for VoIP with WAN smoothing enabled. On Outbound policy the subtunnel is there as a WAN option so you can send VoIP traffic via it.
Or you might have a subtunnel that just uses Starlink which you send you smart TVs over so that they don’t consumed cellular bandwidth.
Yes. This is an automated way to set up an outbound policy for those MAC addresses.
Yes default routing. Or whatever you have in our outbound policy list.
Outbound policy gives you full granular policy based routing control. What you did in SFC is like a wizard to achieve that for SFC tunnels and LAN clients that use it.
That is what I do. I like the full control I have in outbound polices.
Take a look at SaaS steering overview videos for guidance. https://www.youtube.com/watch?v=rcqh84KP8lk