SSL VPN: Convert .ovpn to .apc/.epc for Site-to-Site SSL Tunnels
Please make a tool to conver regular openvpn configuartion files to your apc/epc format. Without such a tool it is impossible to use an astaro as client for existing openvpn server.
Simon Shaw commented
We'd like this feature so we can route certain traffic out of China via VPN servers hosted in Hong Kong. (China Telecom and Unicom have excellent links to HK but routing is an issue.
Why cant we, if we want, set up a SSL VPN Client manually?
Its not that hard to copy certificates, server addresses and such..
To provide a status update. The .apc/.epc format you refer to is not just a .ovpn file which has been converted to a proprietary format. As there is no standard at all for site-to-site SSL VPN at this time, we needed to include more information than just tunnel parameters in the file that you download as "ours" from a UTM.
Conversely, a simple .OVPN file does not contain all the information a UTM needs in order to construct a site-to-site SSL VPN. There are configuration objects used by the UTM that are used by our CONFD in the underlying system overall, and these cannot be easily deduced and labelled by the system. As such, the idea of using a UTM-generated site-to-site SSL VPN configuration file with your OpenVPN server, or importing a .OVPN file (with all the gamut of parameters possible in such a file) into the UTM for easy cross-device SSL VPN site-to-site is a large technical challenge with too many places where assumptions we would have to make would limit the scope and usefulness any ways.
We will look at some sort of solution, but it isn't a simple thing we can easily do in the short term. Keep voting! We see you guys.
Please provide a tool ASAP!!!
Try to setup a connection the other way round: Astaro as server and a linux server as a client.
Cannot understand why somebody should invent this strange format.
But at least a way for conversion is needed. NEEDED!
This is the only thing which is extremely missing from UTM. Definitely voting for this!
Daryl Morse commented
I agree that this feature is necessary. UTM uses OpenVPN, which is a standard. It makes no sense that UTM cannot import a .ovpn file plus the necessary certs and key. This should be a relatively trivial feature to implement, since a .ovpn file is clear text. Alternataively to supporting importation of a .ovpn, UTM could generate a template .apc file with clearly defined sections for a user to paste in the relevant info (ovpn configuration plus certs and key). How hard can that be?
What's happening with this? This feature is really needed.
Must have feature, there is no logical reason not to support OVPN client files.
Jacob Bird commented
temp workaround... backup the file at /var/chroot-openvpn/etc/openvpn/client/REF_SslCliStrongvpn/config-default then modify it with your OpenVPN info then feed the webui any .apc file and it will create the tunnel with your settings...
Andres Maduro commented
This is a must! We need to interoperate with other devices with this.
Alois M commented
Here is a fix
Alois M commented
I was to buy the hardware version of Astaro but after this I don't think I will. Can anyone share how I can convert .ovpn to apc or epc? This needs to be done.
I can not believe this was not done from the beginning. To create some proprietary way that's specific for this brand of router for this kind of connection is so dark-ages.
Stephan Riese commented
or made, that astaro accepts regular openvpn configuration files.
go for it
This would be great!
This would really help out at my office.
Looking right now for a way to interconnect Astaro & Linux server. This feature is definitely demanded.