1 .TH IPSEC.CONF 5 "2012-06-26" "@IPSEC_VERSION@" "strongSwan"
3 ipsec.conf \- IPsec configuration and connections
8 specifies most configuration and control information for the
9 strongSwan IPsec subsystem.
10 The major exception is secrets for authentication;
12 .IR ipsec.secrets (5).
13 Its contents are not security-sensitive.
15 The file is a text file, consisting of one or more
17 White space followed by
19 followed by anything to the end of the line
20 is a comment and is ignored,
21 as are empty lines which are not within a section.
25 and a file name, separated by white space,
26 is replaced by the contents of that file,
27 preceded and followed by empty lines.
28 If the file name is not a full pathname,
29 it is considered to be relative to the directory containing the
31 Such inclusions can be nested.
32 Only a single filename may be supplied, and it may not contain white space,
33 but it may include shell wildcards (see
40 The intention of the include facility is mostly to permit keeping
41 information on connections, or sets of connections,
42 separate from the main configuration file.
43 This permits such connection descriptions to be changed,
44 copied to the other security gateways involved, etc.,
45 without having to constantly extract them from the configuration
46 file and then insert them back into it.
49 parameter (described below) which permits splitting a single logical
50 section (e.g. a connection description) into several actual sections.
53 begins with a line of the form:
60 indicates what type of section follows, and
62 is an arbitrary name which distinguishes the section from others
64 Names must start with a letter and may contain only
65 letters, digits, periods, underscores, and hyphens.
66 All subsequent non-empty lines
67 which begin with white space are part of the section;
68 comments within a section must begin with white space too.
69 There may be only one section of a given type with a given name.
71 Lines within the section are generally of the form
73 \ \ \ \ \ \fIparameter\fB=\fIvalue\fR
75 (note the mandatory preceding white space).
76 There can be white space on either side of the
78 Parameter names follow the same syntax as section names,
79 and are specific to a section type.
80 Unless otherwise explicitly specified,
81 no parameter name may appear more than once in a section.
85 stands for the system default value (if any) of the parameter,
86 i.e. it is roughly equivalent to omitting the parameter line entirely.
89 may contain white space only if the entire
91 is enclosed in double quotes (\fB"\fR);
94 cannot itself contain a double quote,
95 nor may it be continued across more than one line.
97 Numeric values are specified to be either an ``integer''
98 (a sequence of digits) or a ``decimal number''
99 (sequence of digits optionally followed by `.' and another sequence of digits).
101 There is currently one parameter which is available in any type of
105 the value is a section name;
106 the parameters of that section are appended to this section,
107 as if they had been written as part of it.
108 The specified section must exist, must follow the current one,
109 and must have the same section type.
110 (Nesting is permitted,
111 and there may be more than one
114 although it is forbidden to append the same section more than once.)
118 specifies defaults for sections of the same type.
119 For each parameter in it,
120 any section of that type which does not have a parameter of the same name
121 gets a copy of the one from the
124 There may be multiple
126 sections of a given type,
127 but only one default may be supplied for any specific parameter name,
130 sections of a given type must precede all non-\c
132 sections of that type.
134 sections may not contain the
138 Currently there are three types of sections:
141 section specifies general configuration information for IPsec, a
143 section specifies an IPsec connection, while a
145 section specifies special properties of a certification authority.
150 .IR "connection specification" ,
151 defining a network connection to be made using IPsec.
152 The name given is arbitrary, and is used to identify the connection.
153 Here's a simple example:
161 leftsubnet=10.1.0.0/16
163 rightsubnet=10.1.0.0/16
169 A note on terminology: There are two kinds of communications going on:
170 transmission of user IP packets, and gateway-to-gateway negotiations for
171 keying, rekeying, and general control.
172 The path to control the connection is called 'ISAKMP SA' in IKEv1
173 and 'IKE SA' in the IKEv2 protocol. That what is being negotiated, the kernel
174 level data path, is called 'IPsec SA' or 'Child SA'.
175 strongSwan previously used two separate keying daemons, \fIpluto\fP and
176 \fIcharon\fP. This manual does not discuss \fIpluto\fP options anymore, but
177 only \fIcharon\fP that since strongSwan 5.0 supports both IKEv1 and IKEv2.
179 To avoid trivial editing of the configuration file to suit it to each system
180 involved in a connection,
181 connection specifications are written in terms of
186 rather than in terms of local and remote.
187 Which participant is considered
192 for every connection description an attempt is made to figure out whether
193 the local endpoint should act as the
197 endpoint. This is done by matching the IP addresses defined for both endpoints
198 with the IP addresses assigned to local network interfaces. If a match is found
199 then the role (left or right) that matches is going to be considered local.
200 If no match is found during startup,
203 This permits using identical connection specifications on both ends.
204 There are cases where there is no symmetry; a good convention is to
207 for the local side and
209 for the remote side (the first letters are a good mnemonic).
211 Many of the parameters relate to one participant or the other;
214 are listed here, but every parameter whose name begins with
219 whose description is the same but with
225 Parameters are optional unless marked '(required)'.
226 .SS "CONN PARAMETERS"
227 Unless otherwise noted, for a connection to work,
228 in general it is necessary for the two ends to agree exactly
229 on the values of these parameters.
231 .BR aaa_identity " = <id>"
232 defines the identity of the AAA backend used during IKEv2 EAP authentication.
233 This is required if the EAP client uses a method that verifies the server
234 identity (such as EAP-TLS), but it does not match the IKEv2 gateway identity.
237 includes conn section
240 .BR authby " = " pubkey " | rsasig | ecdsasig | psk | secret | never | xauthpsk | xauthrsasig"
241 how the two security gateways should authenticate each other;
242 acceptable values are
246 for pre-shared secrets,
248 (the default) for public key signatures as well as the synonyms
250 for RSA digital signatures and
252 for Elliptic Curve DSA signatures.
254 can be used if negotiation is never to be attempted or accepted (useful for
256 Digital signatures are superior in every way to shared secrets.
257 IKEv1 additionally supports the values
261 that will enable eXtended AUTHentication (XAUTH) in addition to IKEv1 main mode
262 based on shared secrets or digital RSA signatures, respectively.
263 This parameter is deprecated, as two peers do not need to agree on an
264 authentication method in IKEv2. Use the
266 parameter instead to define authentication methods.
268 .BR auto " = " ignore " | add | route | start"
269 what operation, if any, should be done automatically at IPsec startup;
270 currently-accepted values are
278 loads a connection without starting it.
280 loads a connection and installs kernel traps. If traffic is detected between
284 , a connection is established.
286 loads a connection and brings it up immediately.
288 ignores the connection. This is equal to delete a connection from the config
290 Relevant only locally, other end need not agree on it.
292 .BR closeaction " = " none " | clear | hold | restart"
293 defines the action to take if the remote peer unexpectedly closes a CHILD_SA
296 for meaning of values).
298 .B closeaction should not be
299 used if the peer uses reauthentication or uniquids checking, as these events
300 might trigger the defined action when not desired. Currently not supported with
303 .BR compress " = yes | " no
304 whether IPComp compression of content is proposed on the connection
305 (link-level compression does not work on encrypted data,
306 so to be effective, compression must be done \fIbefore\fR encryption);
307 acceptable values are
311 (the default). A value of
313 causes the daemon to propose both compressed and uncompressed,
314 and prefer compressed.
317 prevents the daemon from proposing or accepting compression.
319 .BR dpdaction " = " none " | clear | hold | restart"
320 controls the use of the Dead Peer Detection protocol (DPD, RFC 3706) where
321 R_U_THERE notification messages (IKEv1) or empty INFORMATIONAL messages (IKEv2)
322 are periodically sent in order to check the
323 liveliness of the IPsec peer. The values
328 all activate DPD. If no activity is detected, all connections with a dead peer
329 are stopped and unrouted
331 put in the hold state
337 which disables the active sending of DPD messages.
339 .BR dpddelay " = " 30s " | <time>"
340 defines the period time interval with which R_U_THERE messages/INFORMATIONAL
341 exchanges are sent to the peer. These are only sent if no other traffic is
342 received. In IKEv2, a value of 0 sends no additional INFORMATIONAL
343 messages and uses only standard messages (such as those to rekey) to detect
346 .BR dpdtimeout " = " 150s " | <time>
347 defines the timeout interval, after which all connections to a peer are deleted
348 in case of inactivity. This only applies to IKEv1, in IKEv2 the default
349 retransmission timeout applies, as every exchange is used to detect dead peers.
351 .BR inactivity " = <time>"
352 defines the timeout interval, after which a CHILD_SA is closed if it did
353 not send or receive any traffic.
355 .BR eap_identity " = <id>"
356 defines the identity the client uses to reply to a EAP Identity request.
357 If defined on the EAP server, the defined identity will be used as peer
358 identity during EAP authentication. The special value
360 uses the EAP Identity method to ask the client for an EAP identity. If not
361 defined, the IKEv2 identity will be used as EAP identity.
363 .BR esp " = <cipher suites>"
364 comma-separated list of ESP encryption/authentication algorithms to be used
365 for the connection, e.g.
368 .BR encryption-integrity[-dhgroup][-esnmode] .
371 .BR aes128-sha1,3des-sha1 .
372 The daemon adds its extensive default proposal to this default
373 or the configured value. To restrict it to the configured proposal an
376 can be added at the end.
379 As a responder the daemon accepts the first supported proposal received from
380 the peer. In order to restrict a responder to only accept specific cipher
381 suites, the strict flag
383 exclamation mark) can be used, e.g: aes256-sha512-modp4096!
387 is specified, CHILD_SA/Quick Mode setup and rekeying include a separate
388 Diffie-Hellman exchange. Valid values for
394 Specifying both negotiates Extended Sequence Number support with the peer,
398 .BR forceencaps " = yes | " no
399 force UDP encapsulation for ESP packets even if no NAT situation is detected.
400 This may help to surmount restrictive firewalls. In order to force the peer to
401 encapsulate packets, NAT detection payloads are faked.
403 .BR ike " = <cipher suites>"
404 comma-separated list of IKE/ISAKMP SA encryption/authentication algorithms
406 .BR aes128-sha1-modp2048 .
408 .BR encryption-integrity-dhgroup .
409 In IKEv2, multiple algorithms and proposals may be included, such as
410 aes128-aes256-sha1-modp1536-modp2048,3des-sha1-md5-modp1024.
413 .B aes128-sha1-modp2048,3des-sha1-modp1536 .
414 The daemon adds its extensive default proposal to this
415 default or the configured value. To restrict it to the configured proposal an
418 can be added at the end.
421 As a responder the daemon accepts the first supported proposal received from
422 the peer. In order to restrict a responder to only accept specific cipher
423 suites, the strict flag
425 exclamation mark) can be used, e.g: aes256-sha512-modp4096!
427 .BR ikelifetime " = " 3h " | <time>"
428 how long the keying channel of a connection (ISAKMP or IKE SA)
429 should last before being renegotiated. Also see EXPIRY/REKEY below.
431 .BR installpolicy " = " yes " | no"
432 decides whether IPsec policies are installed in the kernel by the charon daemon
433 for a given connection. Allows peaceful cooperation e.g. with
434 the Mobile IPv6 daemon mip6d who wants to control the kernel policies.
435 Acceptable values are
440 .BR keyexchange " = " ike " | ikev1 | ikev2"
441 method of key exchange;
442 which protocol should be used to initialize the connection. Connections marked with
444 use IKEv2 when initiating, but accept any protocol version when responding.
446 .BR keyingtries " = " 3 " | <number> | %forever"
447 how many attempts (a whole number or \fB%forever\fP) should be made to
448 negotiate a connection, or a replacement for one, before giving up
451 The value \fB%forever\fP
452 means 'never give up'.
453 Relevant only locally, other end need not agree on it.
459 .BR left " = <ip address> | <fqdn> | " %any
461 the IP address of the left participant's public-network interface
462 or one of several magic values.
465 for the local endpoint signifies an address to be filled in (by automatic
466 keying) during negotiation. If the local peer initiates the connection setup
467 the routing table will be queried to determine the correct local IP address.
468 In case the local peer is responding to a connection setup then any IP address
469 that is assigned to a local interface will be accepted.
473 in front of a fully-qualified domain name or an IP address will implicitly set
474 .BR leftallowany =yes.
478 is used for the remote endpoint it literally means any IP address.
480 Please note that with the usage of wildcards multiple connection descriptions
481 might match a given incoming connection attempt. The most specific description
482 is used in that case.
484 .BR leftallowany " = yes | " no
489 although a concrete IP address or domain name has been assigned.
491 .BR leftauth " = <auth method>"
492 Authentication method to use locally (left) or require from the remote (right)
494 Acceptable values are
496 for public key authentication (RSA/ECDSA),
498 for pre-shared key authentication,
500 to (require the) use of the Extensible Authentication Protocol in IKEv2, and
502 for IKEv1 eXtended Authentication.
503 To require a trustchain public key strength for the remote side, specify the
504 key type followed by the minimum strength in bits (for example
507 .BR rsa-2048-ecdsa-256 ).
508 To limit the acceptable set of hashing algorithms for trustchain validation,
509 append hash algorithms to
511 or a key strength definition (for example
512 .BR pubkey-sha1-sha256
514 .BR rsa-2048-ecdsa-256-sha256-sha384-sha512 ).
517 an optional EAP method can be appended. Currently defined methods are
529 Alternatively, IANA assigned EAP method numbers are accepted. Vendor specific
530 EAP methods are defined in the form
532 .RB "(e.g. " eap-7-12345 ).
535 an XAuth authentication backend can be specified, such as
541 Hybrid authentication is used. For traditional XAuth authentication, define
545 .BR leftauth2 " = <auth method>"
548 but defines an additional authentication exchange. In IKEv1, only XAuth can be
549 used in the second authentication round. IKEv2 supports multiple complete
550 authentication rounds using "Multiple Authentication Exchanges" defined
551 in RFC4739. This allows, for example, separated authentication
554 .BR leftca " = <issuer dn> | %same"
555 the distinguished name of a certificate authority which is required to
556 lie in the trust path going from the left participant's certificate up
557 to the root certification authority.
559 .BR leftca2 " = <issuer dn> | %same"
562 but for the second authentication round (IKEv2 only).
564 .BR leftcert " = <path>"
565 the path to the left participant's X.509 certificate. The file can be encoded
566 either in PEM or DER format. OpenPGP certificates are supported as well.
567 Both absolute paths or paths relative to \fI/etc/ipsec.d/certs\fP
568 are accepted. By default
572 to the distinguished name of the certificate's subject and
574 to the distinguished name of the certificate's issuer.
575 The left participant's ID can be overridden by specifying a
577 value which must be certified by the certificate, though.
579 .BR leftcert2 " = <path>"
582 but for the second authentication round (IKEv2 only).
584 .BR leftcertpolicy " = <OIDs>"
585 Comma separated list of certificate policy OIDs the peer's certificate must
587 OIDs are specified using the numerical dotted representation.
589 .BR leftdns " = <servers>"
590 Comma separated list of DNS server addresses to exchange as configuration
591 attributes. On the initiator, a server is a fixed IPv4 / IPv6 address, or
595 to request attributes without an address. On the responder,
596 only fixed IPv4 /IPv6 addresses are allowed and define DNS servers assigned
599 .BR leftfirewall " = yes | " no
600 whether the left participant is doing forwarding-firewalling
601 (including masquerading) using iptables for traffic from \fIleftsubnet\fR,
602 which should be turned off (for traffic to the other subnet)
603 once the connection is established;
604 acceptable values are
609 May not be used in the same connection description with
611 Implemented as a parameter to the default \fBipsec _updown\fR script.
613 Relevant only locally, other end need not agree on it.
615 If one or both security gateways are doing forwarding firewalling
616 (possibly including masquerading),
617 and this is specified using the firewall parameters,
618 tunnels established with IPsec are exempted from it
619 so that packets can flow unchanged through the tunnels.
620 (This means that all subnets connected in this manner must have
621 distinct, non-overlapping subnet address blocks.)
622 This is done by the default \fBipsec _updown\fR script.
624 In situations calling for more control,
625 it may be preferable for the user to supply his own
628 which makes the appropriate adjustments for his system.
630 .BR leftgroups " = <group list>"
631 a comma separated list of group names. If the
633 parameter is present then the peer must be a member of at least one
634 of the groups defined by the parameter.
636 .BR leftgroups2 " = <group list>"
639 but for the second authentication round defined with
642 .BR lefthostaccess " = yes | " no
643 inserts a pair of INPUT and OUTPUT iptables rules using the default
644 \fBipsec _updown\fR script, thus allowing access to the host itself
645 in the case where the host's internal interface is part of the
646 negotiated client subnet.
647 Acceptable values are
654 how the left participant should be identified for authentication;
657 or the subject of the certificate configured with
659 Can be an IP address, a fully-qualified domain name, an email address, or
662 .BR leftid2 " = <id>"
663 identity to use for a second authentication for the left participant
664 (IKEv2 only); defaults to
667 .BR leftikeport " = <port>"
668 UDP port the left participant uses for IKE communication.
669 If unspecified, port 500 is used with the port floating
670 to 4500 if a NAT is detected or MOBIKE is enabled. Specifying a local IKE port
671 different from the default additionally requires a socket implementation that
672 listens to this port.
674 .BR leftprotoport " = <protocol>/<port>"
675 restrict the traffic selector to a single protocol and/or port.
677 .B leftprotoport=tcp/http
679 .B leftprotoport=6/80
683 .BR leftrsasigkey " = " %cert " | <raw rsa public key> | <path to public key>"
684 the left participant's public key for RSA signature authentication, in RFC 2537
685 format using hex (0x prefix) or base64 (0s prefix) encoding. Also accepted is
686 the path to a file containing the public key in PEM or DER encoding.
689 means that the key is extracted from a certificate.
691 .BR leftsendcert " = never | no | " ifasked " | always | yes"
700 .BR ifasked " (the default),"
701 the latter meaning that the peer must send a certificate request payload in
702 order to get a certificate in return.
704 .BR leftsourceip " = %config4 | %config6 | <ip address>"
705 Comma separated list of internal source IPs to use in a tunnel, also known as
706 virtual IP. If the value is one of the synonyms
712 an address (from the tunnel address family) is requested from the peer.
714 .BR rightsourceip " = %config | <network>/<netmask> | %poolname"
715 Comma separated list of internal source IPs to use in a tunnel for the remote
716 peer. If the value is
718 on the responder side, the initiator must propose an address which is then
719 echoed back. Also supported are address pools expressed as
720 \fInetwork\fB/\fInetmask\fR
721 or the use of an external IP address pool using %\fIpoolname\fR,
722 where \fIpoolname\fR is the name of the IP address pool used for the lookup.
724 .BR leftsubnet " = <ip subnet>"
725 private subnet behind the left participant, expressed as
726 \fInetwork\fB/\fInetmask\fR;
727 if omitted, essentially assumed to be \fIleft\fB/32\fR,
728 signifying that the left end of the connection goes to the left participant
729 only. Configured subnets of the peers may differ, the protocol narrows it to
730 the greatest common subnet. In IKEv1, this may lead to problems with other
731 implementations, make sure to configure identical subnets in such
732 configurations. IKEv2 supports multiple subnets separated by commas, IKEv1 only
733 interprets the first subnet of such a definition.
735 .BR leftupdown " = <path>"
736 what ``updown'' script to run to adjust routing and/or firewalling
737 when the status of the connection
739 .BR "ipsec _updown" ).
740 May include positional parameters separated by white space
741 (although this requires enclosing the whole string in quotes);
742 including shell metacharacters is unwise.
743 Relevant only locally, other end need not agree on it. Charon uses the updown
744 script to insert firewall rules only, since routing has been implemented
745 directly into the daemon.
747 .BR lifebytes " = <number>"
748 the number of bytes transmitted over an IPsec SA before it expires.
750 .BR lifepackets " = <number>"
751 the number of packets transmitted over an IPsec SA before it expires.
753 .BR lifetime " = " 1h " | <time>"
754 how long a particular instance of a connection
755 (a set of encryption/authentication keys for user packets) should last,
756 from successful negotiation to expiry;
757 acceptable values are an integer optionally followed by
760 or a decimal number followed by
766 in minutes, hours, or days respectively)
771 Normally, the connection is renegotiated (via the keying channel)
772 before it expires (see
774 The two ends need not exactly agree on
776 although if they do not,
777 there will be some clutter of superseded connections on the end
778 which thinks the lifetime is longer. Also see EXPIRY/REKEY below.
780 .BR marginbytes " = <number>"
781 how many bytes before IPsec SA expiry (see
783 should attempts to negotiate a replacement begin.
785 .BR marginpackets " = <number>"
786 how many packets before IPsec SA expiry (see
788 should attempts to negotiate a replacement begin.
790 .BR margintime " = " 9m " | <time>"
791 how long before connection expiry or keying-channel expiry
793 negotiate a replacement
794 begin; acceptable values as for
798 Relevant only locally, other end need not agree on it. Also see EXPIRY/REKEY
801 .BR mark " = <value>[/<mask>]"
802 sets an XFRM mark in the inbound and outbound
803 IPsec SAs and policies. If the mask is missing then a default
808 .BR mark_in " = <value>[/<mask>]"
809 sets an XFRM mark in the inbound IPsec SA and
810 policy. If the mask is missing then a default mask of
814 .BR mark_out " = <value>[/<mask>]"
815 sets an XFRM mark in the outbound IPsec SA and
816 policy. If the mask is missing then a default mask of
820 .BR mobike " = " yes " | no"
821 enables the IKEv2 MOBIKE protocol defined by RFC 4555. Accepted values are
827 the charon daemon will not actively propose MOBIKE as initiator and
828 ignore the MOBIKE_SUPPORTED notify as responder.
830 .BR modeconfig " = push | " pull
831 defines which mode is used to assign a virtual IP.
837 Push mode is currently not supported in charon, hence this parameter has no
840 .BR reauth " = " yes " | no"
841 whether rekeying of an IKE_SA should also reauthenticate the peer. In IKEv1,
842 reauthentication is always done. In IKEv2, a value of
844 rekeys without uninstalling the IPsec SAs, a value of
846 (the default) creates a new IKE_SA from scratch and tries to recreate
849 .BR rekey " = " yes " | no"
850 whether a connection should be renegotiated when it is about to expire;
851 acceptable values are
856 The two ends need not agree, but while a value of
858 prevents charon from requesting renegotiation,
859 it does not prevent responding to renegotiation requested from the other end,
862 will be largely ineffective unless both ends agree on it. Also see
865 .BR rekeyfuzz " = " 100% " | <percentage>"
866 maximum percentage by which
871 should be randomly increased to randomize rekeying intervals
872 (important for hosts with many connections);
873 acceptable values are an integer,
874 which may exceed 100,
880 after this random increase,
883 (where TYPE is one of
890 will suppress randomization.
891 Relevant only locally, other end need not agree on it. Also see EXPIRY/REKEY
898 .BR reqid " = <number>"
899 sets the reqid for a given connection to a pre-configured fixed value.
902 number of bytes to pad ESP payload data to. Traffic Flow Confidentiality
903 is currently supported in IKEv2 and applies to outgoing packets only. The
906 fills up ESP packets with padding to have the size of the MTU.
908 .BR type " = " tunnel " | transport | transport_proxy | passthrough | drop"
909 the type of the connection; currently the accepted values
913 signifying a host-to-host, host-to-subnet, or subnet-to-subnet tunnel;
915 signifying host-to-host transport mode;
916 .BR transport_proxy ,
917 signifying the special Mobile IPv6 transport proxy mode;
919 signifying that no IPsec processing should be done at all;
921 signifying that packets should be discarded.
923 .BR xauth " = " client " | server"
924 specifies the role in the XAuth protocol if activated by
927 .B authby=xauthrsasig.
934 .BR xauth_identity " = <id>"
935 defines the identity/username the client uses to reply to an XAuth request.
936 If not defined, the IKEv1 identity will be used as XAuth identity.
938 .SS "CONN PARAMETERS: IKEv2 MEDIATION EXTENSION"
939 The following parameters are relevant to IKEv2 Mediation Extension
942 .BR mediation " = yes | " no
943 whether this connection is a mediation connection, ie. whether this
944 connection is used to mediate other connections. Mediation connections
945 create no child SA. Acceptable values are
950 .BR mediated_by " = <name>"
951 the name of the connection to mediate this connection through. If given,
952 the connection will be mediated through the named mediation connection.
953 The mediation connection must set
956 .BR me_peerid " = <id>"
957 ID as which the peer is known to the mediation server, ie. which the other
958 end of this connection uses as its
960 on its connection to the mediation server. This is the ID we request the
961 mediation server to mediate us with. If
965 of this connection will be used as peer ID.
968 These are optional sections that can be used to assign special
969 parameters to a Certification Authority (CA). Because the daemons
970 automatically import CA certificates from \fI/etc/ipsec.d/cacerts\fP,
971 there is no need to explicitly add them with a CA section, unless you
972 want to assign special parameters (like a CRL) to a CA.
978 .BR auto " = " ignore " | add"
979 currently can have either the value
984 .BR cacert " = <path>"
985 defines a path to the CA certificate either relative to
986 \fI/etc/ipsec.d/cacerts\fP or as an absolute path.
988 .BR crluri " = <uri>"
989 defines a CRL distribution point (ldap, http, or file URI)
995 .BR crluri2 " = <uri>"
996 defines an alternative CRL distribution point (ldap, http, or file URI)
999 .BR ocspuri " = <uri>"
1000 defines an OCSP URI.
1006 .BR ocspuri2 " = <uri>"
1007 defines an alternative OCSP URI.
1009 .BR certuribase " = <uri>"
1010 defines the base URI for the Hash and URL feature supported by IKEv2.
1011 Instead of exchanging complete certificates, IKEv2 allows to send an URI
1012 that resolves to the DER encoded certificate. The certificate URIs are built
1013 by appending the SHA1 hash of the DER encoded certificates to this base URI.
1014 .SH "CONFIG SECTIONS"
1015 At present, the only
1017 section known to the IPsec software is the one named
1019 which contains information used when the software is being started.
1020 The currently-accepted
1027 .BR strictcrlpolicy " = yes | ifuri | " no
1028 defines if a fresh CRL must be available in order for the peer authentication
1029 based on RSA signatures to succeed.
1030 IKEv2 additionally recognizes
1034 if at least one CRL URI is defined and to
1038 .BR uniqueids " = " yes " | no | never | replace | keep"
1039 whether a particular participant ID should be kept unique,
1040 with any new IKE_SA using an ID deemed to replace all old ones using that ID;
1041 acceptable values are
1047 Participant IDs normally \fIare\fR unique, so a new IKE_SA using the same ID is
1048 almost invariably intended to replace an old one. The difference between
1052 is that the daemon will replace old IKE_SAs when receving an INITIAL_CONTACT
1053 notify when the option is
1055 but will ignore these notifies if
1058 The daemon also accepts the value
1060 which is identical to
1064 to reject new IKE_SA setups and keep the duplicate established earlier.
1066 .BR charondebug " = <debug list>"
1067 how much charon debugging output should be logged.
1068 A comma separated list containing type/level-pairs may
1070 .B dmn 3, ike 1, net -1.
1071 Acceptable values for types are
1072 .B dmn, mgr, ike, chd, job, cfg, knl, net, asn, enc, lib, esp, tls,
1073 .B tnc, imc, imv, pts
1074 and the level is one of
1075 .B -1, 0, 1, 2, 3, 4
1076 (for silent, audit, control, controlmore, raw, private). By default, the level
1079 for all types. For more flexibility see LOGGER CONFIGURATION in
1080 .IR strongswan.conf (5).
1083 The IKE SAs and IPsec SAs negotiated by the daemon can be configured to expire
1084 after a specific amount of time. For IPsec SAs this can also happen after a
1085 specified number of transmitted packets or transmitted bytes. The following
1086 settings can be used to configure this:
1088 l r l r,- - - -,lB s lB s,a r a r.
1089 Setting Default Setting Default
1091 ikelifetime 3h lifebytes -
1096 IKE SAs as well as IPsec SAs can be rekeyed before they expire. This can be
1097 configured using the following settings:
1099 l r l r,- - - -,lB s lB s,a r a r.
1100 Setting Default Setting Default
1101 IKE and IPsec SA IPsec SA
1102 margintime 9m marginbytes -
1106 To avoid collisions the specified margins are increased randomly before
1107 subtracting them from the expiration limits (see formula below). This is
1118 Randomization can be disabled by setting
1119 .BR rekeyfuzz " to " 0% .
1121 The following formula is used to calculate the rekey time of IPsec SAs:
1124 rekeytime = lifetime - (margintime + random(0, margintime * rekeyfuzz))
1127 It applies equally to IKE SAs and byte and packet limits for IPsec SAs.
1129 Let's consider the default configuration:
1137 From the formula above follows that the rekey time lies between:
1140 rekeytime_min = 1h - (9m + 9m) = 42m
1141 rekeytime_max = 1h - (9m + 0m) = 51m
1144 Thus, the daemon will attempt to rekey the IPsec SA at a random time
1145 between 42 and 51 minutes after establishing the SA. Or, in other words,
1146 between 9 and 18 minutes before the SA expires.
1149 Since the rekeying of an SA needs some time, the margin values must not be
1153 .B margin... + margin... * rekeyfuzz
1154 must not exceed the original limit. For example, specifying
1156 in the default configuration is a bad idea as there is a chance that the rekey
1157 time equals zero and, thus, rekeying gets disabled.
1161 /etc/ipsec.d/aacerts
1163 /etc/ipsec.d/cacerts
1168 strongswan.conf(5), ipsec.secrets(5), ipsec(8)
1170 Originally written for the FreeS/WAN project by Henry Spencer.
1171 Updated and extended for the strongSwan project <http://www.strongswan.org> by
1172 Tobias Brunner, Andreas Steffen and Martin Willi.