Tony wrote:
On Thu, 18 May 2006 23:49:16 +0400, Charles Duffy <cdu...@spamcop.net>
wrote:
Why not just have separate config files for each possible
configuration, rather than stuffing several configurations in one file?
I did not know if it is possible on the client.
Well, there's nothing about OpenVPN itself that makes it possible, and
plenty about what folks can do with shell scripts or small,
easy-to-write snippets of 3rd-party wrapper code that makes it possible.
Since OpenVPN tends to rely quite a bit on shelling out to hooks to add
new functionality, having OpenVPN itself be started by a wrapper that
rotates configurations isn't a very big leap.
Now, if your clients are on Windows and don't have something like Cygwin
installed (and if the Windows Scripting Host isn't flexible enough for
this kind of thing, which it may or may not be), writing that wrapper
may be a little bit trickier than it would be otherwise... but it still
should be a fairly straightforward exercise.
Another option -- if clients are using the OpenVPN GUI -- is just to
have the different .conf files be named after the different locations
they may be at, and let them manually select the one to start from the menu.
