Quantcast
Channel: Untangle Forums
Viewing all articles
Browse latest Browse all 5188

ios connection failure to l2tp

$
0
0
Using an iphone and Untangle 10, I can create a working connection no problem.

Using the same iphone and Untangle 11 I cannot.

Nat traversal is selected, external ip, eth4, is listed in Listening Addresses by default, I see in the logs that the module adds all the interfaces with the appropriate ip's and ports, a user is created in the local directory with the pwd of bill, and the secret is bob, I set those after failures with real passwords, I tripled checked that I didn't swap them, I did not quadruple check, the module has been turned off and on with the 'button', the iphone has been rebooted, the iphone is attempting from its cellular network as you can see from the ip in the log, I have not rebooted the Untangle 11.

I'm cornfused.


Dec 2 17:45:27 untangle3 pluto[28127]: "VPN-L2TP-0"[3] 70.209.73.24 #3: sending notification INVALID_PAYLOAD_TYPE to 70.209.73.24:1429
Dec 2 17:45:27 untangle3 pluto[28127]: "VPN-L2TP-0"[3] 70.209.73.24 #3: message ignored because it contains an unknown or unexpected payload type (ISAKMP_NEXT_SAK) at the outermost level
Dec 2 17:45:20 untangle3 pluto[28127]: "VPN-L2TP-0"[3] 70.209.73.24 #3: sending notification INVALID_PAYLOAD_TYPE to 70.209.73.24:1429
Dec 2 17:45:20 untangle3 pluto[28127]: "VPN-L2TP-0"[3] 70.209.73.24 #3: message ignored because it contains an unknown or unexpected payload type (ISAKMP_NEXT_SAK) at the outermost level
Dec 2 17:45:04 untangle3 pluto[28127]: "VPN-L2TP-0"[3] 70.209.73.24 #3: sending notification INVALID_PAYLOAD_TYPE to 70.209.73.24:1429
Dec 2 17:45:04 untangle3 pluto[28127]: "VPN-L2TP-0"[3] 70.209.73.24 #3: message ignored because it contains an unknown or unexpected payload type (ISAKMP_NEXT_SAK) at the outermost level
Dec 2 17:45:01 untangle3 pluto[28127]: "VPN-L2TP-0"[3] 70.209.73.24 #3: sending notification INVALID_PAYLOAD_TYPE to 70.209.73.24:1429
Dec 2 17:45:01 untangle3 pluto[28127]: "VPN-L2TP-0"[3] 70.209.73.24 #3: message ignored because it contains an unknown or unexpected payload type (ISAKMP_NEXT_SAK) at the outermost level
Dec 2 17:44:58 untangle3 pluto[28127]: "VPN-L2TP-0"[3] 70.209.73.24 #3: sending notification INVALID_PAYLOAD_TYPE to 70.209.73.24:1429
Dec 2 17:44:58 untangle3 pluto[28127]: "VPN-L2TP-0"[3] 70.209.73.24 #3: message ignored because it contains an unknown or unexpected payload type (ISAKMP_NEXT_SAK) at the outermost level
Dec 2 17:44:57 untangle3 pluto[28127]: "VPN-L2TP-0"[3] 70.209.73.24 #3: STATE_MAIN_R1: sent MR1, expecting MI2
Dec 2 17:44:57 untangle3 pluto[28127]: "VPN-L2TP-0"[3] 70.209.73.24 #3: transition from state STATE_MAIN_R0 to state STATE_MAIN_R1
Dec 2 17:44:57 untangle3 pluto[28127]: "VPN-L2TP-0"[3] 70.209.73.24 #3: responding to Main Mode from unknown peer 70.209.73.24
Dec 2 17:44:57 untangle3 pluto[28127]: packet from 70.209.73.24:1429: received Vendor ID payload [Dead Peer Detection]
Dec 2 17:44:57 untangle3 pluto[28127]: packet from 70.209.73.24:1429: ignoring Vendor ID payload [FRAGMENTATION 80000000]
Dec 2 17:44:57 untangle3 pluto[28127]: packet from 70.209.73.24:1429: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02_n] meth=106, but already using method 110
Dec 2 17:44:57 untangle3 pluto[28127]: packet from 70.209.73.24:1429: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 110
Dec 2 17:44:57 untangle3 pluto[28127]: packet from 70.209.73.24:1429: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 110
Dec 2 17:44:57 untangle3 pluto[28127]: packet from 70.209.73.24:1429: ignoring unknown Vendor ID payload [9909b64eed937c6573de52ace952fa6b]
Dec 2 17:44:57 untangle3 pluto[28127]: packet from 70.209.73.24:1429: ignoring unknown Vendor ID payload [80d0bb3def54565ee84645d4c85ce3ee]
Dec 2 17:44:57 untangle3 pluto[28127]: packet from 70.209.73.24:1429: ignoring unknown Vendor ID payload [4d1e0e136deafa34c4f3ea9f02ec7285]
Dec 2 17:44:57 untangle3 pluto[28127]: packet from 70.209.73.24:1429: ignoring unknown Vendor ID payload [439b59f8ba676c4c7737ae22eab8f582]
Dec 2 17:44:57 untangle3 pluto[28127]: packet from 70.209.73.24:1429: ignoring unknown Vendor ID payload [8f8d83826d246b6fc7a8a6a428c11de8]
Dec 2 17:44:57 untangle3 pluto[28127]: packet from 70.209.73.24:1429: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike] method set to=110
Dec 2 17:44:57 untangle3 pluto[28127]: packet from 70.209.73.24:1429: received Vendor ID payload [RFC 3947] method set to=109

Viewing all articles
Browse latest Browse all 5188

Trending Articles