Reply To: problem with host to lan vpn L2tp/ipsec

Home Page Forums Network Management ZeroShell problem with host to lan vpn L2tp/ipsec Reply To: problem with host to lan vpn L2tp/ipsec

#46164

cowking2009
Member

Dear all,

I have the same problem of you while using NAT-T. Any ideas?

11:28:53 INFO: Hashing 140.116.103.162[43166] with algo #1
11:28:53 INFO: Hashing 140.116.103.164[500] with algo #1
11:28:53 INFO: Adding remote and local NAT-D payloads.
11:28:53 INFO: NAT-T: ports changed to: 140.116.103.162[43270]140.116.103.164[4500]
11:28:53 INFO: KA list add: 140.116.103.164[4500]->140.116.103.162[43270]
11:28:53 INFO: ISAKMP-SA established 140.116.103.164[4500]-140.116.103.162[43270] spi:70a96c3f3f6e6c15:8a639dc973d76474
11:28:54 INFO: respond new phase 2 negotiation: 140.116.103.164[4500]140.116.103.162[43270]
11:28:54 INFO: no policy found, try to generate the policy : 140.116.103.162/32[43270] 140.116.103.164/32[1701] proto=udp dir=in
11:28:54 INFO: Adjusting my encmode UDP-Transport->Transport
11:28:54 INFO: Adjusting peer’s encmode UDP-Transport(61444)->Transport(2)
11:28:54 INFO: IPsec-SA established: ESP/Transport 140.116.103.162[43270]->140.116.103.164[4500] spi=120777682(0x732ebd2)
11:28:54 INFO: IPsec-SA established: ESP/Transport 140.116.103.164[4500]->140.116.103.162[43270] spi=592665891(0x23535d23)
11:28:54 ERROR: such policy does not already exist: “140.116.103.162/32[43270] 140.116.103.164/32[1701] proto=udp dir=in”
11:28:54 ERROR: such policy does not already exist: “140.116.103.164/32[1701] 140.116.103.162/32[43270] proto=udp dir=out”
11:29:29 INFO: purging ISAKMP-SA spi=70a96c3f3f6e6c15:8a639dc973d76474.
11:29:29 INFO: purged ISAKMP-SA spi=70a96c3f3f6e6c15:8a639dc973d76474.
11:29:30 INFO: ISAKMP-SA deleted 140.116.103.164[4500]-140.116.103.162[43270] spi:70a96c3f3f6e6c15:8a639dc973d76474

Any ideas?

Thanks and regards,
Cowking