STRONGSWAN.CONF(5) strongSwan STRONGSWAN.CONF(5)

strongswan.conf - strongSwan configuration file

While the ipsec.conf(5) configuration file is well suited to define IPsec related configuration parameters, it is not useful for other strongSwan applications to read options from this file. The file is hard to parse and only ipsec starter is capable of doing so. As the number of components of the strongSwan project is continually growing, a more flexible configuration file was needed, one that is easy to extend and can be used by all components. With strongSwan 4.2.1 strongswan.conf(5) was introduced which meets these requirements.

The format of the strongswan.conf file consists of hierarchical sections and a list of key/value pairs in each section. Each section has a name, followed by C-Style curly brackets defining the section body. Each section body contains a set of subsections and key/value pairs:

settings := (section|keyvalue)*
section  := name { settings }
keyvalue := key = value\n

Values must be terminated by a newline.

Comments are possible using the #-character.

Section names and keys may contain any printable character except:

. , : { } = " # \n \t space

An example file in this format might look like this:

a = b
section-one {
	somevalue = asdf
	subsection {
		othervalue = xxx
	}
	# yei, a comment
	yetanother = zz
}
section-two {
	x = 12
}

Indentation is optional, you may use tabs or spaces.

Options that define an integer value can be specified as decimal (the default) or hexadecimal ("0x" prefix, upper- or lowercase letters are accepted). Locale-dependent strings (e.g. the thousands separator of the current locale) may also be accepted in locales other than "C".

Options that define a floating-point value can be specified as decimal (the default) or hexadecimal ("0x" prefix, upper- or lowercase letters are accepted). The radix character (decimal separator) in either case is locale-dependent, usually ".".

Unless stated otherwise, options that define a time are specified in seconds. The "s", "m", "h" and "d" suffixes may be used to automatically convert values given in seconds, minutes, hours or days (for instance, instead of configuring a rekey time of 4 hours as "14400" seconds, "4h" may be used).

There are some global options that don't accept these suffixes as they are configured as integer values in seconds or milliseconds, or even as floating-point numbers (e.g. the retransmission timeout). Options that accept the suffixes have a corresponding default value.

It is possible to inherit settings and sections from another section. This feature is mainly useful in swanctl.conf (which uses the same file format). The syntax is as follows:

section    := name : references { settings }
references := absname[, absname]*
absname    := name[.name]*

All key/value pairs and all subsections of the referenced sections will be inherited by the section that references them via their absolute name. Values may be overridden in the section or any of its sub-sections (use an empty assignment to clear a value so its default value, if any, will apply). It is currently not possible to limit the inclusion level or clear/remove inherited sub-sections.

If the order is important (e.g. for auth rounds in a connection, if round is not used), it should be noted that inherited settings/sections will follow those defined in the current section (if multiple sections are referenced, their settings are enumerated left to right).

References are evaluated dynamically at runtime, so referring to sections later in the config file or included via other files is no problem.

Here is an example of how this might look like:

conn-defaults {
	# default settings for all conns (e.g. a cert, or IP pools)
}
eap-defaults {
	# defaults if eap is used (e.g. a remote auth round)
}
child-defaults {
	# defaults for child configs (e.g. traffic selectors)
}
connections {
	conn-a : conn-defaults, eap-defaults {
		# set/override stuff specific to this connection
		children {
			child-a : child-defaults {
				# set/override stuff specific to this child
			}
		}
	}
	conn-b : conn-defaults {
		# set/override stuff specific to this connection
		children {
			child-b : child-defaults {
				# set/override stuff specific to this child
			}
		}
	}
	conn-c : connections.conn-a {
		# everything is inherited, including everything conn-a
		# already inherits from the sections it and its
		# sub-section reference
	}
}

Using the include statement it is possible to include other files into strongswan.conf, e.g.

