WTware is able to connect to OpenVPN.

Connection to working OpenVPN

If you have configuration file to connect to working OpenVPN, make sure it works on any Linux distributive. OpenVPN on Windows differs from OpenVPN on Linux. WTware techsupport won't be able to help with OpenVPN, if your configuration file is not tested on Linux.

This tested configuration file should be named openvpn.cfg and placed into configs directory on boot disk of terminal. You may place this file into configs directory using terminal web-interface.

In configuration file must be such line:

daemon

To make OpenVPN on Linux accept addresses of DNS servers from OpenVPN servers specify in configuration file:

script-security 2
up /etc/openvpn/update-resolv-conf

To save login and password on disk and not to enter them at every boot create in configs directory on terminal boot disk pass.txt file, containing two lines — specify login and password to OpenVPN:

OpenVPNUserName
SomeComplexPassword

In configuration file specify that pass.txt file should be used:

auth-user-pass /bootmedia/configs/pass.txt

If you need keys to connect to OpenVPN, they should be placed into configuration file. Example of openvpn.cfg configuration file, that contains keys.

If in your VPN tls-auth key is used and there's such line in configuration file:

tls-auth ta.key 1

then after embedding key into configuration file you should add one more option — key-direction — to specify key direction. Something like that:

key-direction 1
<tls-auth>
-----BEGIN OpenVPN Static key V1-----
073b0025464cdeaa6189247397d0f2f6
...
9a9a92359aa0574a95715a1df0e51484
-----END OpenVPN Static key V1-----
</tls-auth>

New OpenVPN

Easy example of configuration files for client and server: openvpn.zip. For tests: don't change server configuration files, in client configuration file specify server IP-address instead of 10.1.1.32 in line:

remote 10.1.1.32