Plutorun started on Mon Jan 5 22:22:03 YEKT 2015
adjusting ipsec.d to /etc/ipsec.d
Starting Pluto (Openswan Version 2.6.37; Vendor ID OEu\134d\134jy\134\134ap) pid:14580
LEAK_DETECTIVE support [disabled]
OCF support for IKE [disabled]
SAref support [disabled]: Protocol not available
SAbind support [disabled]: Protocol not available
NSS support [disabled]
HAVE_STATSD notification support not compiled in
Setting NAT-Traversal port-4500 floating to on
   port floating activation criteria nat_t=1/port_float=1
   NAT-Traversal support  [enabled]
using /dev/urandom as source of random entropy
ike_alg_register_enc(): Activating OAKLEY_AES_CBC: Ok (ret=0)
starting up 1 cryptographic helpers
started helper pid=14586 (fd:4)
Using Linux 2.6 IPsec interface code on 3.2.0-4-amd64 (experimental code)
using /dev/urandom as source of random entropy
ike_alg_register_enc(): Activating aes_ccm_8: Ok (ret=0)
ike_alg_add(): ERROR: Algorithm already exists
ike_alg_register_enc(): Activating aes_ccm_12: FAILED (ret=-17)
ike_alg_add(): ERROR: Algorithm already exists
ike_alg_register_enc(): Activating aes_ccm_16: FAILED (ret=-17)
ike_alg_add(): ERROR: Algorithm already exists
ike_alg_register_enc(): Activating aes_gcm_8: FAILED (ret=-17)
ike_alg_add(): ERROR: Algorithm already exists
ike_alg_register_enc(): Activating aes_gcm_12: FAILED (ret=-17)
ike_alg_add(): ERROR: Algorithm already exists
ike_alg_register_enc(): Activating aes_gcm_16: FAILED (ret=-17)
Changed path to directory '/etc/ipsec.d/cacerts'
Changed path to directory '/etc/ipsec.d/aacerts'
Changed path to directory '/etc/ipsec.d/ocspcerts'
Changing to directory '/etc/ipsec.d/crls'
  Warning: empty directory
added connection description "L2TP-PSK-NAT"
added connection description "L2TP-PSK-noNAT"
added connection description "passthrough-for-non-l2tp"
listening for IKE messages
adding interface eth0/eth0 192.168.0.103:500
adding interface eth0/eth0 192.168.0.103:4500
adding interface lo/lo 127.0.0.1:500
adding interface lo/lo 127.0.0.1:4500
adding interface lo/lo ::1:500
loading secrets from "/etc/ipsec.secrets"
loading secrets from "/var/lib/openswan/ipsec.secrets.inc"
packet from 89.204.112.133:500: received Vendor ID payload [RFC 3947] method set to=109
packet from 89.204.112.133:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
packet from 89.204.112.133:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02_n] meth=106, but already using method 109
packet from 89.204.112.133:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
packet from 89.204.112.133:500: ignoring Vendor ID payload [FRAGMENTATION 80000000]
packet from 89.204.112.133:500: received Vendor ID payload [Dead Peer Detection]
"L2TP-PSK-NAT"[1] 89.204.112.133 #1: responding to Main Mode from unknown peer 89.204.112.133
"L2TP-PSK-NAT"[1] 89.204.112.133 #1: OAKLEY_SHA2_256 is not supported.  Attribute OAKLEY_HASH_ALGORITHM
"L2TP-PSK-NAT"[1] 89.204.112.133 #1: transition from state STATE_MAIN_R0 to state STATE_MAIN_R1
"L2TP-PSK-NAT"[1] 89.204.112.133 #1: STATE_MAIN_R1: sent MR1, expecting MI2
"L2TP-PSK-NAT"[1] 89.204.112.133 #1: NAT-Traversal: Result using RFC 3947 (NAT-Traversal): both are NATed
"L2TP-PSK-NAT"[1] 89.204.112.133 #1: transition from state STATE_MAIN_R1 to state STATE_MAIN_R2
"L2TP-PSK-NAT"[1] 89.204.112.133 #1: STATE_MAIN_R2: sent MR2, expecting MI3
"L2TP-PSK-NAT"[1] 89.204.112.133 #1: Main mode peer ID is ID_IPV4_ADDR: '10.100.159.81'
"L2TP-PSK-NAT"[1] 89.204.112.133 #1: switched from "L2TP-PSK-NAT" to "L2TP-PSK-NAT"
"L2TP-PSK-NAT"[2] 89.204.112.133 #1: deleting connection "L2TP-PSK-NAT" instance with peer 89.204.112.133 {isakmp=#0/ipsec=#0}
"L2TP-PSK-NAT"[2] 89.204.112.133 #1: transition from state STATE_MAIN_R2 to state STATE_MAIN_R3
"L2TP-PSK-NAT"[2] 89.204.112.133 #1: new NAT mapping for #1, was 89.204.112.133:500, now 89.204.112.133:4500
"L2TP-PSK-NAT"[2] 89.204.112.133 #1: STATE_MAIN_R3: sent MR3, ISAKMP SA established {auth=OAKLEY_PRESHARED_KEY cipher=aes_256 prf=oakley_sha group=modp1024}
"L2TP-PSK-NAT"[2] 89.204.112.133 #1: ignoring informational payload, type IPSEC_INITIAL_CONTACT msgid=00000000
"L2TP-PSK-NAT"[2] 89.204.112.133 #1: received and ignored informational message
"L2TP-PSK-NAT"[2] 89.204.112.133 #1: the peer proposed: 89.179.3.113/32:17/1701 -> 10.100.159.81/32:17/0
"L2TP-PSK-NAT"[2] 89.204.112.133 #2: responding to Quick Mode proposal {msgid:431046d6}
"L2TP-PSK-NAT"[2] 89.204.112.133 #2:     us: 192.168.0.103<192.168.0.103>[+S=C]:17/1701
"L2TP-PSK-NAT"[2] 89.204.112.133 #2:   them: 89.204.112.133[10.100.159.81,+S=C]:17/0===10.100.159.81/32
"L2TP-PSK-NAT"[2] 89.204.112.133 #2: transition from state STATE_QUICK_R0 to state STATE_QUICK_R1
"L2TP-PSK-NAT"[2] 89.204.112.133 #2: STATE_QUICK_R1: sent QR1, inbound IPsec SA installed, expecting QI2
"L2TP-PSK-NAT"[2] 89.204.112.133 #2: transition from state STATE_QUICK_R1 to state STATE_QUICK_R2
"L2TP-PSK-NAT"[2] 89.204.112.133 #2: STATE_QUICK_R2: IPsec SA established transport mode {ESP=>0x0afebfd6 <0x9d2a0aad xfrm=AES_256-HMAC_SHA2_256 NATOA=none NATD=89.204.112.133:4500 DPD=none}