Content-type: text/html
Setup
The action taken depends on the specific command, and on the contents of the config setup section of the IPsec configuration file (/etc/ipsec.conf, see ipsec.conf(5)). Current commands are:
start
stop
restart
status
The stop operation tries to clean up properly even if assorted accidents have occurred, e.g. Pluto having died without removing its lock file. If stop discovers that the subsystem is (supposedly) not running, it will complain, but will do its cleanup anyway before exiting with status 1.
Although a number of configuration-file parameters influence setup's operations, the key one is the interfaces parameter, which must be right or chaos will ensue.
The --show and --showonly options cause setup to display the shell commands that it would execute. --showonly suppresses their execution. Only start, stop, and restart commands recognize these flags.
/etc/rc.d/init.d/ipsec the script itself /etc/init.d/ipsec alternate location for the script /etc/ipsec.conf IPsec configuration file /proc/sys/net/ipv4/ip_forward forwarding control /var/run/pluto/ipsec.info saved information /var/run/pluto/pluto.pid Pluto lock file /var/run/pluto/ipsec_setup.pid IPsec lock file
ipsec.conf(5), ipsec(8), ipsec_manual(8), ipsec_auto(8), route(8)
All output from the commands start and stop goes both to standard output and to syslogd(8), via logger(1). Selected additional information is logged only to syslogd(8).
Written for the FreeS/WAN project <http://www.freeswan.org> by Henry Spencer.
Old versions of logger(1) inject spurious extra newlines onto standard output.