Difference between revisions of "Openswan L2TP/IPsec VPN client setup"

From ArchWiki
Jump to navigation Jump to search
(A further script)
(A further script)
Line 230: Line 230:
cp ./options.l2tpd.client /etc/ppp/
cp ./options.l2tpd.client /etc/ppp/
cp ./ipsec.conf /etc/
cp ./ipsec.conf /etc/
    cp ./ipsec.secrets /etc/
cp ./ipsec.secrets /etc/
cp ./xl2tpd.conf /etc/xl2tpd/
cp ./xl2tpd.conf /etc/xl2tpd/

Revision as of 11:04, 26 March 2012

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.

Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어

External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

L2TP/IPsec is a secure Virtual Private Network solution that is well supported on many different platforms.

This article aims to describe in a HOWTO like fashion how to configure and use a L2TP/IPsec client on Arch Linux. This article will cover the installation and setup of several software packages. One of the packages is only available in the AUR, so knowledge of how to build and install AUR packages on your system is required, as I will not cover how to do that.

This guide is primarly for clients connecting to a Windows Server machine. It uses some setting that are specific to the Microsoft implementation of L2TP/IPsec.


Install xl2tpd from the repos and ipsec-openswanAUR from the AUR.



Edit /etc/ipsec.conf: It should contain the following lines:

  config setup
  # Replace eth0 with your network interface
  conn L2TP-PSK
  # Replace IP address with your local IP (private, behind NAT IP is okay as well)
  # Replace IP address with your VPN server's IP

This file contains the basic information to establish a secure IPsec tunnel to the VPN server. It enables NAT Traversal for if your machine is behind a NAT'ing router (most people are), and various other options that are necessary to connect correctly to the remote IPsec server. The next file contains your pre-shared key (PSK) for the server.

Create the file /etc/ipsec.secrets: It should contain the following line: : PSK "your_pre_shared_key"

