Question Are you using Pepwave SpeedFusion?

[Tnedator]

Yes, I created it as new. This was due to changing my datacenter, but maybe it is a required step

Last time, several years ago, when mine expired, I couldn't figure out a way to renew it, and I wound up creating a new key. This last time, I just paid for a five pack fusion hub license, since I plan to have both my primary and backup home routers as peplinks, as well as my RV. I'm going to create a speedfusion VPN for all of them, so just went ahead and went the paid license route.

 

[Neal]

I never did anything with the InControl expirations, I figured once I had the setup established then my VM hosting SpeedFusion would pair with my Pepwave's and that has held true. I can login to my SpeedFusion VM's to manage them as needed and it's all working great. I don't see a need for InControl other than to remote manage endpoints which at this time everything is settled in and working wonderfully.

 

[Neal]

I am using FusionHub first of all, because I want 100% of all my traffic going thru this. This differs from SpeedFusion in that I am providing the Datacenter connection for my RV.

View attachment 12773


This is what the connection looks like under advanced->speedfusion

So the way I handle traffic is thru the Policy.

Advanced -> Outbound Policy

View attachment 12774


This is what my policy looks like.

The first policy says that if I am using a SoftEtherVPN -- skip speed fusion. I do this for comparison of speeds on the provider vs going direct, and also when I need to alter my IP address for outbound reasons.

All other traffic, being IoT, laptops, guests, etc goes thru the SpeedFusion.

That custom policy looks like this:

View attachment 12775


In my InControl2 page, I can then control the fusion hub.

View attachment 12779


Depending on my physical location, I choose which fusion hub I want to connect to. As shown, I have 3 FusionHubs right now, located in Dallas, New Brunswick, and Seattle. The GPS is wrong for my Seattle location. I plan on adding another in Chicago and Denver, with the goal of being within 500 miles of my fusionhub at all times. This will minimize latency.

For those using speedfusion the algorithm should be "Enforced" and not "Priority". Priority is just that, it tries the first, if fails, moves to the next. This means you may think you're using your VPN but it could fail down to non VPN connections. When you change to Enforced you're picking ONE path and only that path can work or it fails. Just understand the difference between Priority and Enforced.

With that said, you can also just create an Outbound policy rule named Priority for your non speedfusion use. You have all of your wans in priority 1 for example but you want to control the order of use. This is where Priority comes into play. I may want to prefer Verizon over AT&T and the Priority outbound rule does just that.