Tried a few more things with the settings, this time without trying to upgrade anything!! I have managed to get the L2TP working, however xl2tp seems to still be causing an issue. See below:
Oct 26 17:52:01 dcerouter pluto[27401]: "L2TP-PSK-NAT"[1] 192.168.80.139 #23: ignoring informational payload, type IPSEC_INITIAL_CONTACT msgid=00000000
Oct 26 17:52:01 dcerouter pluto[27401]: "L2TP-PSK-NAT"[1] 192.168.80.139 #23: received and ignored informational message
Oct 26 17:52:02 dcerouter pluto[27401]: "L2TP-PSK-NAT"[1] 192.168.80.139 #23: the peer proposed: 92.235.79.186/32:17/1701 -> 192.168.80.139/32:17/0
Oct 26 17:52:02 dcerouter pluto[27401]: "L2TP-PSK-NAT"[1] 192.168.80.139 #24: responding to Quick Mode proposal {msgid:431872ee}
Oct 26 17:52:02 dcerouter pluto[27401]: "L2TP-PSK-NAT"[1] 192.168.80.139 #24: us: 92.235.79.186[+S=C]:17/1701
Oct 26 17:52:02 dcerouter pluto[27401]: "L2TP-PSK-NAT"[1] 192.168.80.139 #24: them: 192.168.80.139[+S=C]:17/0
Oct 26 17:52:02 dcerouter pluto[27401]: "L2TP-PSK-NAT"[1] 192.168.80.139 #24: keeping refhim=4294901761 during rekey
Oct 26 17:52:02 dcerouter pluto[27401]: "L2TP-PSK-NAT"[1] 192.168.80.139 #24: transition from state STATE_QUICK_R0 to state STATE_QUICK_R1
Oct 26 17:52:02 dcerouter pluto[27401]: "L2TP-PSK-NAT"[1] 192.168.80.139 #24: STATE_QUICK_R1: sent QR1, inbound IPsec SA installed, expecting QI2
Oct 26 17:52:02 dcerouter pluto[27401]: "L2TP-PSK-NAT"[1] 192.168.80.139 #24: transition from state STATE_QUICK_R1 to state STATE_QUICK_R2
Oct 26 17:52:02 dcerouter pluto[27401]: "L2TP-PSK-NAT"[1] 192.168.80.139 #24: STATE_QUICK_R2: IPsec SA established transport mode {ESP=>0x032ff1f1 <0xda77ca7b xfrm=3DES_0-HMAC_SHA1 NATOA=none NATD=none DPD=none}
Apparently, from what I've read, the last line means the L2TP tunnel has been established. In /var/log/daemon.log I get the following output:
Oct 26 17:51:24 dcerouter xl2tpd[12399]: Listening on IP address 0.0.0.0, port 1701
Oct 26 17:52:05 dcerouter xl2tpd[12399]: control_finish: Peer requested tunnel 26256 twice, ignoring second one.
Oct 26 17:52:10 dcerouter xl2tpd[12399]: last message repeated 2 times
Oct 26 17:52:10 dcerouter xl2tpd[12399]: Maximum retries exceeded for tunnel 16046. Closing.
Oct 26 17:52:11 dcerouter xl2tpd[12399]: control_finish: Peer requested tunnel 26256 twice, ignoring second one.
Oct 26 17:52:11 dcerouter xl2tpd[12399]: Connection 26256 closed to 192.168.80.139, port 50906 (Timeout)
Oct 26 17:52:13 dcerouter xl2tpd[12399]: control_finish: Peer requested tunnel 26256 twice, ignoring second one.
Oct 26 17:52:15 dcerouter xl2tpd[12399]: control_finish: Peer requested tunnel 26256 twice, ignoring second one.
Oct 26 17:52:16 dcerouter xl2tpd[12399]: Unable to deliver closing message for tunnel 16046. Destroying anyway.
Oct 26 17:52:17 dcerouter xl2tpd[12399]: control_finish: Peer requested tunnel 26256 twice, ignoring second one.
Oct 26 17:52:26 dcerouter xl2tpd[12399]: last message repeated 3 times
Oct 26 17:52:26 dcerouter xl2tpd[12399]: Maximum retries exceeded for tunnel 51656. Closing.
Oct 26 17:52:27 dcerouter xl2tpd[12399]: control_finish: Peer requested tunnel 26256 twice, ignoring second one.
Oct 26 17:52:27 dcerouter xl2tpd[12399]: Connection 26256 closed to 192.168.80.139, port 50906 (Timeout)
Oct 26 17:52:29 dcerouter xl2tpd[12399]: control_finish: Peer requested tunnel 26256 twice, ignoring second one.
Oct 26 17:52:31 dcerouter xl2tpd[12399]: control_finish: Peer requested tunnel 26256 twice, ignoring second one.
Oct 26 17:52:32 dcerouter xl2tpd[12399]: Unable to deliver closing message for tunnel 51656. Destroying anyway.
Oct 26 17:52:33 dcerouter xl2tpd[12399]: control_finish: Peer requested tunnel 26256 twice, ignoring second one.
Oct 26 17:52:37 dcerouter xl2tpd[12399]: control_finish: Peer requested tunnel 26256 twice, ignoring second one.
Oct 26 17:52:39 dcerouter xl2tpd[12399]: control_finish: Peer requested tunnel 26256 twice, ignoring second one.
Oct 26 17:52:41 dcerouter xl2tpd[12399]: control_finish: Peer requested tunnel 26256 twice, ignoring second one.
Oct 26 17:52:42 dcerouter xl2tpd[12399]: Maximum retries exceeded for tunnel 7793. Closing.
Oct 26 17:52:43 dcerouter xl2tpd[12399]: control_finish: Peer requested tunnel 26256 twice, ignoring second one.
Oct 26 17:52:43 dcerouter xl2tpd[12399]: Connection 26256 closed to 192.168.80.139, port 50906 (Timeout)
Oct 26 17:52:43 dcerouter xl2tpd[12399]: control_finish: Peer requested tunnel 26256 twice, ignoring second one.
Oct 26 17:52:43 dcerouter xl2tpd[12399]: check_control: Received out of order control packet on tunnel -1 (got 1, expected 0)
Oct 26 17:52:43 dcerouter xl2tpd[12399]: handle_packet: bad control packet!
Oct 26 17:52:48 dcerouter xl2tpd[12399]: Unable to deliver closing message for tunnel 7793. Destroying anyway.
So, its definitely a xl2tpd issue....... I think?!
I got this far by making the following changes, not entirely sure which of them affected the connection:
/etc/ipsec.conf
changed
virtual_private=%4:192.168.80.0/24
to
virtual_private=%v4:192.168.80.0/24
(adding a
v after the
%)
/etc/ipsec.secrets
changed:
%any %any: "MyXL2TPSuperSecretPassword"
to
%defaultroute %any: PSK "MyXL2TPSuperSecretPassword"
/etc/ppp/options.xl2tpd
ms-dns 192.168.80.1
to
ms-dns 8.8.8.8
ms-dns 8.8.4.4
The only file that I haven't changed within the likely culprits is /etc/ppp/chap-secrets, which contains no mention of the VPN password I set, but instead has the following type entries:
# Secrets for authentication using CHAP
myuser l2tpd !VPNpass1 *
How does it resolve !VPNpass1? I also tried putting a plain text password in instead and restarting the x2ltpd, but no better!
The upshot is it's still not working grrrrrrrrrrrrrrrrrrrrrrr!!!!!
