Project

General

Profile

strongSwan on FreeBSD » History » Version 8

« Previous - Version 8/21 (diff) - Next » - Current version
Tobias Brunner, 26.04.2011 18:32
Updated for FreeBSD 8


strongSwan on FreeBSD

With strongSwan 4.3.4 the IKEv2 daemon charon was ported to FreeBSD. There are still some limitations but
it has since been tested by several users (even with an adapted version of our UML test framework).

This document describes how to install strongSwan on FreeBSD 8.2 (see older revisions of this page for instructions for previous releases).

Prepare FreeBSD

The generic FreeBSD kernel does not come with IPsec support. So you will have to compile your own kernel.

Fortunately, starting with FreeBSD 8, the NAT Traversal patch is included in the kernel sources, so you don't
have to apply any patches yourself, if you need that feature.

Build the Kernel

Basic documentation on how to build a custom kernel can be found in the FreeBSD Handbook.

To enable IPsec you'll need to add the following options to your kernel configuration file:

options   IPSEC
device    crypto

You can verify that your kernel has IPsec support using the following command, which should print a list of ipsec specific kernel state.

/sbin/sysctl -a | grep ipsec

If you need NAT Traversal, add the following option to your kernel config:

options   IPSEC_NAT_T

Install Packages

Our test-system was installed using the Developer and Kern-Developer distributions in sysinstall. So there are maybe additional packages required on your system.

The packages required to build strongSwan are as follows:

  • libgmp (optional, depending on configuration)
  • openssl (optional, depending on configuration)
Notes:
  • The printf-Bug in earlier FreeBSD releases has been fixed and backported to FreeBSD 8. Thus, the vstr string library is not required anymore.

Building strongSwan

Get the latest tarball and configure strongSwan as follows (this compiles the GMP plugin, so libgmp is required).
For details refer to InstallationDocumentation.

./configure --enable-kernel-pfkey --enable-kernel-pfroute --disable-kernel-netlink \
            --disable-tools --disable-scripts --disable-pluto --with-group=wheel

Limitations

  • Due to the lack of policy based routes, virtual IPs can not be used (client-side).
  • The kernel-pfroute interface lacks some final tweaks to fully support MOBIKE.