include /some/path/*.conf

If the file name is not an absolute path, it is considered to be relative to the directory of the file containing the include statement. The file name may include shell wildcards (see sh(1)). Also, such inclusions can be nested.

Sections loaded from included files extend previously loaded sections; already existing values are replaced. It is important to note that settings are added relative to the section the include statement is in.

As an example, the following three files result in the same final config as the one given above:

	a = b
	section-one {
		somevalue = before include
		include include.conf
	}
	include other.conf
include.conf:
	# settings loaded from this file are added to section-one
	# the following replaces the previous value
	somevalue = asdf
	subsection {
		othervalue = yyy
	}
	yetanother = zz
other.conf:
	# this extends section-one and subsection
	section-one {
		subsection {
			# this replaces the previous value
			othervalue = xxx
		}
	}
	section-two {
		x = 12
	}

Values are accessed using a dot-separated section list and a key. With reference to the example above, accessing section-one.subsection.othervalue will return xxx.

The following keys are currently defined (using dot notation). The default value (if any) is listed in brackets after the key.

Plugins to load in ipsec aikgen tool.
File measurement information database URI. If it contains a password, make sure to adjust the permissions of the config file accordingly.
Plugins to load in ipsec attest tool.

Options for the charon IKE daemon.

Note: Many of the options in this section also apply to charon-cmd and other charon derivatives. Just use their respective name (e.g. charon-cmd instead of charon). For many options defaults can be defined in the libstrongswan section.

Deliberately violate the IKE standard's requirement and allow the use of private algorithm identifiers, even if the peer implementation is unknown.
Accept unencrypted ID and HASH payloads in IKEv1 Main Mode.

Some implementations send the third Main Mode message unencrypted, probably to find the PSKs for the specified ID for authentication. This is very similar to Aggressive Mode, and has the same security implications: A passive attacker can sniff the negotiated Identity, and start brute forcing the PSK using the HASH payload.

It is recommended to keep this option to no, unless you know exactly what the implications are and require compatibility to such devices (for example, some SonicWall boxes).

Maximum number of half-open IKE_SAs (including unprocessed IKE_SA_INITs) for a single peer IP.
Whether Certificate Revocation Lists (CRLs) fetched via HTTP or LDAP should be saved under a unique file name derived from the public key of the Certification Authority (CA) to ${sysconfdir}/ipsec.d/crls (stroke) or ${sysconfdir}/swanctl/x509crl (vici), respectively.
Whether relations in validated certificate chains should be cached in memory.
By default, after detecting any changes to interfaces and/or addresses no action is taken if the current path to the remote peer still looks usable. Enabling this option will use DPD to check if the path actually still works, or, for instance, the peer removed the state after a longer phase without connectivity. It will also trigger a MOBIKE update if NAT mappings were removed during the downtime.
Send the Cisco FlexVPN vendor ID payload, which is required in order to make Cisco brand devices allow negotiating a local traffic selector (from strongSwan's point of view) that is not the assigned virtual IP address if such an address is requested by strongSwan. Sending the Cisco FlexVPN vendor ID prevents the peer from narrowing the initiator's local traffic selector and allows it to e.g. negotiate a TS of 0.0.0.0/0 == 0.0.0.0/0 instead. This has been tested with a "tunnel mode ipsec ipv4" Cisco template but should also work for GRE encapsulation.
Send Cisco Unity vendor ID payload (IKEv1 only).
Close the IKE_SA if setup of the CHILD_SA along with IKE_AUTH failed.
Number of half-open IKE_SAs (including unprocessed IKE_SA_INITs) that activate the cookie mechanism.
Number of half-open IKE_SAs (including unprocessed IKE_SA_INITs) for a single peer IP that activate the cookie mechanism.
Benchmark crypto algorithms and order them by efficiency.
Buffer size used for crypto benchmark.
Time in ms during which crypto algorithm performance is measured.
Test crypto algorithms during registration (requires test vectors provided by the test-vectors plugin).
Test crypto algorithms on each crypto primitive instantiation.
Strictly require at least one test vector to enable an algorithm.
Whether to test RNG with TRUE quality; requires a lot of entropy.
Delete CHILD_SAs right after they got successfully rekeyed (IKEv1 only). Reduces the number of stale CHILD_SAs in scenarios with a lot of rekeyings. However, this might cause problems with implementations that continue to use rekeyed SAs until they expire.
Delay in seconds until inbound IPsec SAs are deleted after rekeyings (IKEv2 only). To process delayed packets the inbound part of a CHILD_SA is kept installed up to the configured number of seconds after it got replaced during a rekeying. If set to 0 the CHILD_SA will be kept installed until it expires (if no lifetime is set it will be destroyed immediately).
Use ANSI X9.42 DH exponent size or optimum size matched to cryptographic strength.
Use RTLD_NOW with dlopen when loading plugins and IMV/IMCs to reveal missing symbols immediately.
DNS server assigned to peer via configuration payload (CP).
DNS server assigned to peer via configuration payload (CP).
Enable Denial of Service protection using cookies and aggressiveness checks.

Section to define file loggers, see LOGGER CONFIGURATION in strongswan.conf(5).

<name> may be the full path to the log file if it only contains characters permitted in section names. Is ignored if path is specified.
Loglevel for a specific subsystem.
If this option is enabled log entries are appended to the existing file.
Specifies the default loglevel to be used for subsystems for which no specific loglevel is defined.
Enabling this option disables block buffering and enables line buffering.
Prefix each log entry with the connection name and a unique numerical identifier for each IKE_SA.
Add the log level of each message after the subsystem (e.g. [IKE2]).
Optional path to the log file. Overrides the section name. Must be used if the path contains characters that aren't allowed in section names.
Adds the milliseconds within the current second after the timestamp (separated by a dot, so time_format should end with %S or %T).
Prefix each log entry with a timestamp. The option accepts a format string as passed to strftime(3).
If enabled objects used during authentication (certificates, identities etc.) are released to free memory once an IKE_SA is established. Enabling this might conflict with plugins that later need access to e.g. the used certificates.
Whether to follow IKEv2 redirects (RFC 5685).
Violate RFC 5998 and use EAP-only authentication even if the peer did not send an EAP_ONLY_AUTHENTICATION notify during IKE_AUTH.
Maximum size (complete IP datagram size in bytes) of a sent IKE fragment when using proprietary IKEv1 or standardized IKEv2 fragmentation, defaults to 1280 (use 0 for address family specific default values, which uses a lower value for IPv4). If specified this limit is used for both IPv4 and IPv6.
Name of the group the daemon changes to after startup.
Timeout in seconds for connecting IKE_SAs (also see IKE_SA_INIT DROPPING).
Enable hash and URL support.
Maximum number of concurrent resolver threads (they are terminated if unused).
Minimum number of resolver threads to keep around.
If enabled responders are allowed to use IKEv1 Aggressive Mode with pre-shared keys, which is discouraged due to security concerns (offline attacks on the openly transmitted hash of the PSK).
If this is disabled the traffic selectors from the kernel's acquire events, which are derived from the triggering packet, are prepended to the traffic selectors from the configuration for IKEv2 connection. By enabling this, such specific traffic selectors will be ignored and only the ones in the config will be sent. This always happens for IKEv1 connections as the protocol only supports one set of traffic selectors per CHILD_SA.
A space-separated list of routing tables to be excluded from route lookups.
Maximum number of IKE_SAs that can be established at the same time before new connection attempts are blocked.
Number of exclusively locked segments in the hash table.
Size of the IKE_SA hash table.

Defaults for options in this section can be configured in the libimcv section.
Whether IMVs send a standard IETF Assessment Result attribute.
Global IMV policy database URI. If it contains a password, make sure to adjust the permissions of the config file accordingly.
Manually set whether a default password is enabled
Manually set the name of the client OS (e.g. Ubuntu).
Manually set the version of the client OS (e.g. 12.04 i686).
Script called for each TNC connection to generate IMV policies.
Whether to close IKE_SA if the only CHILD_SA closed due to inactivity.
Limit new connections based on the current number of half open IKE_SAs, see IKE_SA_INIT DROPPING in strongswan.conf(5).
Limit new connections based on the number of jobs currently queued for processing (see IKE_SA_INIT DROPPING).
Causes charon daemon to ignore IKE initiation requests.
Install routes into a separate routing table for established IPsec tunnels.
Install virtual IP addresses.
The name of the interface on which virtual IP addresses should be installed. If not specified the addresses will be installed on the outbound interface.
Check daemon, libstrongswan and plugin integrity at startup.
A comma-separated list of network interfaces that should be ignored, if interfaces_use is specified this option has no effect.
A comma-separated list of network interfaces that should be used by charon. All other interfaces are ignored.
NAT keep alive interval.
Number of seconds the keep alive interval may be exceeded before a DPD is sent instead of a NAT keep alive (0 to disable). This is only useful if a clock is used that includes time spent suspended (e.g. CLOCK_BOOTTIME).
Includes source file names and line numbers in leak detective output.
Threshold in bytes for allocations to be included in usage reports (0 to include all).
Threshold in number of allocations for allocations to be included in usage reports (0 to include all).
Plugins to load in the IKE daemon charon.
If enabled, the list of plugins to load is determined via the value of the charon.plugins.<name>.load options. In addition to a simple boolean flag that option may take an integer value indicating the priority of a plugin, which would influence the order of a plugin in the plugin list (the default is 1). If two plugins have the same priority their order in the default plugin list is preserved. Enabled plugins not found in that list are ordered alphabetically before other plugins with the same priority.
Initiate IKEv2 reauthentication with a make-before-break instead of a break-before-make scheme. Make-before-break uses overlapping IKE and CHILD_SA during reauthentication by first recreating all new SAs before deleting the old ones. This behavior can be beneficial to avoid connectivity gaps during reauthentication, but requires support for overlapping SAs by the peer. strongSwan can handle such overlapping SAs since version 5.3.0.
Maximum number of IKEv1 phase 2 exchanges per IKE_SA to keep state about and track concurrently.
Maximum packet size accepted by charon.
Enable multiple authentication exchanges (RFC 4739).
WINS servers assigned to peer via configuration payload (CP).
WINS servers assigned to peer via configuration payload (CP).
Length of nonces in OCSP requests. According to RFC 8954, valid values are between 1 and 32, with new clients required to use 32. Some servers might not support that so lowering the value to e.g. 16 might be necessary.
RFC3779 requires that all addrblocks claimed by a certificate must be contained in the addrblock extension of the issuer certificate, up to the root CA. The default depth setting of -1 enforces this.

In practice, third party (root) CAs may not contain the extension, making the addrblock extension unusable under such CAs. By limiting the validation depth, only a certain level of issuer certificates are validated for proper addrblock extensions: A depth of 0 does not check any issuer certificate extensions, a depth of 1 only the direct issuer of the end entity certificate is checkend, and so on.

If set to yes, a subject certificate without an addrblock extension is rejected if the issuer certificate has such an addrblock extension. If set to no, subject certificates issued without the addrblock extension are accepted without any traffic selector checks and no policy is enforced by the plugin.
Loglevel for logging to Android specific logger.

Section to specify arbitrary attributes that are assigned to a peer via configuration payload (CP).
<attr> can be either address, netmask, dns, nbns, dhcp, subnet, split-include, split-exclude or the numeric identifier of the attribute type. The assigned value can be an IPv4/IPv6 address, a subnet in CIDR notation or an arbitrary value depending on the attribute type. For some attribute types multiple values may be specified as a comma separated list.
Release all online leases during startup. Disable this to share the DB between multiple VPN gateways.
Database URI for attr-sql plugin used by charon. If it contains a password, make sure to adjust the permissions of the config file accordingly.
Enable logging of SQL IP pool leases.
Use the enhanced BLISS-B key generation and signature algorithm.
If enabled, only Botan's internal RNG will be used throughout the plugin. Otherwise, and if supported by Botan, rng_t implementations provided by other loaded plugins will be used as RNG.
A comma-separated list of network interfaces for which connected subnets should be ignored, if interfaces_use is specified this option has no effect.
A comma-separated list of network interfaces for which connected subnets should be considered. All other interfaces are ignored.
Cron style string specifying CSV export times.
String to use in empty intermediate CA fields.
Use a fixed intermediate CA field count.
Force export of all trustchains we have a private key for.
strftime(3) format string to export expiration dates as.
strftime(3) format string for the CSV file name to export local certificates to.
strftime(3) format string for the CSV file name to export remote certificates to.
CSV field separator.
File to store coupling list to.
Hashing algorithm to fingerprint coupled certificates.
Maximum number of coupling entries to create.
Maximum number of redirects followed by the plugin, set to 0 to disable following redirects, set to -1 for no limit.
The SSL/TLS backend to configure in curl if multiple are available (requires libcurl 7.56 or newer). A list of available options is logged on level 2 if nothing is configured. Similar but on level 1 if the selected backend isn't available.
Always use the configured server address. This might be helpful if the DHCP server runs on the same host as strongSwan, and the DHCP daemon does not listen on the loopback interface. In that case the server cannot be reached via unicast (or even 255.255.255.255) as that would be routed via loopback. Setting this option to yes and configuring the local broadcast address (e.g. 192.168.0.255) as server address might work.
Derive user-defined MAC address from hash of IKE identity and send client identity DHCP option.
Interface name the plugin uses for address allocation. The default is to bind to any (0.0.0.0) and let the system decide which way to route the packets to the DHCP server.
DHCP server unicast or broadcast IP address.
Use the DHCP server port (67) as source port, instead of the DHCP client port (68), when a unicast server address is configured and the plugin acts as relay agent. When replying in this mode the DHCP server will always send packets to the DHCP server port and if no process binds that port an ICMP port unreachables will be sent back, which might be problematic for some DHCP servers. To avoid that, enabling this option will cause the plugin to bind the DHCP server port to send its requests when acting as relay agent. This is not necessary if a DHCP server is already running on the same host and might even cause conflicts (and since the server port is already bound, ICMPs should not be an issue).
Enable fetching of CERT RRs via DNS.
Number of pseudo-random bit requests from the DRBG before an automatic reseeding occurs.
Enable duplicheck plugin (if loaded).
Socket provided by the duplicheck plugin.
Enable to activate sequence check of the AKA SQN values in order to trigger resync cycles.
Enable to activate sequence check of the AKA SQN values in order to trigger resync cycles.
If enabled the EAP methods proposed in an EAP-Nak message sent by the peer are preferred over the methods registered locally.
The preferred EAP method(s) to be used. If it is not given the first registered method will be used initially. If a comma separated list is given the methods are tried in the given order before trying the rest of the registered methods.
XAuth backend to be used for credential verification.
Maximum size of an EAP-PEAP packet.
Include length in non-fragmented EAP-PEAP packets.
Maximum number of processed EAP-PEAP packets (0 = no limit).
Phase2 EAP client authentication method.
Phase2 EAP Identity request piggybacked by server onto TLS Finished message, relevant only if TLS 1.2 or earlier is negotiated.
Start phase2 EAP TNC protocol after successful client authentication.
Request peer authentication based on a client certificate.
Send RADIUS accounting information to RADIUS servers.
Close the IKE_SA if there is a timeout during interim RADIUS accounting updates.
Interval in seconds for interim RADIUS accounting updates, if not specified by the RADIUS server in the Access-Accept message.
If enabled, accounting is disabled unless an IKE_SA has at least one virtual IP. Only for IKEv2, for IKEv1 a virtual IP is strictly necessary.
If enabled, adds the Class attributes received in Access-Accept message to the RADIUS accounting messages.
Use the class attribute sent in the RADIUS-Accept message as group membership information that is compared to the groups specified in the rightgroups option in ipsec.conf(5).
Closes all IKE_SAs if communication with the RADIUS server times out. If it is not set only the current IKE_SA is closed.
Enables support for the Dynamic Authorization Extension (RFC 5176).
Address to listen for DAE messages from the RADIUS server.
Port to listen for DAE requests.
Shared secret used to verify/sign DAE messages. If set, make sure to adjust the permissions of the config file accordingly.
Send EAP-Start instead of EAP-Identity to start RADIUS conversation.
If the RADIUS tunnel_type attribute with value ESP is received, use the filter_id attribute sent in the RADIUS-Accept message as group membership information that is compared to the groups specified in the rightgroups option in ipsec.conf(5).
RADIUS attributes to be forwarded from IKEv2 to RADIUS (can be defined by name or attribute number, a colon can be used to specify vendor-specific attributes, e.g. Reply-Message, or 11, or 36906:12).
Same as charon.plugins.eap-radius.forward.ike_to_radius but from RADIUS to IKEv2, a strongSwan specific private notify (40969) is used to transmit the attributes.
Prefix to EAP-Identity, some AAA servers use a IMSI prefix to select the EAP method.
NAS-Identifier to include in RADIUS messages.
Port of RADIUS server (authentication).
Base to use for calculating exponential back off.
Timeout in seconds before sending first retransmit.
Number of times to retransmit a packet before giving up.
Shared secret between RADIUS and NAS. If set, make sure to adjust the permissions of the config file accordingly.
IP/Hostname of RADIUS server.

Section to specify multiple RADIUS servers. The nas_identifier, secret, sockets and port (or auth_port) options can be specified for each server. A server's IP/Hostname can be configured using the address option. The acct_port [1813] option can be used to specify the port used for RADIUS accounting. For each RADIUS server a priority can be specified using the preference [0] option. The retransmission time for each server can set set using retransmit_base, retransmit_timeout and retransmit_tries.
Number of sockets (ports) to use, increase for high load.
Whether to include the UDP port in the Called- and Calling-Station-Id RADIUS attributes.

Section to configure multiple XAuth authentication rounds via RADIUS. The subsections define so called authentication profiles with arbitrary names. In each profile section one or more XAuth types can be configured, with an assigned message. For each type a separate XAuth exchange will be initiated and all replies get concatenated into the User-Password attribute, which then gets verified over RADIUS.

Available XAuth types are password, passcode, nextpin, and answer. This type is not relevant to strongSwan or the AAA server, but the client may show a different dialog (along with the configured message).

To use the configured profiles, they have to be configured in the respective connection in ipsec.conf(5) by appending the profile name, separated by a colon, to the xauth-radius XAauth backend configuration in rightauth or rightauth2, for instance, rightauth2=xauth-radius:profile.

Maximum size of an EAP-TLS packet.
Include length in non-fragmented EAP-TLS packets.
Maximum number of processed EAP-TLS packets (0 = no limit).
Maximum number of processed EAP-TNC packets (0 = no limit).
IF-TNCCS protocol version to be used (tnccs-1.1, tnccs-2.0, tnccs-dynamic).
Maximum size of an EAP-TTLS packet.
Include length in non-fragmented EAP-TTLS packets.
Maximum number of processed EAP-TTLS packets (0 = no limit).
Phase2 EAP client authentication method.
Phase2 EAP Identity request piggybacked by server onto TLS Finished message.
Start phase2 EAP TNC protocol after successful client authentication.
Phase2 EAP TNC transport protocol (pt as IETF standard or legacy tnc)
Request peer authentication based on a client certificate.
Socket provided by the error-notify plugin.
Command to pass to the system shell for peer authorization. Authorization is considered successful if the command executes normally with an exit code of zero. For all other exit codes IKE_SA authorization is rejected.

The following environment variables get passed to the script: IKE_UNIQUE_ID: The IKE_SA numerical unique identifier. IKE_NAME: The peer configuration connection name. IKE_LOCAL_HOST: Local IKE IP address. IKE_REMOTE_HOST: Remote IKE IP address. IKE_LOCAL_ID: Local IKE identity. IKE_REMOTE_ID: Remote IKE identity. IKE_REMOTE_EAP_ID: Remote EAP or XAuth identity, if used.

Comma separated list of multicast groups to join locally. The local host receives and forwards packets in the local LAN for joined multicast groups only. Packets matching the list of multicast groups get forwarded to connected clients. The default group includes host multicasts, IGMP, mDNS, LLMNR and SSDP/WS-Discovery, and is usually a good choice for Windows clients.
Name of the local interface to listen for broadcasts messages to forward. If no interface is configured, the first usable interface is used, which is usually just fine for single-homed hosts. If your host has multiple interfaces, set this option to the local LAN interface you want to forward broadcasts from/to.
Comma separated list of CHILD_SA configuration names for which to perform multi/broadcast reinjection. For clients connecting over such a configuration, any multi/broadcast received over the tunnel gets reinjected to all active tunnels. This makes the broadcasts visible to other peers, and for examples allows clients to see others shares. If disabled, multi/broadcast messages received over a tunnel are injected to the local network only, but not to other IPsec clients.
Use faster random numbers in gcrypt; for testing only, produces weak keys!
Interval in seconds to automatically balance handled segments between nodes. Set to 0 to disable.
Buffer size for received HA messages. For IKEv1 the public DH factors are also transmitted so depending on the DH group the HA messages can get quite big (the default should be fine up to modp4096).
Enable fetching of IPSECKEY RRs via DNS.
Allow that the remote traffic selector equals the IKE peer. The route installed for such traffic (via TUN device) usually prevents further IKE traffic. The fwmark options for the kernel-netlink and socket-default plugins can be used to circumvent that problem.
Firewall mark to set on outbound raw ESP packets.
Whether to send and receive ESP packets without UDP encapsulation if supported on this platform and no NAT is detected.
Buffer size for received Netlink messages.
Firewall mark to set on the routing rule that directs traffic to our routing table. The format is [!]mark[/mask], where the optional exclamation mark inverts the meaning (i.e. the rule only applies to packets that don't match the mark).
If the kernel supports hardware offloading, the plugin needs to find the feature flag which represents hardware offloading support for network devices. Using the loopback device for this purpose is usually fine, since it should always be present. For rare cases in which the loopback device cannot be used to obtain the appropriate feature flag, this option can be used to specify an alternative interface for offload feature detection.
Whether to ignore errors potentially resulting from a retransmission.
Whether routes via XFRM interfaces are automatically installed for SAs that reference such an interface via if_id_out. If the traffic selectors include the IKE traffic to the peer, this requires special care (e.g. installing bypass policies and/or routes, or setting a mark on the IKE socket and excluding such packets from the configured routing table via fwmark option).
MSS to set on installed routes, 0 to disable.
MTU to set on installed routes, 0 to disable.
Whether to perform concurrent Netlink ROUTE queries on a single socket. While parallel queries can improve throughput, it has more overhead. On vanilla Linux, DUMP queries fail with EBUSY and must be retried, further decreasing performance.
Whether to perform concurrent Netlink XFRM queries on a single socket.
Whether to always use XFRM_MSG_UPDPOLICY to install policies.
Whether to use port or socket based IKE XFRM bypass policies. IKE bypass policies are used to exempt IKE traffic from XFRM processing. The default socket based policies are directly tied to the IKE UDP sockets, port based policies use global XFRM bypass policies for the used IKE UDP ports.
Whether to process changes in routing rules to trigger roam events. This is currently only useful if the kernel based route lookup is used (i.e. if route installation is disabled or an inverted fwmark match is configured).
Maximum Netlink socket receive buffer in bytes. This value controls how many bytes of Netlink messages can be queued to a Netlink socket. If set to 0, the default from /proc/sys/net/core/rmem_default will apply. Note that the kernel doubles the configured value to account for overhead. To exceed the system-wide maximum from /proc/sys/net/core/rmem_max, special privileges (CAP_NET_ADMIN) are necessary, otherwise, the kernel silently caps the value.
Number of Netlink message retransmissions to send on timeout.
Whether to trigger roam events when interfaces, addresses or routes change.
Whether to set protocol and ports in the selector installed on transport mode IPsec SAs in the kernel. While doing so enforces policies for inbound traffic, it also prevents the use of a single IPsec SA by more than one traffic selector.

XFRM policy hashing threshold configuration for IPv4 and IPv6.

The section defines hashing thresholds to configure in the kernel during daemon startup. Each address family takes a threshold for the local subnet of an IPsec policy (src in out-policies, dst in in- and forward-policies) and the remote subnet (dst in out-policies, src in in- and forward-policies).

If the subnet has more or equal net bits than the threshold, the first threshold bits are used to calculate a hash to lookup the policy.

Policy hashing thresholds are not supported before Linux 3.18 and might conflict with socket policies before Linux 4.8.

Local subnet XFRM policy hashing threshold for IPv4.
Remote subnet XFRM policy hashing threshold for IPv4.
Local subnet XFRM policy hashing threshold for IPv6.
Remote subnet XFRM policy hashing threshold for IPv6.
Netlink message retransmission timeout, 0 to disable retransmissions.
Lifetime of XFRM acquire state created by the kernel when traffic matches a trap policy. The value gets written to /proc/sys/net/core/xfrm_acq_expires. Indirectly controls the delay between XFRM acquire messages triggered by the kernel for a trap policy. The same value is used as timeout for SPIs allocated by the kernel. The default value equals the total retransmission timeout for IKE messages, see IKEv2 RETRANSMISSION in strongswan.conf(5).
Size of the receive buffer for the event socket (0 for default size). Because events are received asynchronously installing e.g. lots of policies may require a larger buffer than the default on certain platforms in order to receive all messages.
Whether to use the internal or external interface in installed routes. The internal interface is the one where the IP address contained in the local traffic selector is located, the external interface is the one over which the destination address of the IPsec tunnel can be reached. This is not relevant if virtual IPs are used, for which a TUN device is created that's used in the routes.
MTU to set on TUN devices created for virtual IPs.
Time in ms to wait until virtual IP addresses appear/disappear before failing.

Section to configure the load-tester plugin, see LOAD TESTS in strongswan.conf(5) for details.

Section that contains key/value pairs with address pools (in CIDR notation) to use for a specific network interface e.g. eth0 = 10.10.0.0/16.
Whether to keep dynamic addresses even after the associated SA got terminated.
Network prefix length to use when installing dynamic addresses. If set to -1 the full address is used (i.e. 32 or 128).
Directory to load (intermediate) CA certificates from.
Seconds to start CHILD_SA rekeying after setup.
URI to a CRL to include as certificate distribution point in generated certificates.
Delay between initiations for each thread.
Delete an IKE_SA as soon as it has been established.
Digest algorithm used when issuing certificates.
DPD delay to use in load test.
Base port to be used for requests (each client uses a different port).
EAP secret to use in load test.
Enable the load testing plugin. WARNING: Never enable this plugin on productive systems. It provides preconfigured credentials and allows an attacker to authenticate as any user.
CHILD_SA proposal to use for load tests.
Fake the kernel interface to allow load-testing against self.
Seconds to start IKE_SA rekeying after setup.
Global limit of concurrently established SAs during load test.
Address to initiate from.
Authentication method(s) the initiator uses.
Initiator ID used in load test.
Initiator ID to match against as responder.
Traffic selector on initiator side, as proposed by initiator.
Traffic selector on responder side, as proposed by initiator.
Number of concurrent initiator threads to use in load test.
Path to the issuer certificate (if not configured a hard-coded default value is used).
Path to private key that is used to issue certificates (if not configured a hard-coded default value is used).
Number of IKE_SAs to initiate by each initiator in load test.
IPsec mode to use, one of tunnel, transport, or beet.
Provide INTERNAL_IPV4_ADDRs from a named pool.
Preshared key to use in load test.
IKE proposal to use in load test.
Request an INTERNAL_IPV4_ADDR and INTERNAL_IPV6_ADDR from the server.
Address to initiation connections to.
Authentication method(s) the responder uses.
Responder ID used in load test.
Traffic selector on initiator side, as narrowed by responder.
Traffic selector on responder side, as narrowed by responder.
Shutdown the daemon after all IKE_SAs have been established.
Socket provided by the load-tester plugin.
IKE version to use (0 means use IKEv2 as initiator and accept any version as responder).
Socket provided by the lookip plugin.
The following parameter sets are available: x9_98_speed, x9_98_bandwidth, x9_98_balance and optimum, the last set not being part of the X9.98 standard but having the best performance.
ENGINE ID to use in the OpenSSL plugin.
Set OpenSSL FIPS mode. With OpenSSL before 3.0, the supported values are disabled(0), enabled(1) and Suite B enabled(2). With OpenSSL 3+, any value other than 0 will explicitly load the fips and base providers (load_legacy will be ignored). The latter still requires the config in fipsmodule.cnf (e.g. for the module's MAC), but allows explicitly loading the provider if it's not activated in that config.
Load the legacy provider in OpenSSL 3+ for algorithms like MD4, DES, or Blowfish (the first two are required for EAP-MSCHAPv2). If disabled, the default provider is loaded, or those configured in the OpenSSL config (e.g. the fips provider).
Database URI connecting to the OpenXPKI certificate database. If it contains a password, make sure to adjust the permissions of the config file accordingly.
Whether DNS servers are appended to existing entries, instead of replacing them.

Section to enable requesting P-CSCF server addresses for individual connections.
<conn> is the name of a connection with an ePDG from which to request P-CSCF server addresses. Requests will be sent for addresses of the same families for which internal IPs are requested.

List of available PKCS#11 modules.
Whether to automatically load certificates from tokens.
Whether OS locking should be enabled for this module.
Full path to the shared object file of this PKCS#11 module.
Reload certificates from all tokens if charon receives a SIGHUP.
Whether the PKCS#11 modules should be used for DH and ECDH (see use_ecc option).
Whether the PKCS#11 modules should be used for ECDH and ECDSA public key operations. ECDSA private keys can be used regardless of this option.
Whether the PKCS#11 modules should be used to hash data.
Whether the PKCS#11 modules should be used for public key operations, even for keys not stored on tokens.
Whether the PKCS#11 modules should be used as RNG.
Whether the PKCS#11 modules should try to use internal hashing for RSA-PSS signatures (some PKCS#11 libraries don't implement internal hashing in conjunction with RSA-PSS correctly).
Directory where RADIUS attributes are stored in client-ID specific files.
Attributes are added to all IKE_AUTH messages by default (-1), or only to the IKE_AUTH message with the given IKEv2 message ID.
File to read random bytes from.
If set to yes the RNG_STRONG class reads random bytes from the same source as the RNG_TRUE class.
File to read pseudo random bytes from.
File where to add DNS server entries if not using resolvconf(8).
The interface name and protocol sent to resolvconf(8). This has to be a valid interface name according to the rules defined by resolvconf. Also, it should have a high priority according to the order defined in interface-order(5) if relevant on the system.
Path/command for resolvconf(8). The command is executed by a shell, so "resolvconf" will work if it's in $PATH of the daemon.

If not configured, resolvconf(8) will be used if found at the default location. Otherwise, the file in charon.plugins.resolve.file will be modified directly.

Whether CRL validation should be enabled.
Whether OCSP validation should be enabled.
Timeout used when fetching OCSP/CRL.
Whether to save ESP keys.
Whether to save IKE keys.
Whether to load the plugin.
Directory where the keys are stored in the format supported by Wireshark. IKEv1 keys are stored in the ikev1_decryption_table file. IKEv2 keys are stored in the ikev2_decryption_table file. Keys for ESP CHILD_SAs are stored in the esp_sa file.
Firewall mark to set on outbound packets.
Set source address on outbound packets, if possible.
Force sending interface on outbound packets, if possible. This allows using IPv6 link-local addresses as tunnel endpoints.
Listen on IPv4, if possible.
Listen on IPv6, if possible.
Database URI for charon's SQL plugin. If it contains a password, make sure to adjust the permissions of the config file accordingly.
Loglevel for logging to SQL database.
Analyze addresses/hostnames in left|right to detect which side is local and swap configuration options if necessary. If disabled left is always local.
Treat certificates in ipsec.d/cacerts and ipsec.conf ca sections as CA certificates even if they don't contain a CA basic constraint.
Maximum number of stroke messages handled concurrently.
If enabled log level changes via stroke socket are not allowed.
Location of the ipsec.secrets file
Socket provided by the stroke plugin.
Timeout in ms for any stroke command. Use 0 to disable the timeout.
Interval in seconds to check system time for validity. 0 disables the check.
Whether to use reauth or delete if an invalid cert lifetime is detected.
Threshold date where system time is considered valid. Disabled if not specified.
strptime(3) format used to parse threshold option.
How long to wait for a valid system time if an interval is configured. 0 to recheck indefinitely.
Path to X.509 certificate file of IF-MAP client.
Path to private key file of IF-MAP client.
Unique name of strongSwan server as a PEP and/or PDP device.
Interval in seconds between periodic IF-MAP RenewSession requests.
Path to X.509 certificate file of IF-MAP server.
URI of the form [https://]servername[:port][/path].
Credentials of IF-MAP client of the form username:password. If set, make sure to adjust the permissions of the config file accordingly.
Unload IMC after use.
Preferred language for TNC recommendations.
Unload IMV after use.
TNC recommendation policy, one of default, any, or all.
Enable PT-TLS protocol on the strongSwan PDP.
PT-TLS server port the strongSwan PDP is listening on.
Enable RADIUS protocol on the strongSwan PDP.
EAP tunnel method to be used.
RADIUS server port the strongSwan PDP is listening on.
Shared RADIUS secret between strongSwan PDP and NAS. If set, make sure to adjust the permissions of the config file accordingly.
Name of the strongSwan PDP as contained in the AAA certificate.
Timeout in seconds before closing incomplete connections.
Maximum size of a PA-TNC message (XML & Base64 encoding).
Maximum size of a PB-TNC batch (upper limit via PT-EAP = 65529).
Maximum size of a PA-TNC message (upper limit via PT-EAP = 65497).
Enable PB-TNC mutual protocol.
Send an unsupported PB-TNC message type with the NOSKIP flag set.
Send a PB-TNC batch with a modified PB-TNC version.
Handle of the RSA or ECC Endorsement Key (EK) to be used to set up an authenticated session with a TPM 2.0 (e.g. 0x81010001).
Is the TPM 2.0 FIPS-186-4 compliant, forcing e.g. the use of the default salt length instead of maximum salt length with RSAPSS padding.
Name of TPM 2.0 TCTI library. Valid values: tabrmd, device or mssim. Defaults are device if the /dev/tpmrm0 in-kernel TPM 2.0 resource manager device exists, and tabrmd otherwise, requiring the d-bus based TPM 2.0 access broker and resource manager to be available.
Options for the TPM 2.0 TCTI library. Defaults are /dev/tpmrm0 if the TCTI library name is device and no options otherwise.
Whether the TPM should be used as RNG. For security reasons enable only if an authenticated session can be set up (see ek_handle option).
File to read trusted keys for DLV (DNSSEC Lookaside Validation) from. It uses the same format as trust_anchors. Only one DLV can be configured, which is then used as a root trusted DLV, this means that it is a lookaside for the root.
File to read DNS resolver configuration from.
File to read DNSSEC trust anchors from (usually root zone KSK). The format of the file is the standard DNS Zone file format, anchors can be stored as DS or DNSKEY entries in the file.
Whether the updown script should handle DNS servers assigned via IKEv1 Mode Config or IKEv2 Config Payloads (if enabled they can't be handled by other plugins, like resolve)
Socket the vici plugin serves clients.
Enable loaded whitelist plugin.
Socket provided by the whitelist plugin.
Enable to prevent loading the plugin if wolfSSL is not in FIPS mode.
EAP plugin to be used as backend for XAuth credential verification.
PAM service to be used for authentication.
Open/close a PAM session for each active IKE_SA.
If an email address is received as an XAuth username, trim it to just the username part.
UDP port used locally. If set to 0 a random port will be allocated.
UDP port used locally in case of NAT-T. If set to 0 a random port will be allocated. Has to be different from charon.port, otherwise a random port will be allocated.
By default, charon keeps SAs on the routing path with addresses it previously used if that path is still usable. By setting this option to yes, it tries more aggressively to update SAs with MOBIKE on routing priority changes using the cheapest path. This adds more noise, but allows to dynamically adapt SAs to routing priority changes. This option has no effect if MOBIKE is not supported or disabled.
Prefer locally configured proposals for IKE/IPsec over supplied ones as responder (disabling this can avoid keying retries due to INVALID_KE_PAYLOAD notifies).
By default, permanent IPv6 source addresses are preferred over temporary ones (RFC 4941), to make connections more stable. Enable this option to reverse this.

It also affects which IPv6 addresses are announced as additional addresses if MOBIKE is used. If the option is disabled, only permanent addresses are sent, and only temporary ones if it is enabled.

Process RTM_NEWROUTE and RTM_DELROUTE events.

Section to configure the number of reserved threads per priority class see JOB PRIORITY MANAGEMENT in strongswan.conf(5).
How RDNs in subject DNs of certificates are matched against configured identities. Possible values are strict (the default), reordered, and relaxed. With strict the number, type and order of all RDNs has to match, wildcards (*) for the values of RDNs are allowed (that's the case for all three variants). Using reordered also matches DNs if the RDNs appear in a different order, the number and type still has to match. Finally, relaxed also allows matches of DNs that contain more RDNs than the configured identity (missing RDNs are treated like a wildcard match).

Note that reordered and relaxed impose a considerable overhead on memory usage and runtime, in particular, for mismatches, compared to strict.

Delay in ms for receiving packets, to simulate larger RTT.
Delay request messages.
Delay response messages.
Specific IKEv2 message type to delay, 0 for any.
Reject peers that use trusted end-entity certificates (i.e. local certificates).
Size of the AH/ESP replay window, in packets.
Value of the first reqid to be automatically assigned to a CHILD_SA.
Base to use for calculating exponential back off, see IKEv2 RETRANSMISSION in strongswan.conf(5).
Maximum jitter in percent to apply randomly to calculated retransmission timeout (0 to disable).
Upper limit in seconds for calculated retransmission timeout (0 to disable).
Timeout in seconds before sending first retransmit.
Number of times to retransmit a packet before giving up.
Interval in seconds to use when retrying to initiate an IKE_SA (e.g. if DNS resolution failed), 0 to disable retries.
Initiate CHILD_SA within existing IKE_SAs (always enabled for IKEv1).
Numerical routing table to install routes to.
Priority of the routing table.
Whether to use RSA with PSS padding instead of PKCS#1 padding by default.
Whether to encode an explicit trailerField value of 0x01 in the RSA-PSS algorithmIdentifier (CONTEXT3) or using the DEFAULT value by omitting it.
Delay in ms for sending packets, to simulate larger RTT.
Delay request messages.
Delay response messages.
Specific IKEv2 message type to delay, 0 for any.
Send strongSwan vendor ID payload
Whether to enable Signature Authentication as per RFC 7427.
If enabled, signature schemes configured in rightauth, in addition to getting used as constraints against signature schemes employed in the certificate chain, are also used as constraints against the signature scheme used by peers during IKEv2.
Value mixed into the local IKE SPIs after applying spi_mask.
Mask applied to local IKE SPIs before mixing in spi_label (bits set will be replaced with spi_label).
The upper limit for SPIs requested from the kernel for IPsec SAs.
The lower limit for SPIs requested from the kernel for IPsec SAs. Should not be set lower than 0x00000100 (256), as SPIs between 1 and 255 are reserved by IANA.

Section containing a list of scripts (name = path) that are executed when the daemon is started.

Section containing a list of scripts (name = path) that are executed when the daemon is terminated.

Section to define syslog loggers, see LOGGER CONFIGURATION in strongswan.conf(5).

<facility> is one of the supported syslog facilities, see LOGGER CONFIGURATION in strongswan.conf(5).
Loglevel for a specific subsystem.
Specifies the default loglevel to be used for subsystems for which no specific loglevel is defined.
Prefix each log entry with the connection name and a unique numerical identifier for each IKE_SA.
Add the log level of each message after the subsystem (e.g. [IKE2]).
The default setting of -1 passes all messages to syslog using a log level of LOG_INFO. A non-negative value maps the strongSwan specific loglevels (0..4) to the syslog level starting at the specified number. For example, a value of 5 (LOG_NOTICE) maps strongSwan loglevel 0 to LOG_NOTICE, level 1 to LOG_INFO, and levels 2, 3 and 4 to LOG_DEBUG. This allows (additional) filtering of log messages on the syslog server.
Global identifier used for an openlog(3) call, prepended to each log message by syslog. If not configured, openlog(3) is not called, so the value will depend on system defaults (often the program name).
Number of worker threads in charon. Several of these are reserved for long running tasks in internal modules and plugins. Therefore, make sure you don't set this value too low. The number of idle worker threads listed in ipsec statusall might be used as indicator on the number of reserved threads.
List of TLS encryption ciphers.
List of TLS key exchange groups.
List of TLS key exchange methods.
List of TLS MAC algorithms.
Whether to include CAs in a server's CertificateRequest message. May be disabled if clients can't handle a long list of CAs.
List of TLS signature schemes.
List of TLS cipher suites.
Maximum TLS version to negotiate.
Minimum TLS version to negotiate.
TNC IMC/IMV configuration file.
Name of the user the daemon changes to after startup.
Discard certificates with unsupported or unknown critical extensions.
Directory from which to load CA certificates if no certificate is configured.
MTU for XFRM interfaces created by the NM plugin.

Section to configure native systemd journal logger, very similar to the syslog logger as described in LOGGER CONFIGURATION in strongswan.conf(5).
Loglevel for a specific subsystem.
Specifies the default loglevel to be used for subsystems for which no specific loglevel is defined.
Shell command to be executed with recommendation allow.
Shell command to be executed with all other recommendations.
Database URI for the database that stores the package information. If it contains a password, make sure to adjust the permissions of the config file accordingly.
Plugins to load in IMV policy manager.
Debug level for a stand-alone libimcv library.
Plugins to load in IMC/IMVs with stand-alone libimcv library.
AIK encrypted private key blob file.
AIK certificate file.
AIK object handle.
AIK public key file.
Preferred measurement hash algorithm.
Enforce mandatory Diffie-Hellman groups.
DH nonce length.
PCR17 value after measurement.
PCR17 value before measurement.
Dummy measurement value extended into PCR17 if the TBOOT log is not available.
PCR18 value after measurement.
PCR18 value before measurement.
Dummy measurement value extended into PCR17 if the TBOOT log is not available.
Whether to send pcr_before and pcr_after info.
Whether to pad IMA SHA1 measurements values when extending into SHA256 PCR bank.
Use Quote2 AIK signature instead of Quote signature.
Version Info is included in Quote2 signature.
Send quadruple info without being prompted.
Section to define PWG HCD PA subtypes.
Defines a PWG HCD PA subtype section. Recognized subtype section names are system, control, marker, finisher, interface and scanner.
Defines a software type section. Recognized software type section names are firmware, resident_application and user_application.
Defines a software section having an arbitrary name.
Name of the software installed on the hardcopy device.
String describing all patches applied to the given software on this hardcopy device. The individual patches are separated by a newline character '\n'.
String describing the version of the given software on this hardcopy device.
Hex-encoded version string with a length of 16 octets consisting of the fields major version number (4 octets), minor version number (4 octets), build number (4 octets), service pack major number (2 octets) and service pack minor number (2 octets).
Variable length natural language tag conforming to RFC 5646 specifies the language to be used in the health assessment message of a given subtype.
Hex-encoded certification state.
Hex-encoded configuration state.
String specifying the machine type and model of the hardcopy device.
Specifies if a PSTN facsimile interface is installed and enabled on the hardcopy device.
String specifying the hostname of the network time server used by the hardcopy device.
Specifies if users can dynamically download and execute applications on the hardcopy device.
Specifies if user dynamically downloaded applications can persist outside the boundaries of a single job on the hardcopy device.
String specifying the manufacturer of the hardcopy device.
Integer specifying the globally unique 24-bit SMI code assigned to the manufacturer of the hardcopy device.
Manually set the path to the client device certificate (e.g. /etc/pts/aikCert.der)
Manually set handle to a private key bound to a smartcard or TPM (e.g. 0x81010004)
Manually set the client device ID in hexadecimal format (e.g. 1083f03988c9762703b1c1080c2e46f72b99cc31)
Manually set the path to the client device public key (e.g. /etc/pts/aikPub.der)
Send operating system info without being prompted.
Send open listening ports without being prompted.
Set 32 bit epoch value for event IDs manually if software collector database is not available.
Accept SW Inventory or SW Events subscriptions.
URI to software collector database containing event timestamps, software creation and deletion events and collected software identifiers. If it contains a password, make sure to adjust the permissions of the config file accordingly.
Directory where SWID tags are located.
Include file information in the XML-encoded SWID tags.
Generate XML-encoded SWID tags with pretty indentation.
Number of additional IMC IDs.
Command to be sent to the Test IMV.
Size of dummy attribute to be sent to the Test IMV (0 = disabled).
Do a handshake retry.
Command to be sent to the Test IMV in the handshake retry.
Path to directory with AIK cacerts.
Preferred Diffie-Hellman group.
Preferred measurement hash algorithm.
Enforce mandatory Diffie-Hellman groups.
DH minimum nonce length.
URI pointing to operating system remediation instructions.
URI pointing to scanner remediation instructions.
Timeout of SWID REST API HTTP POST transaction.
HTTP URI of the SWID REST API.
Number of IMC-IMV retry rounds.
Disable output to stderr with a stand-alone libimcv library.
SWID generator command to be executed.
Name of the tagCreator entity.
regid of the tagCreator entity.
Credential database URI for manager. If it contains a password, make sure to adjust the permissions of the config file accordingly.
Enable debugging in manager.
Plugins to load in manager.
FastCGI socket of manager, to run it statically.
Threads to use for request handling.
Session timeout for manager.
Mediation server database URI. If it contains a password, make sure to adjust the permissions of the config file accordingly.
Debugging in mediation server web application.
DPD timeout to use in mediation server plugin.
Plugins to load in mediation server plugin.
Minimum password length required for mediation server user accounts.
Rekeying time on mediation connections in mediation server plugin.
Run Mediation server web application statically on socket.
Number of thread for mediation service web application.
Session timeout for mediation service.
Plugins to load in the pki tool.
Source IP address to bind for HTTP operations.
Timeout for HTTP operations.
Some SCEP servers (e.g. openxpki) are incorrectly doing certificate renewal via messageType PKCSReq (19) instead of RenewalReq (17).
Database URI for the database that stores IP pools and configuration attributes. If it contains a password, make sure to adjust the permissions of the config file accordingly.
Plugins to load in ipsec pool tool.

Options for the sec-updater tool.
Global IMV policy database URI. If it contains a password, make sure to adjust the permissions of the config file accordingly.
Plugins to load in sec-updater tool.
SWID generator command to be executed.
Name of the tagCreator entity.
regid of the tagCreator entity.
Temporary storage for downloaded deb package file.
Temporary storage for generated SWID tags.
strongTNC manage.py command used to import SWID tags.
Location of the ipsec.conf file
Disable charon plugin load option warning.

Options for the sw-collector tool.
URI to software collector database containing event timestamps, software creation and deletion events and collected software identifiers. If it contains a password, make sure to adjust the permissions of the config file accordingly.
Path pointing to file created when the Linux OS was installed.
Time in UTC when the Linux OS was installed.
Path pointing to apt history.log file.
Plugins to load in sw-collector tool.
Timeout of REST API HTTP POST transaction.
HTTP URI of the central collector's REST API.
Plugins to load in swanctl.
VICI socket to connect to by default.

Options in strongswan.conf(5) provide a much more flexible way to configure loggers for the IKE daemon charon than using the charondebug option in ipsec.conf(5).

Note: If any loggers are specified in strongswan.conf, charondebug does not have any effect.

There are currently two types of loggers:

Log directly to a file and are defined by specifying an arbitrarily named subsection in the charon.filelog section. The full path to the file is configured in the path setting of that subsection, however, if it only contains characters permitted in section names, the setting may also be omitted and the path specified as name of the subsection. To log to the console the two special filenames stdout and stderr may be used.
Log into a syslog facility and are defined by specifying the facility to log to as the name of a subsection in the charon.syslog section. The following facilities are currently supported: daemon and auth.

Multiple loggers can be defined for each type with different log verbosity for the different subsystems of the daemon.

Main daemon setup/cleanup/signal handling
IKE_SA manager, handling synchronization for IKE_SA access
IKE_SA
CHILD_SA
Jobs queueing/processing and thread pool management
Configuration management and plugins
IPsec/Networking kernel interface
IKE network communication
Low-level encoding/decoding (ASN.1, X.509 etc.)
Packet encoding/decoding encryption/decryption operations
libtls library messages
libipsec library messages
libstrongswan library messages
Trusted Network Connect
Integrity Measurement Collector
Integrity Measurement Verifier
Platform Trust Service

-1
Absolutely silent
0
Very basic auditing logs, (e.g. SA up/SA down)
1
Generic control flow with errors, a good default to see what's going on
2
More detailed debugging control flow
3
Including RAW data dumps in Hex
4
Also include sensitive material in dumps, e.g. keys

charon {
	filelog {
		charon {
			path = /var/log/charon.log
			time_format = %b %e %T
			append = no
			default = 1
		}
		stderr {
			ike = 2
			knl = 3
			ike_name = yes
		}
	}
	syslog {
		# enable logging to LOG_DAEMON, use defaults
		daemon {
		}
		# minimalistic IKE auditing logging to LOG_AUTHPRIV
		auth {
			default = -1
			ike = 0
		}
	}
}

Some operations in the IKEv2 daemon charon are currently implemented synchronously and blocking. Two examples for such operations are communication with a RADIUS server via EAP-RADIUS, or fetching CRL/OCSP information during certificate chain verification. Under high load conditions, the thread pool may run out of available threads, and some more important jobs, such as liveness checking, may not get executed in time.

To prevent thread starvation in such situations job priorities were introduced. The job processor will reserve some threads for higher priority jobs, these threads are not available for lower priority, locking jobs.

Currently 4 priorities have been defined, and they are used in charon as follows:

Priority for long-running dispatcher jobs.
INFORMATIONAL exchanges, as used by liveness checking (DPD).
Everything not HIGH/LOW, including IKE_SA_INIT processing.
IKE_AUTH message processing. RADIUS and CRL fetching block here

Although IKE_SA_INIT processing is computationally expensive, it is explicitly assigned to the MEDIUM class. This allows charon to do the DH exchange while other threads are blocked in IKE_AUTH. To prevent the daemon from accepting more IKE_SA_INIT requests than it can handle, use IKE_SA_INIT DROPPING.

The thread pool processes jobs strictly by priority, meaning it will consume all higher priority jobs before looking for ones with lower priority. Further, it reserves threads for certain priorities. A priority class having reserved n threads will always have n threads available for this class (either currently processing a job, or waiting for one).

To ensure that there are always enough threads available for higher priority tasks, threads must be reserved for each priority class.

Threads reserved for CRITICAL priority class jobs
Threads reserved for HIGH priority class jobs
Threads reserved for MEDIUM priority class jobs
Threads reserved for LOW priority class jobs

Let's consider the following configuration:

charon {
	processor {
		priority_threads {
			high = 1
			medium = 4
		}
	}
}

With this configuration, one thread is reserved for HIGH priority tasks. As currently only liveness checking and stroke message processing is done with high priority, one or two threads should be sufficient.

The MEDIUM class mostly processes non-blocking jobs. Unless your setup is experiencing many blocks in locks while accessing shared resources, threads for one or two times the number of CPU cores is fine.

It is usually not required to reserve threads for CRITICAL jobs. Jobs in this class rarely return and do not release their thread to the pool.

The remaining threads are available for LOW priority jobs. Reserving threads does not make sense (until we have an even lower priority).

To see what the threads are actually doing, invoke ipsec statusall. Under high load, something like this will show up:

worker threads: 2 or 32 idle, 5/1/2/22 working,
	job queue: 0/0/1/149, scheduled: 198

From 32 worker threads,

2
are currently idle.
5
are running CRITICAL priority jobs (dispatching from sockets, etc.).
1
is currently handling a HIGH priority job. This is actually the thread currently providing this information via stroke.
2
are handling MEDIUM priority jobs, likely IKE_SA_INIT or CREATE_CHILD_SA messages.
22
are handling LOW priority jobs, probably waiting for an EAP-RADIUS response while processing IKE_AUTH messages.

The job queue load shows how many jobs are queued for each priority, ready for execution. The single MEDIUM priority job will get executed immediately, as we have two spare threads reserved for MEDIUM class jobs.

If a responder receives more connection requests per seconds than it can handle, it does not make sense to accept more IKE_SA_INIT messages. And if they are queued but can't get processed in time, an answer might be sent after the client has already given up and restarted its connection setup. This additionally increases the load on the responder.

To limit the responder load resulting from new connection attempts, the daemon can drop IKE_SA_INIT messages just after reception. There are two mechanisms to decide if this should happen, configured with the following options:

Limit based on the number of half open IKE_SAs. Half open IKE_SAs are SAs in connecting state, but not yet established.
Limit based on the number of jobs currently queued for processing (sum over all job priorities).

The second limit includes load from other jobs, such as rekeying. Choosing a good value is difficult and depends on the hardware and expected load.

The first limit is simpler to calculate, but includes the load from new connections only. If your responder is capable of negotiating 100 tunnels/s, you might set this limit to 1000. The daemon will then drop new connection attempts if generating a response would require more than 10 seconds. If you are allowing for a maximum response time of more than 30 seconds, consider adjusting the timeout for connecting IKE_SAs (charon.half_open_timeout). A responder, by default, deletes an IKE_SA if the initiator does not establish it within 30 seconds. Under high load, a higher value might be required.

To do stability testing and performance optimizations, the IKE daemon charon provides the load-tester plugin. This plugin allows one to setup thousands of tunnels concurrently against the daemon itself or a remote host.

WARNING: Never enable the load-testing plugin on productive systems. It provides preconfigured credentials and allows an attacker to authenticate as any user.

For public key authentication, the responder uses the "CN=srv, OU=load-test, O=strongSwan" identity. For the initiator, each connection attempt uses a different identity in the form "CN=c1-r1, OU=load-test, O=strongSwan", where the first number indicates the client number, the second the authentication round (if multiple authentication rounds are used).

For PSK authentication, FQDN identities are used. The server uses srv.strongswan.org, the client uses an identity in the form c1-r1.strongswan.org.

For EAP authentication, the client uses a NAI in the form 100000000010001@strongswan.org.

To configure multiple authentication rounds, concatenate multiple methods using, e.g.

initiator_auth = pubkey|psk|eap-md5|eap-aka

The responder uses a hardcoded certificate based on a 1024-bit RSA key. This certificate additionally serves as CA certificate. A peer uses the same private key, but generates client certificates on demand signed by the CA certificate. Install the Responder/CA certificate on the remote host to authenticate all clients.

To speed up testing, the load tester plugin implements a special Diffie-Hellman implementation called modpnull. By setting

proposal = aes128-sha1-modpnull
this wicked fast DH implementation is used. It does not provide any security at all, but allows one to run tests without DH calculation overhead.

In the simplest case, the daemon initiates IKE_SAs against itself using the loopback interface. This will actually establish double the number of IKE_SAs, as the daemon is initiator and responder for each IKE_SA at the same time. Installation of IPsec SAs would fail, as each SA gets installed twice. To simulate the correct behavior, a fake kernel interface can be enabled which does not install the IPsec SAs at the kernel level.

A simple loopback configuration might look like this:

charon {
	# create new IKE_SAs for each CHILD_SA to simulate
	# different clients
	reuse_ikesa = no
	# turn off denial of service protection
	dos_protection = no
	plugins {
		load-tester {
			# enable the plugin
			enable = yes
			# use 4 threads to initiate connections
			# simultaneously
			initiators = 4
			# each thread initiates 1000 connections
			iterations = 1000
			# delay each initiation in each thread by 20ms
			delay = 20
			# enable the fake kernel interface to
			# avoid SA conflicts
			fake_kernel = yes
		}
	}
}

This will initiate 4000 IKE_SAs within 20 seconds. You may increase the delay value if your box can not handle that much load, or decrease it to put more load on it. If the daemon starts retransmitting messages your box probably can not handle all connection attempts.

The plugin also allows one to test against a remote host. This might help to test against a real world configuration. A connection setup to do stress testing of a gateway might look like this:

charon {
	reuse_ikesa = no
	threads = 32
	plugins {
		load-tester {
			enable = yes
			# 10000 connections, ten in parallel
			initiators = 10
			iterations = 1000
			# use a delay of 100ms, overall time is:
			# iterations * delay = 100s
			delay = 100
			# address of the gateway
			remote = 1.2.3.4
			# IKE-proposal to use
			proposal = aes128-sha1-modp1024
			# use faster PSK authentication instead
			# of 1024bit RSA
			initiator_auth = psk
			responder_auth = psk
			# request a virtual IP using configuration
			# payloads
			request_virtual_ip = yes
			# enable CHILD_SA every 60s
			child_rekey = 60
		}
	}
}

Retransmission timeouts in the IKEv2 daemon charon can be configured globally using the three keys listed below:

charon.retransmit_base [1.8]
charon.retransmit_timeout [4.0]
charon.retransmit_tries [5]
charon.retransmit_jitter [0]
charon.retransmit_limit [0]

The following algorithm is used to calculate the timeout:

relative timeout = retransmit_timeout * retransmit_base ^ (n-1)

Where n is the current retransmission count. The calculated timeout can't exceed the configured retransmit_limit (if any), which is useful if the number of retries is high.

If a jitter in percent is configured, the timeout is modified as follows:

relative timeout -= random(0, retransmit_jitter * relative timeout)

Using the default values, packets are retransmitted in:

Retransmission Relative Timeout Absolute Timeout
1 4s 4s
2 7s 11s
3 13s 24s
4 23s 47s
5 42s 89s
giving up 76s 165s

The variables used above are configured as follows:

${piddir}               /var/run
${prefix}               /usr
${sysconfdir}           /etc
${random_device}        /dev/random
${urandom_device}       /dev/urandom

/etc/strongswan.conf       configuration file
/etc/strongswan.d/         directory containing included config snippets
/etc/strongswan.d/charon/  plugin specific config snippets

swanctl.conf(5), swanctl(8), ipsec.conf(5), ipsec.secrets(5), ipsec(8), charon-cmd(8)

Written for the strongSwan project by Tobias Brunner, Andreas Steffen and Martin Willi.

5.9.14