Remember to replace the local ( and remote ( IP addresses with the correct numbers for your location. The pre-shared key will be supplied by the VPN provider and will need to be placed in this file in cleartext form.

At this point the IPsec configuration is complete and we can move on to the L2TP configuration.


Edit /etc/xl2tpd/xl2tpd.conf: It should resemble the following:

  [lac vpn-connection]
  lns =
  ppp debug = yes
  pppoptfile = /etc/ppp/options.l2tpd.client
  length bit = yes

This file configures xl2tpd with the connection name, server IP address(which again, please remember to change to your servers address) and various options that will be passed to pppd once the tunnel is set up.

Now modify /etc/ppp/options.l2tpd.client:

 idle 1800
 mtu 1410
 mru 1410
 connect-delay 5000
 name your_vpn_username
 password your_password

Place your assigned username and password for the VPN server in this file. A lot of these options are for interoperability with Windows Server L2TP servers.

This concludes the configuration of the applicable software suites to connect to a L2TP/IPsec server. To start the connection do the following:

 /etc/rc.d/openswan start
 /etc/rc.d/xl2tpd start
 ipsec auto --up L2TP-PSK
 echo "c vpn-connection" > /var/run/xl2tpd/l2tp-control

At this point the tunnel is up and you should be able to see the interface for it if you type:

$ ip link

You should see a pppX device that represents the tunnel. Right now, nothing is going to get routed through it. You need to add some routing rules to make it work right:


Routing traffic to a single IP address through the tunnel

This is as easy as adding a routing rule to your kernel table:

 #route add xxx.xxx.xxx.xxx gw yyy.yyy.yyy.yyy eth0

Replace xxx.xxx.xxx.xxx with the specific ip address of the server that you wish to communicate with through the tunnel, then replace yyy.yyy.yyy.yyy with the remote IP your PPP connection. The remote IP of a PPP connection can be discovered by issuing:


and reading the P-t-P address for the PPP interface that corresponds to your tunnel.

Routing all traffic through the tunnel

This is a lot more complex, but all your traffic will travel through the tunnel. Start by adding a special route for the actual VPN server through your current gateway:

 #route add gw eth0

This will ensure that once the default gateway is changed to the ppp interface that your network stack can still find the VPN server by routing around the tunnel. If you miss this step you will lose connectivity to the Internet and the tunnel will collapse. Now add a default route that routes to the PPP remote end:

 #route add default gw yyy.yyy.yyy.yyy eth0

The remote PPP end can be discovered by following the step in the previous section. Now to ensure that ALL traffic is routing through the tunnel, delete the original default route:

 #route delete default gw eth0

To restore your system to the previous state, you can reboot or reverse all of the above steps.


Issue: I get a message from pppd saying "Failed to authenticate ourselves to peer" and I've verified my password is correct. What could be wrong?

Solution: If you see the following in your /var/log/daemon.log:

Dec 20 15:14:03 myhost pppd[26529]: rcvd [CHAP Challenge id=0x1 <some_or_another_hash>, name = "SonicWALL"]
Dec 20 15:14:03 myhost pppd[26529]: sent [CHAP Response id=0x1 <some_or_another_hash>, name = "your_vpn_username"]
Dec 20 15:14:03 myhost pppd[26529]: rcvd [LCP EchoRep id=0x0 magic=0x45c269c6]
Dec 20 15:14:03 myhost pppd[26529]: rcvd [CHAP Failure id=0x1 ""]
Dec 20 15:14:03 myhost pppd[26529]: CHAP authentication failed
Dec 20 15:14:03 myhost pppd[26529]: CHAP authentication failed
Dec 20 15:14:03 myhost pppd[26529]: sent [LCP TermReq id=0x3 "Failed to authenticate ourselves to peer"]
Dec 20 15:14:03 myhost pppd[26529]: rcvd [LCP TermReq id=0x2]
Dec 20 15:14:03 myhost pppd[26529]: sent [LCP TermAck id=0x2]
Dec 20 15:14:03 myhost pppd[26529]: rcvd [LCP TermAck id=0x3]

then you are authenticating against a SonicWALL LNS that does not know how to handle CHAP-style authentication correctly.

The solution to this is to add the following to your options.l2tp.client file:


This will cause the SonicWALL to default to the next authentication mechanism, namely MSCHAP-v2. This should authenticate successfully, and from this point xl2tpd should successfully construct a tunnel between you and the remote L2TP server.

Tips and Tricks

Script start up and shut down

You can create some scripts either in your home directory or elsewhere(remember where you put them) to bring up the tunnel then shut it back down.

First, a utility script to automatically discover PPP distant ends: getip.sh

  /sbin/ifconfig $1 | grep "P-t-P" | gawk -F: '{print $2}' | gawk '{print $1}'

Next, the script to bring the tunnel up. This will replace the default route, so all traffic will pass via the tunnel: startvpn.sh

  /etc/rc.d/openswan start
  sleep 2                                                   #delay to ensure that IPsec is started before overlaying L2TP
  /etc/rc.d/xl2tpd start
  /usr/sbin/ipsec auto --up L2TP-PSK                        
  /bin/echo "c vpn-connection" > /var/run/xl2tpd/l2tp-control     
  sleep 2                                                   #delay again to make that the PPP connection is up.
  PPP_GW_ADD=`./getip.sh ppp0`
  route add gw eth0
  route add default gw $PPP_GW_ADD
  route delete default gw

Finally, the shutdown script, it simply reverses the process: stopvpn.sh

  /usr/sbin/ipsec auto --down L2TP-PSK
  /bin/echo "d vpn-connection" > /var/run/xl2tpd/l2tp-control
  /etc/rc.d/xl2tpd stop
  /etc/rc.d/openswan stop
  route delete gw eth0
  route add default gw

A further script

Above script really help me work. And notice the script use fixed ip, and someone like me may change net vpn addr, i'd like to put my further script below(not sure how to add attachment, so just raw ):

if [ $# != 1 ] ; then
	echo "Usage: (sudo) sh $0 {init|start|stop}" 
	exit 1;


function getIP(){
	/sbin/ifconfig $1 |grep "inet "|awk '{print $2}'

function getGateWay(){
	/sbin/route -n |grep -m 1 "^0\.0\.0\.0" |awk '{print $2}'
function getVPNGateWay(){
	/sbin/route -n |grep -m 1 "$VPN_ADDR" |awk '{print $2}'


function init(){
	cp ./options.l2tpd.client /etc/ppp/
	cp ./ipsec.conf /etc/
	cp ./ipsec.secrets /etc/
	cp ./xl2tpd.conf /etc/xl2tpd/

function start(){
	sed -i "s/^lns =.*/lns = $VPN_ADDR/g" /etc/xl2tpd/xl2tpd.conf
	sed -i "s/plutoopts=.*/plutoopts=\"--interface=$IFACE\"/g" /etc/ipsec.conf
	sed -i "s/left=.*$/left=$(getIP $IFACE)/g" /etc/ipsec.conf
	sed -i "s/right=.*$/right=$VPN_ADDR/g" /etc/ipsec.conf
	sed -i "s/^.*: PSK/$(getIP $IFACE) $VPN_ADDR : PSK/g" /etc/ipsec.secrets
	/etc/rc.d/openswan start
	sleep 2    #delay to ensure that IPsec is started before overlaying L2TP

	/etc/rc.d/xl2tpd start
	/usr/sbin/ipsec auto --up L2TP-PSK                        
	/bin/echo "c vpn-connection" > /var/run/xl2tpd/l2tp-control     
	sleep 2    #delay again to make that the PPP connection is up.

	route add $VPN_ADDR gw $GW_ADDR $IFACE
	route add default gw $(getIP ppp0)
	route delete default gw $GW_ADDR

function stop(){
	/usr/sbin/ipsec auto --down L2TP-PSK
	/bin/echo "d vpn-connection" > /var/run/xl2tpd/l2tp-control
	/etc/rc.d/xl2tpd stop
	/etc/rc.d/openswan stop
	route delete $VPN_ADDR gw $VPN_GW $IFACE
	route add default gw $VPN_GW

exit 0

AUR link for the OpenSwan package

OpenSwanAUR can be found in the AUR.

External links


I would like to thank phaoost from the StrongVPN forums for his initial guide to setup L2TP/IPsec on Linux, for without, this article would certainly not be possible.