ipsec-addconn - Man Page
load a given policy into the pluto IKE daemon
Synopsis
ipsec addconn [--configsetup] [--config /etc/ipsec.conf] [--ctlsocket /run/pluto/pluto.ctl] [--verbose] [--noexport] [--warningsfatal]
ipsec addconn --liststack [--config /etc/ipsec.conf] [--ctlsocket /run/pluto/pluto.ctl] [--verbose] [--noexport] [--warningsfatal]
ipsec addconn --checkconfig [--config /etc/ipsec.conf] [--ctlsocket /run/pluto/pluto.ctl] [--verbose] [--warningsfatal]
ipsec addconn --autoall [--config /etc/ipsec.conf] [--ctlsocket /run/pluto/pluto.ctl] [--verbose] [--warningsfatal]
ipsec addconn [--config /etc/ipsec.conf] [--ctlsocket /run/pluto/pluto.ctl] [--verbose] [--warningsfatal] connection [connection ...]
ipsec addconn [--config /etc/ipsec.conf] [--ctlsocket /run/pluto/pluto.ctl] [--listadd] [--listall] [--listignore] [--listroute] [--liststart] [--verbose] [--warningsfatal]
ipsec addconn --help
Description
ipsec addconn takes a config file (or stdin) containing the format of ipsec.conf, or the format of individual "conn" sections, and uses that information to load named or all connections defined in that configuration file into the running libreswan pluto IKE daemon. If no configuration file is specified, the default configuration file is used. If no pluto socket is specified, the default socket location will be used.
When --autoall is specified, all connections that include the auto= configuration option are processed as follows:
- auto=add, auto=keep
the connection is loaded
- auto=route, auto=ondemand
the connection is loaded and routed
- auto=up, auto=start
the connection is loaded, routed, marked as needing to stay up, and initiated
If the connection is already loaded then it is first removed.
When one or more connections are specified, those connections are loaded. Any auto= in the configuration is ignored.
When --configsetup is specified, the configuration file is parsed for the config setup section and printed to the terminal usable as a shell script. These are prefaced with export unless --noexport is specified.
When --checkconfig is specified, the configuration file is parsed and all sections are checked for correct syntax. If an error is found, information about it is printed to the terminal.
When --listroute or --liststart is specified, no connections are added or replaced, only shown. This command can be used to verify which connections the addcon command would act upon, without actually performing any action.
History
Man page written for the Libreswan project <https://libreswan.org/> by Paul Wouters
Author
Paul Wouters