Not able to connect on IPSEC

mnsmani

Hi, I am trying to connect on IPSEC from pfsense <–> pfsense through WAN interface.

all the time I am getting errors like:
Apr 20 09:48:46 racoon: INFO: caught signal 15
Apr 20 09:48:47 racoon: INFO: racoon shutdown
Apr 20 09:48:52 racoon: INFO: @(#)ipsec-tools 0.6.6 (http://ipsec-tools.sourceforge.net)
Apr 20 09:48:52 racoon: INFO: @(#)This product linked OpenSSL 0.9.7e-p1 25 Oct 2004 (http://www.openssl.org/)
Apr 20 09:48:52 racoon: INFO: fe80::1%lo0[500] used as isakmp port (fd=13)
Apr 20 09:48:52 racoon: INFO: ::1[500] used as isakmp port (fd=14)
Apr 20 09:48:52 racoon: INFO: 127.0.0.1[500] used as isakmp port (fd=15)
Apr 20 09:48:52 racoon: WARNING: setsockopt(UDP_ENCAP_ESPINUDP_NON_IKE): Invalid argument
Apr 20 09:48:52 racoon: INFO: fe80::202:b6ff:fe34:5722%rl2[500] used as isakmp port (fd=16)
Apr 20 09:48:52 racoon: INFO: 192.168.2.99[500] used as isakmp port (fd=17)
Apr 20 09:48:52 racoon: WARNING: setsockopt(UDP_ENCAP_ESPINUDP_NON_IKE): Invalid argument
Apr 20 09:48:52 racoon: INFO: fe80::202:b6ff:fe34:5724%rl0[500] used as isakmp port (fd=18)
Apr 20 09:48:52 racoon: INFO: 121.247.124.90[500] used as isakmp port (fd=19)
Apr 20 09:48:52 racoon: WARNING: setsockopt(UDP_ENCAP_ESPINUDP_NON_IKE): Invalid argument

is there anything that needs to be done here?

my conf looks like this: (phase 1)
encryption->3DES, Hash->SHA1, DH Key Group ->2, life time ->2000 sec, authentication method->pre-shared key.
phase 2:
Protocol ->ESP, Encryption Algo: DES/3DES/BLOWFISH/CAST128/Rijndael256/Rijndael AES/ (all are selected).Hash->Md5/SH1 (both selected), PFS key group 1, lifetime 2000 sec.

can somebody help me?

also, as is damn strange enough, I see that this conf connects from one side, and does not connect from other side. but I could not reproduce that scenario myself :(

thanks in advance
Mani

hoba

@mnsmani:

…
Apr 20 09:48:52 racoon: INFO: 192.168.2.99[500] used as isakmp port (fd=17)
…
Apr 20 09:48:52 racoon: INFO: 121.247.124.90[500] used as isakmp port (fd=19)
…
also, as is damn strange enough, I see that this conf connects from one side, and does not connect from other side. but I could not reproduce that scenario myself :(

Is one of the peers behind another NAT with it's WAN in a private IP-Space? Seems to be the case from the logs. In that case you most likely will only be able to connect from the end behind the NAT to the other end as the NAT is preventing one end to be reached from the internet directly. I would try to get the both pfSense to real WAN IPs with nothing but transparent equipement (like modems) in front of them.