Back up to the FireBrick Road Warrior Category Page

Difference between revisions of "FireBrick Road Warrior OSX"

From AAISP Support Site
Jump to navigation Jump to search
[quality revision][quality revision]
Line 40: Line 40:
   
 
You'll then have a swan icon in your clock tool bar at the top (it actually looks like a Dalek!)
 
You'll then have a swan icon in your clock tool bar at the top (it actually looks like a Dalek!)
[[File:OSX-stronSwanMenuIcon.png|thumbnail]]
 
   
 
#Click Add Connection
 
#Click Add Connection
Line 49: Line 48:
   
 
<gallery>
 
<gallery>
 
OSX-stronSwanMenuIcon.png|strongSwan menu icon
 
FireBrick_IPsec_OSX_Dalek.png|Add a Strongswan connection
 
FireBrick_IPsec_OSX_Dalek.png|Add a Strongswan connection
 
FireBrick_IPsec_OSX_connection.png|Strongswan settings
 
FireBrick_IPsec_OSX_connection.png|Strongswan settings

Revision as of 22:36, 10 August 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.

  1. Log into the Firebrick.
  2. Click on the Config menu in the bar on the left.
  3. Click on the Certificates menu beneath that.
  4. You should be presented with a list of certificates installed. Each line will look approximately as follows : Toothless - Cliff s test FB2700 2700-0001-9224 Certificate management.jpg
  5. At the right hand end of the row corresponding the the certificate you wish to download, click on the PEM link.

Installing the CA certificate into OSX

  1. Go to: Applications - Utilities - Keychain Access
  2. In the top/left area named 'Keychains, click on System
  3. In the bottom/left are named 'Category', click on Certificates
  4. Go to: File - Import Items
  5. Select the file you've downloaded, eg ca-cert.pem
  6. Review the certificate and then select Always Trust, you may be asked to confirm your apple user password.

Configure strongSwan

Run strong swan by either:

  1. Go to Applications and click on the strongSwan icon
  2. Use the 'spotlight' search tool neat the clock to search for strongSwan


You'll then have a swan icon in your clock tool bar at the top (it actually looks like a Dalek!)

  1. Click Add Connection
    1. Name: eg FireBrick
    2. Authentication IKEv2 EAP
    3. Server address: IP or Name of your FireBrick
    4. Click OK

Connect!

  1. Click on the Dalek StrongSwan icon once more,
  2. Click your connection name then connect.
  3. The first time, you may be asked to install a 'Helper' application for Strong Swan, your computer password will be required
  4. You'll be prompted for the password, this is the one as set up in the EAP Identity on the FireBrick (in this example, we had set up a user of fred with a password)


Error: 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 AES if the underlying OS can't do it (which as of July 2015 OSX can't manage AES). However, the easy workaround is to set up an ipsec-proposal to avoid this:

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

Here is example config for this:

<IPsec-proposal name="custom" authset="HMAC-SHA1"/>