I would suggest switching from PPTP to L2TP - it is more secure, and should not be blocked by Azure. You would still need to open the proper ports/protocols in the Azure firewall, port forward those from FusionHub to your balance’s LAN IP (inside the tunnel), and configure the proper authentication settings on your balance.
This article should help you find the right ports and settings needed to achieve the setup in Kenny’s previous guide.
Hello, any updates on the road map and availability of this this remote user access feature for FHB?
I have a customer who has similar requirement.
He needs to connect PPTP to L2TP to his HD2 but via FHB sitting at AWS because HD2 does not have public ip address and DDNS does not work, is not an option as well.
Can I do port forward from FHB towards the LAN ip address of the HD2 via existing SF tunnel instead of HD2’s WAN interface ip address?
Use port forward from FusionHub to Balance/MAX to enable remote user access only work for PPTP. This is not working for L2TP (and no way to make it work now).
In Balance/MAX’s “Remote User Access” page, select "PPTP’, in “Listen On” row, select at least one WAN connection, that can be any WAN (even a disabled WAN).
Details for setting port forwarding rule on FusionHub is in the 2nd post of this thread.
We are working on Remote User Access on FusionHub, it is expected to be available in next firmware.
You can message me if you want to beta test this feature.
I don’t have any problem to upgrade the FusionHub from 8.0.0 to 8.0.0b047. Please ensure the Upgrade only is unchecked on the firmware management page. Please open ticket if you still encounter the issue.
Hello @TK_Liew,
All sorted, there was a typo in the initially posted URL, @Kenny has updated the thread with the corrected URL now.
Happy to Help,
Marcus
I’m using Sophos SSL client on Windows which seems to be a fork of OpenVPN ( installing the sophos client after OpenVPN overwrites it) and the source of the issue. I’ll try to make them coexist and see if it solves the issue.
I have reply your question via the following post :
Please help to perform packet capture at the Fusionhub end and verify whether the OpenVPN traffics generate from the client is reaching to the FusionHub. If you found the traffics is reaching to the FusionHub please follow up that using a support ticket.
for OpenVPN, the Server IP address in the ovpn file is set to FusionHub’s private IP address, you need to modify the ovpn file to set server IP address to FusionHub’s public IP address. We will improve this in future release.