@sitchuwap I don’t know about your particular hardware or setup, but as long as you leave off the WAN Smoothing option, then SpeedFusion absolutely bonds 2 links together at the packet level… IE packet 1 on Link A, packet 2 on Link B, packet 3 on Link A, Packet 4 on Link B, etc for double the throughput in theory. I say in theory because there’s CPU overhead, packet overhead, another end of the tunnel and lots of variables.
If you are using the SpeedFusion cloud option, there are 2 tunnels, Default and WAN Smoothing… just use default.
If you are setting up your own FusionHub, leave off this option…
Now with all that said I’ve only been able to push about 80Mbps through SpeedFusion cloud or even my own FusionHub server at Azure, versus I get 110-160Mb and 40-80Mb out of my 2 links respectively. So if I use an application that starts 2 data streams and load balance it locally with Weighted Balance Algorithm, I’m able to get 220MB of download throughput. So I wouldn’t say SpeedFusion will fix everything in your life, you’ll still have to play around with the trade offs of each solution. For my needs, I’m using outbound policy to select what goes down the tunnels versus what goes out locally.