Revision as of 14:24, 13 July 2015

It is possible to connect an Apple Mac with OSX to a FireBrick over IPSEC with IKEv2 and EAP. Regrettably the IPSEC facilities within OSX are not fully enough featured to achieve this alone, so some additional VPN client software can be installed called StrongSwan.

Downloading & installing the StrongSwan Native Client

Visit the download site and download the latest binary. At the time of writing the latest version was strongswan-5.2.2-1.app.zip. Allow the machine to unarchive it; usually by selecting the "Open with Archive Utility" option. This will deposit the StrongSwan.app into your downloads directory. Drag the app from the downloads directory into your Applications folder. This completes installation of the StrongSwan Client.

Getting the CA from the FireBrick

Note: this guide doesn't go into actual configuration of the FireBrick to be an endpoint, merely how to connect your Mac client to it. Therefore it is assumed the certificate already exists on the FireBrick. It may also be that this is emailed to you by whoever maintains your FireBrick, in which case skip this step.

Log into the Firebrick.
Click on the Config menu in the bar on the left.
Click on the Certificates menu beneath that.
You should be presented with a list of certificates installed. Each line will look approximately as follows :
At the right hand end of the row corresponding the the certificate you wish to download, click on the PEM link.

Installing the certificate into OSX

To be continued...

Errors/help

Unsupported integrity algorithm

There is one "gotcha" with StrongSwan on MAC though - it may negotiate an encryption algorithm for the data connection which OS X doesn't support, the FireBrick will create a log like:

failed to create ESP context: unsupported integrity algorithm AES_XCBC_96

This really a bug in the way the StrongSwan app was built - it shouldn't negotiate something if the underlying OS can't do it! However, the easy workaround is to set up an ipsec-proposal to avoid this:

On the FB config editor create a 'Proposals for IPsec AH/ESP security association'.
Give is a name, and set, for example, 3DES-CBC for cryptset.
Then, back in the 'IPsec IKE connection settings' select the new Proposal in the 'ipsec-proposals' drop down.

@@ Line 25: / Line 25: @@
  failed to create ESP context: unsupported integrity algorithm AES_XCBC_96
-This really a bug in the way the StrongSwan app was built - it  shouldn't negotiate something if the underlying OS can't do it! However, the easy workaround is to set up an ipsec-proposal to avoid this.
+This really a bug in the way the StrongSwan app was built - it  shouldn't negotiate something if the underlying OS can't do it! However, the easy workaround is to set up an ipsec-proposal to avoid this:
+#On the FB config editor create a 'Proposals for IPsec AH/ESP security association'.
+#Give is a name, and set, for example, 3DES-CBC for cryptset.
+#Then, back in the 'IPsec IKE connection settings' select the new Proposal in the 'ipsec-proposals' drop down.