I am working with a vendor who will operate a virtual server for us on AWS. I want to use FusionHub to connect with our other locations which all have Balance routers.
We installed FusionHub and set up the PepVPN links. We can ping between the remote nodes and FusionHub.
We cannot communicate between FusionHub and the AWS virtual server. The problem seems to be that the FusionHub LAN is a slightly different subnet than the AWS virtual server.
173.31.11.xx = FusionHub WAN IP
173.31.10.xx = AWS server IP
I am told these things are configured on the AWS side. I’m in a bit of a standoff with the vendor who has no experience with Peplink. I have 15 years of experience with Peplink but nothing with AWS.
Can someone tell me where these items are configured on AWS? I’m guessing they simply mis-typed one of the boxes when the AWS instance was created.
It’s likely based on your IP ranges that these two things are in different VPCs, so you need to route between the VPCs. First, see what VPC each of these instances belong to. Then, if they’re different, set up a VPC gateway and route per AWS documentation: Example routing options - Amazon Virtual Private Cloud
If they’re the same VPC, ensure your security group’s firewall rules allow for transit between these two devices, and then start from a simple ping between them.
Next, if your AWS provider does not understand this (assuming I’m not missing something), you should find another AWS provider.
AWS VPC’s default to large subnets on creation, it may just be in a /23 that’s why the IP’s are like that, and that’s normal. On your side you have to allow access to the local net, which I assume you’ve already done. On their side they need to disable source/destination checking on the fusionhub instance, make sure the security groups allow the necessary traffic, and the VPC’s subnet route table has all your local subnets pointed to your fusionhub network interface.
It kinda sounds like the vendor doesn’t understand AWS basics because this is real simple stuff.
My usage of peplink with AWS is very extensive, and for the most part, they work together very well.