Difference between revisions of "Vpnsec Linux install"

From Cncz
Jump to: navigation, search
([Installatie zonder NetworkManager][Installation without NetworkManager])
([Installatie zonder NetworkManager][Installation without NetworkManager])
Line 73: Line 73:
 
== [Installatie zonder NetworkManager][Installation without NetworkManager] ==
 
== [Installatie zonder NetworkManager][Installation without NetworkManager] ==
  
[nl]PS: Onderaan extra opmerkingen voor Fedora Core (FC23).[/nl]
+
[nl]<em>PS: Onderaan extra opmerkingen voor Fedora Core (FC23).</em>[/nl]
[en]Note: Below some remarks for Fedora Core (FC23).[/en]
+
[en]<em>Note: Below some remarks for Fedora Core (FC23).</em>[/en]
  
 
[nl]Installeer strongswan, inclusief de curl, eap-identity, eap-mschapv2 en eap-md4 (benodigd voor eap-mschapv2) plugins. Wanneer je strongswan zelf compileert, zorg er dan voor dat je de benodigde plugins meegeeft aan het <b><tt>configure</tt></b>-script.[/nl]
 
[nl]Installeer strongswan, inclusief de curl, eap-identity, eap-mschapv2 en eap-md4 (benodigd voor eap-mschapv2) plugins. Wanneer je strongswan zelf compileert, zorg er dan voor dat je de benodigde plugins meegeeft aan het <b><tt>configure</tt></b>-script.[/nl]
Line 130: Line 130:
 
$ sudo ln -s /etc/ca-certificates/extracted/cadir/DigiCert_Assured_ID_Root_CA.pem [/usr/local]/etc/ipsec.d/cacerts/DigiCert_Assured_ID_Root_CA.pem
 
$ sudo ln -s /etc/ca-certificates/extracted/cadir/DigiCert_Assured_ID_Root_CA.pem [/usr/local]/etc/ipsec.d/cacerts/DigiCert_Assured_ID_Root_CA.pem
 
</pre>
 
</pre>
 +
 +
== Fedora (FC23) ==
 +
 +
FC23, 1/3/2016:
  
 
[nl]Vervang op Fedora (getest met FC23) <b><tt>ipsec</tt></b> door <b><tt>strongswan</tt></b>.[/nl]
 
[nl]Vervang op Fedora (getest met FC23) <b><tt>ipsec</tt></b> door <b><tt>strongswan</tt></b>.[/nl]
 
[en]On Fedora (tested on FC23), use command <b><tt>strongswan</tt></b> instead of <b><tt>ipsec</tt></b> in the instructions above.[/en]
 
[en]On Fedora (tested on FC23), use command <b><tt>strongswan</tt></b> instead of <b><tt>ipsec</tt></b> in the instructions above.[/en]
 +
 +
[nl]Je hebt de nieuwste SELinux policies nodig, doe daarom:[/nl]
 +
[en]To get the newest SELinux policies, you need to issue:[/en]
 +
<pre>
 +
dnf update --enablerepo=updates-testing selinux-policy
 +
</pre>

Revision as of 22:09, 2 March 2016

This procedure assumes using NetworkManager. See below for a manual procedure.

Install the required software:

# aptitude install network-manager-strongswan strongswan-plugin-eap-mschapv2
The following NEW packages will be installed:
  libstrongswan{a} network-manager-strongswan strongswan-ike{a} strongswan-nm{a}
  strongswan-plugin-eap-mschapv2 strongswan-plugin-openssl{a} 
...

# service network-manager stop
network-manager stop/waiting
# service network-manager start
network-manager start/running, process 29031

Configuration:

Select the NetworkManager applet and after that Edit Connections...

Vpnsec linux 2.png

Click Add, select IPsec/IKEv2 in the section VPN, click Create

Vpnsec linux 3.png

Enter data at:Connection name, Address (vpnsec.science.ru.nl), loginname, etc. and check the marks where needed.

Vpnsec linux 4.png

Save: (Save and Close)

Vpnsec linux 5.png

Start the VPN. Select the NetworkManager applet, next VPN Connections and finally the connection created.

Vpnsec linux 6.png

Known problems

If the VPN connection has been established, but ping ns1.science.ru.nl doesn't work, while ping 131.174.224.4 does work, then probably dnsmasq is the culprit. This can be solved bij disabling the dnsmasq DNS cache, as is described in Ask Ubuntu: DNS problem when connected to a VPN:

First make sure that there are no lines beginning with nameserver in any files in /etc/resolvconf/resolv.conf.d.
If /etc/resolvconf/resolv.conf.d/tail is a symbolic link to target original, make it point to /dev/null.

Second, disconnect from the VPN. Edit /etc/NetworkManager/NetworkManager.conf

$ sudo gedit /etc/NetworkManager/NetworkManager.conf

and comment out

dns=dnsmasq

(i.e., add a # so that it looks like the following)

#dns=dnsmasq

and then

sudo service network-manager restart

Installation without NetworkManager

Note: Below some remarks for Fedora Core (FC23).

Install strongswan, including the curl, eap-identity, eap-mschapv2 and eap-md4 (required for eap-mschapv2) plugins. When you compile strongswan from source, make sure to pass the right parameters to the configure script.

$ ./configure --enable-curl --enable-md4 --enable-openssl --enable-xauth-eap --enable-eap-md5 --enable-eap-gtc --enable-eap-tls --enable-eap-ttls --enable-eap-peap --enable-eap-mschapv2 --enable-eap-identify
$ make
$ sudo make install

You can test which plugins are loaded with sudo ipsec statusall or sudo ipsec listplugins. If necessary you can load plugins manually by editing strongswan.conf.

Make sure your ipsec.conf, probably located in /etc or in /usr/local/etc, looks like this:

config setup
    strictcrlpolicy=yes

conn %default
    ikelifetime=60m
    keylife=20m
    rekeymargin=3m
    keyingtries=1
    keyexchange=ikev2

conn science
    left=%defaultroute
    leftfirewall=yes
    leftsourceip=%config
    leftauth=eap-mschapv2
    leftid=mysciencelogin        <-- edit this
    eap_identity=mysciencelogin  <-- edit this
    right=vpnsec.science.ru.nl
    rightauth=pubkey
    rightid=@vpnsec.science.ru.nl
    rightsubnet=0.0.0.0/0
    forceencaps=yes
    auto=start

And your ipsec.secrets as follows, where you enter your own Science account name and password. Watch out that this file cannot be read by everyone, as it contains your password! It is typically owned by root:root with -rw------- (600) permissions.

mysciencelogin : EAP "mypassword"

Everything should work now:

$ sudo ipsec start
$ sudo ipsec up science

It can be necessary to put the root certificate in the right folder manually:

$ sudo ln -s /etc/ca-certificates/extracted/cadir/DigiCert_Assured_ID_Root_CA.pem [/usr/local]/etc/ipsec.d/cacerts/DigiCert_Assured_ID_Root_CA.pem

Fedora (FC23)

FC23, 1/3/2016:

On Fedora (tested on FC23), use command strongswan instead of ipsec in the instructions above.

To get the newest SELinux policies, you need to issue:

dnf update --enablerepo=updates-testing selinux-policy