877
edits
Changes
From SME Server
Jump to navigationJump to searchno edit summary
Take this action only *after* you have confirmed proper L2TP connection is working.
Take this action only *after* you have confirmed proper L2TP connection is working.
== Issues ==
Ipsec and l2tpd is a vast and complicated subject. I have tried to simplify it to the best of my abilities. Mainly because I can't do complicated.
Please go and have a good read of the online documentation for [https://libreswan.org/ Libreswan]
I basically used an example like this [https://libreswan.org/wiki/VPN_server_for_remote_clients_using_IKEv1_with_L2TP Ipsec/L2tpd] although this never page existed when I first started building this contrib.
The first thing to do if you get stuck is check all your settings and your logs.
Go back and check your network settings. Check you passwords. Get someone else to make sure they are OK.
Is the ipsec secret correct?
Have you enabled remote VPN access for a user and checked the password?
Ipsec - check here first:
/var/log/pluto/pluto./log
Look for L2TPD-PSK entries and in particular this "STATE_QUICK_R2: IPsec SA established transport mode"
That means that you have a basic ipsec connection
L2tpd - check here:
/var/log/messages
Look for xl2tpd and pppd entries
Do you get as far as this "ip-up: xl2tpd ppp0 /dev/pts/2 150 192.168.97.1 192.168.97.180 xl2tpd"
If so you have a basic l2tpd connection
To debug have a look at the following:
db ipsec_connections show L2TPD-PSK
config show ipsec
config show xl2tpd
cat /etc/ipsec.d/ipsec.conf
cat /etc/ipsec.d/ipsec.secrets
Try restarting both ipsec and xl2tpd and watch your logs for errors:
service xl2tpd restart
service ipsec restart
If you are still stuck then ask on the forums, or if you have some template errors or other issues please raise a bug.
==To Do List==
==To Do List==
