|
Title: Problems with ipsec 2.5.2 efw Post by: betopin on Tuesday 19 August 2014, 02:33:52 am Hi everybody
I'm trying to configurate an ipsec vpn in endian 2.5.2 but i have an strange problem. This is the log when Im trying to connect my endian with a CISCO ASA LoyaltyPROD" #1: received Vendor ID payload [Dead Peer Detection] Aug 15 15:22:55 pluto[12241] "LoyaltyPROD" #1: Peer ID is ID_IPV4_ADDR: 'a.a.a.a' Aug 15 15:22:55 pluto[12241] "LoyaltyPROD" #1: we require peer to have ID 'b.b.b.b', but peer declares 'a.a.a.a' Aug 15 15:22:55 pluto[12241] "LoyaltyPROD" #1: sending encrypted notification INVALID_ID_INFORMATION to b.b.b.b:500 Where b.b.b.b it's a public ip and a.a.a.a it's a private ip in the domain of b.b.b.b What is the problem? Could you help me? Thanks a lot! Title: Re: Problems with ipsec 2.5.2 efw Post by: Eduardo on Sunday 24 August 2014, 05:14:32 pm Did you see this?
http://help.endian.com/entries/20061251-IPSec-VPN-How-to-Create-a-Net-to-Net-Connection-Endian-2-4-to-Cisco-ASA- Maybe it will help. Rgrds :) Title: Re: Problems with ipsec 2.5.2 efw Post by: betopin on Thursday 28 August 2014, 07:16:28 am Yes I did, but I was not very useful.
I had a big problem with the peer ID. That parameter is optional in the efw. Big problem for me!!! Ipsec it's perfect now. |