This never has been done successfully by anyone here that I can remember. Maybe this new member has an idea: https://community.sophos.com/members/jw0914_5f00_01
Cheers - Bob
This never has been done successfully by anyone here that I can remember.
This never has been done successfully by anyone here that I can remember. Maybe this new member has an idea: https://community.sophos.com/members/jw0914_5f00_01
Cheers - Bob
What!? Seriously!?
I mean, let's forget the .ovpn-to-.a/.epc file conversion... I can get that THAT hasnm't been done successfully. I have followed several threads and sites and scripts, and none have worked. I get that.
But are you telling me that we canNOT configure a Sophos UTM device to be an OpenVPN client!? How can that be?
Possible, maybe... easy, not likely. OpenVPN is inherently easy to configure and use, with configs, and their respective options, extremely easy to configure... the problem with Sophos is the way it has gone about implementing OpenVPN on the backend.
Being extremely familiar with OpenVPN, a hunch says it's possible; however due to Sophos' custom deployment of OpenVPN and the fact it creates server and client configs dynamically, filesystem information would be required. If someone can find out where Sophos stores all OpenVPN files and scripts, I'd be more than willing to do some research, but without those files to show exactly what Sophos is doing and how it's doing it, there's a zero chance it can be configured as a client.
If the OpenVPN files and scripts can be found, it should allow not just configuring Sophos as an OpenVPN client, but also make it possible to run multiple OpenVPN servers.
The way Sophos is configured by default is to create client configs dynamically based upon the dynamic creation of the server config. When no SSL profile is enabled (created, but not enabled), no server config exists; once an SSL profile is enabled, Sophos dynamically creates a server config from openvpn.conf-default, as well as client configs from ./client/config.default. Disable the SSL profile, and server and client configs are deleted until they're dynamically created again when the SSL profile(s) is(are) enabled.
[SIZE="1"]**DISCLAIMER: Making any changes via the command line interface [cli] results in the loss of support and warranty for paid licensees**[/SIZE]
A simple solution is to buy a VPN router (http://www.amazon.com/TP-LINK-TL-R600VPN-Gigabit-Broadband-Supports/dp/B007B60SCG/ref=sr_1_1?ie=UTF8&qid=1445007503&sr=8-1&keywords=tp-link+vpn+router) and place it between your cable modem and UTM hardware. The VPN router uses DHCP to the cable modem and the UTM hardware uses DHCP to the VPN router. I have successfully used the web interface to the VPN router to connect with HMA VPN service. I could not establish an automatic on-demand connection; the VPN connection needs to be re-established manually.
Why would you recommend to a UTM owner to buy a VPN router, when UTM is a VPN router?
Exactly. It is for this very reason I had chosen Sophos UTM as the solution here.
Sadly, it looks lke Sophos canNOT be configured to be a VPN Client.
Unless I am wrong in this, I am going to have to start searching for another solution that CAN act as a VPN Client. Given that there's a feature request that's been going on for over 5 years, with no Official responses from Sophos, I doubt that this is anything that will be resolved in any amount of time. This is rather sad in my opinion...
The reason why you currently cannot use UTM as a client is because of the backend scripts that control the OpenVPN config files within the OpenVPN jail... find the scripts and it can be configured as a client