> > Are you saying you want OpenVPN to read configuration options from a config > > file rather than the command line when -f is used? > > > > James > > > > That's right. Configuration files have some advantages from my point of > view: > - Only one script to start/stop VPNs. A init.d-like script that will > call OpenVPN for each one of the conf. files. > - Configuration files are easier to edit via scripts than shell scripts > with lots of '--option val \' lines > - Configuration files are easier to comment and can even have all > options OpenVPN support (Soe commented out, some not)
Hmmm. I am hesitant to put in a configuration file parser because linux/unix already seem to have so many powerful external tools to do this, e.g. *********** cat >openvpn.config dnl this is a sample OpenVPN config file dnl local host --local near.bar.net dnl remote host --remote far.bar.net dnl tun/tap device --dev tun1 <control-d> openvpn `m4 openvpn.config` ******************** which gives you the power of m4 if you want it, but also gives you the simplicity to be able to build a tunnel with just a short command line. James
