Accessing end-points via FusionHub server

Hello everyone!

Last week I’ve tried to configure a FusionHub VM over my own PC at work,
However, after I managed to establish a connection with my router (MAX HD2) and I could ping the FusionHub VM from the router and vice versa (through the web panel), I haven’t figured out how can I access the endpoints devices that are connected to the router?

The host that running the FusionHub Virtual machine is running with Windows 10 OS, and the software used to run the VM is VMWare Workstation,
I followed this official manual to configure the environment:

What am I missing? how can I access the VPN LAN network from my host (the windows machine) via the FusionHub virtual machine?

Thanks!

Your windows host will need some way to know what subnets are at the other end of the SpeedFusion VPN connection and then that it has to route via the Fusionhub to get there.

Easiest way is to setup static routes on your windows host with the Fusionhub LAN as the next gateway/hop.

If you plan to have many remote Peplink peers then I would consider using OSPF or BGP or RIP between your fusionhub and your existing network gateway to make this more transparent.

Thank you for your quick response!

I’ve tried to add some rules in the Windows host routing table, however, I didn’t managed to navigate the traffic through the FusionHub LAN.

In terms of setting up a static route, do I need to setup both the Windows host routing tables and the FusionHub Virtual machine static route (from the web interface)?

And what about the fact that my network (from the ISP router) is on 10.0.0.0/24 and the FusionHub LAN is 192.168.10.0/24? is that even possible to do that?
Note that my VM network adapter is on bridge, meaning that it’s having the internal IP of 10.0.0.23 (given from my ISP router’s DHCP) but the VPN LAN IP is different as I mentioned.

No because you Fusionhub already knows where the 10.0.0.x/x subnet is because it has a LAN interface on that subnet. Its only the windows host that doesn’t know where to route traffic destined for the 192.168.10.0/24 subnet.

So a static route on the windows host for 192.168.10.0/24 with a gateway of 10.0.0.x (where that IP is in use by the Fusionhub LAN) is what you need.

The other thing to note is that Windows firewall when dealing with “Private” networks like “Home” and “Work” networks will only treat a connection as if it was from the “Private” network if the origin IP is from the same subnet.

So your windows firewall on your host might be messing with you and blocking the traffic from the remote peer.

1 Like