Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
4.5.0, 4.5.1, 4.6.0
-
None
-
Security Level: Public (Anyone can view this level - this is the default.)
-
None
Description
OpenSwan would have this error message in auth.log:
Oct 31 00:13:11 r-13-VM pluto[4717]: "L2TP-PSK"[1] 10.215.3.6 #1: responding to Main Mode from unknown peer 10.215.3.6
Oct 31 00:13:11 r-13-VM pluto[4717]: "L2TP-PSK"[1] 10.215.3.6 #1: transition from state STATE_MAIN_R0 to state STATE_MAIN_R1
Oct 31 00:13:11 r-13-VM pluto[4717]: "L2TP-PSK"[1] 10.215.3.6 #1: STATE_MAIN_R1: sent MR1, expecting MI2
Oct 31 00:13:11 r-13-VM pluto[4717]: "L2TP-PSK"[1] 10.215.3.6 #1: NAT-Traversal: Result using draft-ietf-ipsec-nat-t-ike (MacOS X): no NAT detected
Oct 31 00:13:11 r-13-VM pluto[4717]: "L2TP-PSK"[1] 10.215.3.6 #1: transition from state STATE_MAIN_R1 to state STATE_MAIN_R2
Oct 31 00:13:11 r-13-VM pluto[4717]: "L2TP-PSK"[1] 10.215.3.6 #1: STATE_MAIN_R2: sent MR2, expecting MI3
Oct 31 00:13:11 r-13-VM pluto[4717]: "L2TP-PSK"[1] 10.215.3.6 #1: ignoring informational payload, type IPSEC_INITIAL_CONTACT msgid=00000000
Oct 31 00:13:11 r-13-VM pluto[4717]: "L2TP-PSK"[1] 10.215.3.6 #1: Main mode peer ID is ID_IPV4_ADDR: '10.215.3.6'
Oct 31 00:13:11 r-13-VM pluto[4717]: "L2TP-PSK"[1] 10.215.3.6 #1: transition from state STATE_MAIN_R2 to state STATE_MAIN_R3
Oct 31 00:13:11 r-13-VM pluto[4717]: "L2TP-PSK"[1] 10.215.3.6 #1: new NAT mapping for #1, was 10.215.3.6:500, now 10.215.3.6:4500
Oct 31 00:13:11 r-13-VM pluto[4717]: "L2TP-PSK"[1] 10.215.3.6 #1: STATE_MAIN_R3: sent MR3, ISAKMP SA established
Oct 31 00:13:12 r-13-VM pluto[4717]: "L2TP-PSK"[1] 10.215.3.6 #1: the peer proposed: 10.223.161.22/32:17/1701 -> 10.215.3.6/32:17/0
Oct 31 00:13:12 r-13-VM pluto[4717]: "L2TP-PSK"[1] 10.215.3.6 #2: ENCAPSULATION_MODE_UDP_TRANSPORT_RFC must only be used if NAT-Traversal is detected
Oct 31 00:13:12 r-13-VM pluto[4717]: "L2TP-PSK"[1] 10.215.3.6 #2: sending encrypted notification BAD_PROPOSAL_SYNTAX to 10.215.3.6:4500
Oct 31 00:13:15 r-13-VM pluto[4717]: "L2TP-PSK"[1] 10.215.3.6 #1: the peer proposed: 10.223.161.22/32:17/1701 -> 10.215.3.6/32:17/54694
Oct 31 00:13:15 r-13-VM pluto[4717]: "L2TP-PSK"[1] 10.215.3.6 #3: ENCAPSULATION_MODE_UDP_TRANSPORT_RFC must only be used if NAT-Traversal is detected
Oct 31 00:13:15 r-13-VM pluto[4717]: "L2TP-PSK"[1] 10.215.3.6 #3: sending encrypted notification BAD_PROPOSAL_SYNTAX to 10.215.3.6:4500
Oct 31 00:13:18 r-13-VM pluto[4717]: "L2TP-PSK"[1] 10.215.3.6 #1: the peer proposed: 10.223.161.22/32:17/1701 -> 10.215.3.6/32:17/54694
Oct 31 00:13:18 r-13-VM pluto[4717]: "L2TP-PSK"[1] 10.215.3.6 #4: ENCAPSULATION_MODE_UDP_TRANSPORT_RFC must only be used if NAT-Traversal is detected
Oct 31 00:13:18 r-13-VM pluto[4717]: "L2TP-PSK"[1] 10.215.3.6 #4: sending encrypted notification BAD_PROPOSAL_SYNTAX to 10.215.3.6:4500
Oct 31 00:13:21 r-13-VM pluto[4717]: "L2TP-PSK"[1] 10.215.3.6 #1: the peer proposed: 10.223.161.22/32:17/1701 -> 10.215.3.6/32:17/54694
Attachments
Issue Links
- duplicates
-
CLOUDSTACK-9197 CS 4.5.1 VR Remote Access VPN - received packet that claimed to be (I)nitiator, but rcookie is not zero?
- Resolved
-
CLOUDSTACK-9212 Cannot Connect to VPN with Public IP on Windows 7 L2TP IPSEC VPN Client
- Resolved
- relates to
-
CLOUDSTACK-8682 Replace openswan ipsec with strongswan ipsec
- Resolved