We have several devices on the WAN which communicate with devices on the Peplink LAN via port forwarding. Each WAN device is configured with the peplink IP and a forwarding port.
This is marvelous until the internet goes down and the Peplink switches to cellular failover. The WAN IP address of the Peplink evaporates and does not resolve leaving all of the WAN devices in the dark. The LAN devices still have internet so which is the reason why we chose the Peplink for Cellular failover - but half of our solution is severely compromised during the outage.
For our solution to fully comprehensive we need to have the original configured IP address viable for communication in parallel during the outage.
That is why Speedfusion exists. You build a bonded tunnel (using WAN and cellular) to a FusionHub virtual appliance in the cloud and port forward from the Fusionhub cloud based public IP over the tunnel to your LAN devices.
Then if any WAN fails, the IP stays the same because it is not tied to a local WAN connection.
At Venn, we do this with full datacenter resilience for enterprise customers too, so a Fusionhub can fail, WANs can fail, even the remote peer Peplink device can fail (we can deploy two Peplinks in an active active pair) and inbound IP routing still works on the original public IP.
1 Like
Hmmm. I will have to try this. Is there documentation how to set this up?
I would think conceptually having this work locally is more reliable. Helpdesk did say something about a reverse tunnel but I did not understand it to mean SpeedFusion.
I would imagine that means my license needs to be up to date?
Thanks,
Ben
I have an old video here that explains most of it.
You can do this using routing alone bit not without the help of your ISP.
You would advertise your Wan IP using BGP to your ISP, if the WAN were to fail, your Peplink would then advertise it to your Cellular provider. If your wired WAN ISP is friendly with your Cellular provider they can push updates to each other for inbound routing.
However this is rare, the config is conplex enough that your ISP will charge more for it and you are then tied into a config that you don’t manage end to end yourself which always makes me nervous.
I believe I have some networks with similar setups based on your description. The option you need to look into is “Independent from Backup WANs”. I use this to leave the IP Forwarding WAN active even if it “fails”.
Martin - thank you so much for your reply. I was going to test your suggestion when Noah responded. I actually tried checking the Independent from Backup WANs setting and it worked!
Kudos to Noah for that.
The only question I have is that I noticed that when using this setting - the Cellular is in Connected mode rather than Standby. Does that mean Cellular is being used even while on Priority 1 ethernet?
Please compare the snapshots:
