Project

General

Profile

NetworkManager » History » Version 20

Martin Willi, 15.05.2009 17:26

1 19 Andreas Steffen
h1. NetworkManager
2 1 Martin Willi
3 19 Andreas Steffen
"NetworkManager":http://www.gnome.org/projects/NetworkManager/ allows configuration and control of VPN daemons through a plugin interface. We provide such a plugin for NetworkManager to configure road warrior clients for the most common setups.
4 19 Andreas Steffen
5 1 Martin Willi
NetworkManager uses DBUS to communicate with a plugin loaded by the IKEv2 charon daemon.
6 19 Andreas Steffen
7 1 Martin Willi
The plugin uses a certificate for gateway authentication and supports EAP and RSA authentication for client authentication. PSK is not supported, as it is considered insecure if the secrets are not strong enough. 
8 19 Andreas Steffen
9 20 Martin Willi
You can use any password based EAP method supported by strongSwan (MD5/GTC/MSCHAPv2) or private key authentication. Private keys are either stored in a file or accessed through your ready-to-use ssh-agent. You'll need a certificate matching that key.
10 12 Martin Willi
11 20 Martin Willi
If you configure the gateway certificate directly on the clients, there are no requirements to the certificate. If you deploy CA certificates (supported in 4.3.1+), the gateway certificate will need a subjectAltName including the Hostname of the gateway (the same you enter in the clients configuration).
12 1 Martin Willi
13 20 Martin Willi
h2. Dependencies
14 1 Martin Willi
15 20 Martin Willi
The strongSwan NM plugin and the NetworkManager VPN module are currently written against NetworkManager 7.1. It should be working with your distributors latest packages.
16 19 Andreas Steffen
17 20 Martin Willi
h2. Installation
18 19 Andreas Steffen
19 20 Martin Willi
We provide strongSwan packages for Ubuntu intrepid/jaunty in our "PPA":https://launchpad.net/~strongswan/+archive/ppa.
20 19 Andreas Steffen
21 19 Andreas Steffen
If you are not running Ubuntu/Debian, you have to build strongSwan from source.
22 1 Martin Willi
23 20 Martin Willi
h3. Using strongSwan PPA
24 1 Martin Willi
25 1 Martin Willi
Add our "PPA":https://launchpad.net/~strongswan/+archive/ppa to your _sources.list_ and install the packages:
26 19 Andreas Steffen
<pre>
27 1 Martin Willi
echo "deb http://ppa.launchpad.net/strongswan/ppa/ubuntu intrepid main" >> /etc/apt/sources.list
28 1 Martin Willi
aptitude update
29 19 Andreas Steffen
aptitude install network-manager-strongswan
30 19 Andreas Steffen
</pre>
31 1 Martin Willi
32 20 Martin Willi
h3. Building from source
33 1 Martin Willi
34 20 Martin Willi
To build from source, you additionally need the PAM headers for EAP-GTC and NetworkManager headers for the plugin:
35 19 Andreas Steffen
<pre>
36 1 Martin Willi
aptitude install libpam0g-dev network-manager-dev libnm-util-dev libnm-glib-dev libgnomeui-dev gnome-common
37 1 Martin Willi
</pre>
38 19 Andreas Steffen
39 20 Martin Willi
NM integration works only for IKEv2, but this allows us to disable a lot of IKEv1 legacy stuff. Since on a desktop we have OpenSSL installed anyway, we are going to use libcrypto for all cryptographical operations. --enable-agent builds the ssh-agent private key plugin, EAP plugins are enabled using --enable-eap-gtc --enable-eap-md5 --enable-eap-mschapv2. You may build only what you'll actually use.
40 19 Andreas Steffen
41 19 Andreas Steffen
<pre>
42 1 Martin Willi
# get the strongSwan tarball
43 20 Martin Willi
wget http://download.strongswan.org/strongswan-4.2.14.tar.bz2
44 20 Martin Willi
tar xjf strongswan-4.2.14.tar.bz2
45 20 Martin Willi
cd strongswan-4.2.14
46 1 Martin Willi
47 20 Martin Willi
# build charon with OpenSSL/NM Plugin
48 1 Martin Willi
./configure --sysconfdir=/etc --prefix=/usr --libexecdir=/usr/lib \
49 18 Andreas Steffen
   --disable-aes --disable-des --disable-md5 --disable-sha1 --disable-sha2 \
50 19 Andreas Steffen
   --disable-fips-prf --disable-gmp --disable-stroke --disable-pluto --disable-tools \
51 20 Martin Willi
   --disable-updown --enable-openssl --enable-nm --enable-agent \
52 20 Martin Willi
   --enable-eap-gtc --enable-eap-md5 --enable-eap-mschapv2
53 1 Martin Willi
make
54 18 Andreas Steffen
make install
55 1 Martin Willi
56 20 Martin Willi
# get the NetworkManager strongsSwan plugin as a tarball
57 20 Martin Willi
wget http://download.strongswan.org/NetworkManager/NetworkManager-strongswan-1.1.0.tar.bz2
58 20 Martin Willi
tar xjf NetworkManager-strongswan-1.1.0.tar.bz2
59 20 Martin Willi
cd NetworkManager-strongswan-1.1.0
60 9 Martin Willi
61 20 Martin Willi
# build the NetworkManager strongsSwan plugin
62 9 Martin Willi
./configure --sysconfdir=/etc --prefix=/usr --libexecdir=/usr/lib --with-charon=/usr/lib/ipsec/charon
63 19 Andreas Steffen
make
64 9 Martin Willi
make install
65 19 Andreas Steffen
</pre>
66 19 Andreas Steffen
67 20 Martin Willi
h2. Configuration
68 1 Martin Willi
69 11 Martin Willi
70 17 Martin Willi
* Click on nm-applet -> VPN Connections -> Configure VPN...
71 17 Martin Willi
* Add -> Ipsec/IKEv2 (strongswan) -> Create ...
72 17 Martin Willi
* Configure your client
73 9 Martin Willi
* Click on nm-applet -> VPN Connections -> Your Connection
74 9 Martin Willi
* Enter password
75 9 Martin Willi
76 9 Martin Willi
As you can see, there is no subnet configuration for the tunnel. We let the gateway administration choose the subnet; the client always proposes 0.0.0.0/0 for the remote network and the gateway narrows that down to the configured subnet. 
77 9 Martin Willi
78 20 Martin Willi
h2. Screenshots
79 17 Martin Willi
80 20 Martin Willi
!nm-strongswan-config.png! !nm-strongswan-auth.png!
81 1 Martin Willi
82 20 Martin Willi
h2. Server configuration
83 1 Martin Willi
84 20 Martin Willi
Depending on the used authentication methods, you can use gateway configurations very similar to Windows 7 ([[Win7MultipleConfig|Certificate]]/[[Win7EapMultipleConfig|MSCHAPv2]]), or use [[EapGtc|EAP-GTC]] to authenticate against PAM.