BAlfson wrote the following post at 29 Oct 2015 5:28 PM:
I'm curious, JD. What is the reason for needing the UTM to act as a client?
I'm not looking at a default route - but I have a VPS which has an openVPN server running - allowing for various people/locations to connect and tunnel data to the server, and for some of them to contact between each other.
I can't put Sophos up there, because I couldn't then install any of the things I actually want the VPS for, so it's all hand crafted.
I've previously had my home network connected to the VPN by the firewall (and a couple of rules allowing limited return access), which made life very easy inside the home network. And allowed me to contact the home network from wherever I was by going via the VPS.
I can probably (I haven't tried it from "outside" yet) get to my home network using the SSL VPN - and that will be fine - but I lose the convenience of internal connectivity to my VPS and the other sites which are connected to the VPS.
BAlfson wrote the following post at 29 Oct 2015 5:28 PM:
I'm curious, JD. What is the reason for needing the UTM to act as a client?
I'm not looking at a default route - but I have a VPS which has an openVPN server running - allowing for various people/locations to connect and tunnel data to the server, and for some of them to contact between each other.
I can't put Sophos up there, because I couldn't then install any of the things I actually want the VPS for, so it's all hand crafted.
I've previously had my home network connected to the VPN by the firewall (and a couple of rules allowing limited return access), which made life very easy inside the home network. And allowed me to contact the home network from wherever I was by going via the VPS.
I can probably (I haven't tried it from "outside" yet) get to my home network using the SSL VPN - and that will be fine - but I lose the convenience of internal connectivity to my VPS and the other sites which are connected to the VPS.