In order to establish a PepVPN between a product like Balance One Core and FusionHub deployed in Azure or AWS, it is required that one of the two WANs has a Public IP address.
In my case, I have Starlink on WAN 1 and a AT&T LTE Modem (Nighthawk M1) on WAN 2. Starlink doesn’t offer Public IP addresses and is very limited in terms of being configured while AT&T uses Carrier Grade NAT (CGNAT) which also means no Public IP address.
The result is a newly created PepVPN connections hangs forever trying to connect. Argh!!
Is there really no work around for this? I’m a little confused why PepVPN requires on both end points whereas services like SpeedFusion Cloud, which I’m assuming is doing a very similiar VPN connection between the Balance One and their own instance running in their cloud, does not require knowledge of my WAN Public IPs. To be clear, SpeedFusion Cloud works fine in my situation, but I am after the throughput capability and configuration granularity of FusionHub in Azure.
Does any clever person here have a work around for customers like me with no Public IP address on either WAN port?