Hi Richard,
Tibbs, Richard wrote:
I sent the following item to the openvpn user's list and the replyDepends on your definition of "best". If you don't need to constantly restart individual links, the easiest way would be to simply stick another "whatever.conf" into /etc/openvpn/ do "svi openvpn restart" and the new instance should be started (remember to run it on a different port).
advised it was possible by running two instances of openvpn with
separate config files.
One option would be to include an extra config file somewhere and manually start it on home FW. Another is to include a few lines in the openvpn start/stop script like /sbin/openvpn --config ... which I could put in several places to get start/stop/restart/reload capabilities.
What would be the best way to do this?
If you need to start tunnels individually ("on demand"), take a look at /etc/init.d/openvpn - that's the script that starts/stops the tunnels - you could basically use that as a base for scripts to individually start/stop the daemon.
Martin
P.S. I'm referring to the /etc/init.d/openvpn script found in the Bering uClibc version of openvpn - but it should be identical to what is found in the Bering package, unless Erich changed something in his package.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
