should --config be --connect?

How to customize and extend your OpenVPN installation.

Moderators: TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech

Post Reply
User avatar
Ingber
OpenVpn Newbie
Posts: 16
Joined: Wed Sep 24, 2014 3:05 am

should --config be --connect?

Post by Ingber » Mon Aug 03, 2015 5:51 pm

In my C:/Program Files/OpenVPN/doc/openvpn.8.html (and in online openvpn.net docs) I see is states that --config can be used on client conf files, and that it can be left off if only one file is used, which I assume means a .ovpn file, e.g., as prepared on an OpenVPN server.

In my Thinkpad Carbon Windows 10 x64 Pro running OpenVPN 2.3.7 x64 this does not work in a shortcut -> Properties -> Target window.

However, using "--connect", which is NOT at all found in the above-mentioned doc files, does work just fine on the desktop and under the Startup folder:
"C:\Program Files\OpenVPN\bin\openvpn-gui.exe" --connect xxxx.ovpn
E.g., using "--config" instead of "--connect" does not work?

User avatar
Traffic
OpenVPN Protagonist
Posts: 4066
Joined: Sat Aug 09, 2014 11:24 am

Re: should --config be --connect?

Post by Traffic » Tue Aug 04, 2015 9:14 am

Using OpenVPN-GUI.exe is slightly different to using openvpn.exe from command line.

Try this:

Code: Select all

c:\Program Files\OpenVPN\bin\Openvpn-GUI.exe --help

User avatar
Ingber
OpenVpn Newbie
Posts: 16
Joined: Wed Sep 24, 2014 3:05 am

Re: should --config be --connect?

Post by Ingber » Tue Aug 04, 2015 3:33 pm

Thanks for this information.

Post Reply