raspberryfish
Posts: 16
Joined: Wed May 23, 2012 6:13 pm

L2TP/IPSec cant get it working

Sat Oct 17, 2015 6:59 pm

Hello,

i followed the instructions on this page, but i cant connect locally or via 3G with my Windows Phone.

http://www.smileykeith.com/2014/01/27/i ... rch-linux/

Just changed ipsec.secrets:

Code: Select all

xx.no-ip.org xxx.no-ip.org : PSK "0x............"
but i am getting an error:

Code: Select all

Oct 17 18:52:35 lemaker pluto[376]: loading secrets from "/etc/ipsec.secrets"
Oct 17 18:52:35 lemaker ipsec__plutorun[371]: 002 listening for IKE messages
Oct 17 18:52:35 lemaker ipsec__plutorun[371]: 002 adding interface lo/lo 127.0.0.1:500
Oct 17 18:52:35 lemaker ipsec__plutorun[371]: 002 adding interface lo/lo 127.0.0.1:4500
Oct 17 18:52:35 lemaker ipsec__plutorun[371]: 002 adding interface lo/lo ::1:500
Oct 17 18:52:35 lemaker ipsec__plutorun[371]: 002 loading secrets from "/etc/ipsec.secrets"
Oct 17 18:52:35 lemaker pluto[376]: ERROR "/etc/ipsec.secrets" line 1: index "xxx.no-ip.org" does not look numeric and name lookup failed
Oct 17 18:52:35 lemaker ipsec__plutorun[371]: 003 ERROR "/etc/ipsec.secrets" line 1: index "xxx.no-ip.org" does not look numeric and name lookup failed
Oct 17 18:52:35 lemaker pluto[376]: ERROR "/etc/ipsec.secrets" line 1: index "xxx.no-ip.org" does not look numeric and name lookup failed
Oct 17 18:52:35 lemaker ipsec__plutorun[371]: 003 ERROR "/etc/ipsec.secrets" line 1: index "xxx.no-ip.org" does not look numeric and name lookup failed
does anyone know a solution?

thanks

sdjf
Posts: 1397
Joined: Fri Mar 16, 2012 5:20 am
Location: California
Contact: Website

Re: L2TP/IPSec cant get it working

Sun Oct 18, 2015 9:13 am

It looks like you need to use a numeric IP address and you have used a text URL instead in your ipsec.secrets file.

Too bad that guide you followed did not make that clear, but other sites show numeric IPs and not alphabetic URLs in their examples.
FORUM TIP: To view someone's posting history, sign in, click on their user name, then on "Search User's Posts." || Running ArchLinuxArm on Model 2B and 512MB Model B

raspberryfish
Posts: 16
Joined: Wed May 23, 2012 6:13 pm

Re: L2TP/IPSec cant get it working

Sun Oct 18, 2015 11:00 am

Hello,

yes it was something related to that. According to another blog i changed it to PI-IP which is 192.168.58.164.

But when i connect to it with my Windows 10 COmputer

i am getting this:

Code: Select all

Oct 18 10:58:31 lemaker pluto[874]: "L2TP-PSK-noNAT" #11: non-critical payload ignored because it contains an unknown or unexpected payload type (ISAKMP_NEXT_v2CP) at the outermost level
Oct 18 10:58:31 lemaker pluto[874]: "L2TP-PSK-noNAT" #11: missing encrypted payload for v2_state: responder-auth-process: ISAKMP_NEXT_v2AUTH. Message dropped.
Oct 18 10:58:31 lemaker pluto[874]: | ikev2_parent_inI2outR2_tail returned STF_FAIL with v2N_INVALID_SYNTAX
Oct 18 10:58:31 lemaker pluto[874]: "L2TP-PSK-noNAT" #11: STATE_PARENT_R1: INVALID_EXCHANGE_TYPE
Oct 18 10:58:31 lemaker pluto[874]: "L2TP-PSK-noNAT" #11: sending  notification v2N_INVALID_SYNTAX to 192.168.58.195:500
Oct 18 10:58:32 lemaker pluto[874]: "L2TP-PSK-noNAT" #11: non-critical payload ignored because it contains an unknown or unexpected payload type (ISAKMP_NEXT_v2CP) at the outermost level
Oct 18 10:58:32 lemaker pluto[874]: "L2TP-PSK-noNAT" #11: missing encrypted payload for v2_state: responder-auth-process: ISAKMP_NEXT_v2AUTH. Message dropped.
Oct 18 10:58:32 lemaker pluto[874]: | ikev2_parent_inI2outR2_tail returned STF_FAIL with v2N_INVALID_SYNTAX
Oct 18 10:58:32 lemaker pluto[874]: "L2TP-PSK-noNAT" #11: STATE_PARENT_R1: INVALID_EXCHANGE_TYPE
Oct 18 10:58:32 lemaker pluto[874]: "L2TP-PSK-noNAT" #11: sending  notification v2N_INVALID_SYNTAX to 192.168.58.195:500
Oct 18 10:58:35 lemaker pluto[874]: "L2TP-PSK-noNAT" #11: non-critical payload ignored because it contains an unknown or unexpected payload type (ISAKMP_NEXT_v2CP) at the outermost level
Oct 18 10:58:35 lemaker pluto[874]: "L2TP-PSK-noNAT" #11: missing encrypted payload for v2_state: responder-auth-process: ISAKMP_NEXT_v2AUTH. Message dropped.
Oct 18 10:58:35 lemaker pluto[874]: | ikev2_parent_inI2outR2_tail returned STF_FAIL with v2N_INVALID_SYNTAX
Oct 18 10:58:35 lemaker pluto[874]: "L2TP-PSK-noNAT" #11: STATE_PARENT_R1: INVALID_EXCHANGE_TYPE
Oct 18 10:58:35 lemaker pluto[874]: "L2TP-PSK-noNAT" #11: sending  notification v2N_INVALID_SYNTAX to 192.168.58.195:500

Return to “Arch”