Hello,
I think I went a long way setting up FusionHub on an AWS EC2 instance, solo license, Balance 30 Pro. I found the entire process way longer and more difficult that they made it seem, perhaps because I had to setup the VPC in Amazon from scratch.
I followed a few of the posts and youtube videos, none of which was entirely comprehensive, and this is what I managed so far.
I have a route conflict that I think stems from the way I setup the VPC and/or the subnet or something like that. In particular the LAN IP’s where the balance 30 Pro is located is 192.168.1.x
The Amazon VPC has IPv4 CIDR: 192.168.1.0/24
Public Elastic IP, I can log into the instance and upgrade the firmware
I had to modify the route table other wise I could not log into the instance. There was an item with destination = 192.168.1.0/24; I added another route with destination 0.0.0.0, and that made the instance reachable and I presumed opened the internet to the EC2 instance.
Now, in the Balance Pro status page:
Under PepVPN with SpeedFusion section, I see the yellow square instead of green, and it says Route Conflict, and in the details page: Route conflict: 192.168.1.0/24
In the FusionHub:
in the status-speedfusion page, it shows the green square next to WAN, and where it says the Balance Pro name it’s stuck on “Updating routes…”
In the Dashboard, it shows WAN IP Address: 192.168.1.9
In a youtube video that I’ve seen, although it was setup on Vultr, the guy had a public IP there. Mine is private and the same family as my LAN, so I think my route conflict stems from that. Is that the problem? How do I fix it? Should I have a public IP in the IPv4 CIDR field of the subnet, and which one, the same as the elastic IP ?
I thank in advance anybody that wants to help, I think it’s a quick fix if you know what to do. Let me know if you need more details , thank you!