In evaluating FusionHub running in an AWS VM running in my VPC-DEV (development VPC), I’m able to form a PepVPN connection from multiple PepWave devices. Yay!!!
I am, however, only able to reach private IP’s from my PepWave devices to a within VPC-DEV that are located ON THE SAME SUBNET as the FusionHub VM. This means I have to locate my AWS VM’s on the same subnet and AZ (availability zone) as the FusionHub VM. Now this sounds like a simple matter of setting up static routes somewhere or something similar.
Well this is taking me way too long to figure out on my own. Seems like FusionHub should, perhaps, interrogate the AWS VPC it’s running on to see the what the CIDR is. And then advertise and provide route(s) as needed to allow remote VPN’s reach all subnets associated with the VPC’s CIDR block.
Or at least give some manual options in FusionHub to address this.
Or maybe it’s something ridiculously simple that I’m overlooking.