Pepwave MAX HD2 Dual SIM Bonding

Product Discussion Other Products
1

Dear All,
I am attempting to use SpeedFusion with 2 AT&T SIM cards.
I have installed the VSPHERE virtual server for it and attempted using the PepVPN on both HD2 and Vsphere.

My Ip address for the HD2 is 192.168.50.2 and Vsphere 192.168.50.17

I am very new to VPN, so if you could please give me some advise or where to find it that would be great. I’ve also opened the suggested ports.

Thank you!

2

OK So just to check, you have Fusionhub installed on vsphere in an office / datacenter somewhere and a HD2 connected just via cellular right?

The normal LAN IP for a HD2 is 192.168.50.1, what I’m curious about is why your vsphere server (I assume you mean the Fusionhub) also has an IP in the same subnet of (192.168.50.0/24)?

If you want to create a VPN between the LAN of the HD2 and the LAN of the Fusionhub they will need to have different LAN subnets so consider changing the Fusionhub LAN to something else (like 192.168.100.1)

The easiest way to get VPN up and running would be using InControl2. Add the Fusionhub and HD2 to a group in IC2 and then use the VPN configuration manager. You can see a demo of that on the IC2 page. https://www.peplink.com/products/incontrol-2/

1 Like
4

Hey Martin,
Thanks for the fast reply. I do have an HD2 and a Fusionhub. Just to clarify, I want to bond both of the sims together. I guess that means that 20mbps+20mbps is 40. Is this what I am doing by creating a VPN to my vsphere server. The server and the HD2 are in the same room.
I will try and change the IP of the FusionHub, but if you could clarify me the question above that would be great.

Thanks!

5

OK got it. So your FusionHub will need a public IP (or ports forwarded from a public IP to its WAN that then has a Private IP).

Then the HD2 with its cellular connections can then create the multiple tunnels via that public IP to the Fusionhub and SpeedFusion will then use all available tunnels at the same time and bond them together.

Since each connection has its own VPN tunnel created over it and those tunnels have a bandwidth overhead, the general rule of thumb is that you will lose 20% of the available bandwidth to the underlying SpeedFusion process.

In your theoretical example above, you would then get 32Mbps of usable bandwidth.

In the real world, lots of other things affect bandwidth availability - ie latency (and latency variation / jitter) between the HD2 and the FusionHub, packet loss, tower congestion RF interference etc.

Once you have the SpeedFusion VPN up you can use the tools in Status → SpeedFusion on both devices to test throughput over the tunnel.

Good luck!

1 Like
7

Okay, So you are saying that I have to do the following:

FusionHUB IP: 192.168.50.17

cellular connection 1 IP: lets say 1.1.1.1
cellular conneciton 2 IP: lets say 2.2.2.2

so a VPN tunnel has to be made from 1.1.1.1 to 192.168.50.17
and another of 2.2.2.2 to 192.168.50.17

Is this correct?

Thanks

8

Kind of. That’s what happens in the background. SpeedFusion VPN is really clever and does the individual tunnels for you (so if you were to add another internet connection to the HD2 like a DSL it would see that and just roll it into the bonded tunnel automatically). All you need to do is set up a profile on both the FusionHub and the HD2 to tell each one about the other.

To set it up manually (rather than using InControl2 which will do this for you) you would do the following.

On the FusionHub:

  1. Login to Web admin and navigate to Network → VPN | SpeedFusion
  2. Make a note of the PepVPN Local ID (or set one if it asks you to and remember it) - for this example we’ll pretend its MyFusionHub this is just an ID used to identify this Fusionhub.
  3. Click New Profile and, give it a name, turn off encryption (as this will improve throughput) set a remote ID of MyHD2 click Save and then Apply.

On the HD2

  1. Login to the web UI Navigate to Network VPN | SpeedFusion
  2. Edit the PepVPN Local ID (or set it if asked) to MyHD2
  3. Click New Profile
  4. Set the Name as FusionHub (or whatever you like its just so you know what profile this is for)
  5. Turn off Encryption - again to give you the most bandwidth
  6. Set the remote ID to MyFusionHub
  7. Set the Remote IP Address to be the public IP of your network there (that has ports TCP 32015 and UDP 4500 forwarded to the FusionHub IP of 192.168.50.17)
  8. Click Save and Apply

Then sit back and watch the tunnel get created. Then test it.

1 Like
9

Hey Martin,

I just did that and it’s still giving me problems. The link just stays in Starting. It might be because I am using a Cisco ASDM Firewall and it did not quite understand my port forwarding. Hopefully I will solve it tomorrow and tell you how it goes!

Thanks again.