Forge Home


Manages strongswan via swanctl / VICI.


245 latest version

5.0 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 0.1.0 (latest)
released Sep 1st 2023
This version is compatible with:
  • Puppet Enterprise 2023.2.x, 2023.1.x, 2023.0.x, 2021.7.x, 2021.6.x, 2021.5.x, 2021.4.x, 2021.3.x, 2021.2.x, 2021.1.x, 2021.0.x, 2019.8.x
  • Puppet >= 6.21.0 < 8.0.0

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'zitrlp-strongswan', '0.1.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add zitrlp-strongswan
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install zitrlp-strongswan --version 0.1.0

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.



zitrlp/strongswan — version 0.1.0 Sep 1st 2023


This module allows to manage strongswan on Debian via swanctl / VICI, route-based or otherwise.

Table of Contents

  1. Setup
  2. Usage
  3. Limitations
  4. Development


Besides installing the module, no special setup steps are necessary.


strongswan supplies parameters which are directly mapped to the according blocks in strongswan.conf and swanctl.conf. Therefore, it is recommended to use it via include and put the config into hiera. The keys are named as in strongswan, except that - is replaced by _. Hashes are mapped to blocks. Key/value pairs are mapped to key = value with the exception of include as key. In this case, the = is omitted.

Special Values

There are a few values which are not passed through to the config files:

  • strongswan::route_based: If set to true, XFRM interfaces are added for each interface ID occuring in the config.
  • strongswan::connections/<connection>/base_interface sets the base interface for an XFRM device.
  • strongswan::connections/<connection>/if_id is copied into if_id_in and if_id_out.


  load_modular: yes
        include: strongswan.d/charon/*.conf

yields this strongswan.conf

charon {
    load_modular = true
    plugins {
        include strongswan.d/charon/*.conf


This module was only tested on Debian and uses /etc/network/interfaces (i.e. no networkd etc.) for route based VPNs.


The repo is located at