NAME¶

ipsec_addconn - load a given policy into the pluto IKE daemon

SYNOPSIS¶

ipsec addconn --configsetup [--rootdir dir] [--config filename] [--ctlbase socketfile]

ipsec addconn --addall [--rootdir dir] [--config filename] [--ctlbase socketfile] [--defaultroute addr] [--defaultroutenexthop addr]

ipsec addconn [--rootdir dir] [--config filename] [--ctlbase socketfile] [--defaultroute addr] [--defaultroutenexthop addr] name1 [name2 ..]

ipsec addconn [--listroute] [--liststart] [--rootdir dir] [--config filename] [--ctlbase socketfile]

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 openswan 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 --addall is used, all connections defined in the config file will be operated on. Otherwise, only the specified connection names will be affected.

When addcon is run, connections that have the auto= option set to add, start or route will be loaded, routed or initiated. If a connection was loaded or initiated already, it will be replaced.

When --configsetup is specified, the configuration file is parsed for the config setup section and printed to the terminal usable as a shell script.

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 Xelerance Openswan project <http://www.openswan.org/> by Paul Wouters