I had a similiar problem with a IPSEC VPN tunnel.  I enabled the keep alive on both ends of the tunnel and have not had any trouble at all.  Also I had to make sure that the ICMP port was open so that the ping could pass throught the tunnel.
RC

Configure ipsec tunnel by this tutorial.
http://pfsense.com/mirror.php?section=tutorials/mobile_ipsec/

Everything worked just fine for me(i have two shops connected)!
Tunnel is very stable(not like ovpn between same points for example).

Anton

I had the same trouble, but after i pinged opposite side of tunnel, everything went ok.

Last message before i pinged was
racoon: WARNING: setsockopt(UDP_ENCAP_ESPINUDP_NON_IKE): Invalid argument

After

racoon: INFO: IPsec-SA established: ESP/Tunnel 10.7.3.115[0]->192.170.1.2[0] spi=236667421(0xe1b421d)
racoon: INFO: IPsec-SA established: ESP/Tunnel 192.170.1.2[0]->10.7.3.115[0] spi=53599917(0x331dead)

And it works fine.

@tacfit:

L2TP and IPSec are not the same, so I don't think it should work. I've tried similar with the Windows L2TP client and it wouldn't work.

Thanks - that was not present that I can have IPsec without L2TP - I thought if you have IPsec you always have L2TP.

Bye,
eweri

OK, given your wording I'm still not entirely sure your problem. It sounds like you're asking this:

1. You have your pfsense server setup "normally", with a static IP.
2. You want to connect to it via IPSEC, from other places, like home or an internet cafe.

As I said, the configuration issue is with the router you are behind, when you're at home or at the cafe. It's not a question of the router's IP, it's the IPSEC NAT settings. If the router has been configured to pass IPSEC through the NAT, then it will work fine. Otherwise, no luck. That's a limitation with IPSEC, it's not NAT friendly, so the router your laptop is behind must be configured to pass IPSEC through NAT unhindered. Most routers have this option, some older ones won't.

We've got an 'allow anything' on the LAN interface (VLAN 10) and an 'allow anything' rule on the IPSEC interface on pfSense. If I do a tcpdump on enc0 and ping a host on the LAN subnet from the other end of the ipsec tunnell (10.1.1.0/24), I see the incoming ping request, and the outgoing ping response, but the remote network never receives the packet. I've also checked the filters on the remote linksys router, and I'm not having much luck. We've even tried dropping the filters on the remote end entirely, and still no response.

In my initial look at the state table I wasn't quick enough. An initial attempt to go directly to the host w/o involving NAT happens, and then after some time, NAT gets involved. I also have the system logging all blocked packets, and I don't see any blocks of my ICMP packets being logged.

If I see the incoming request, and the pinged host's response on enc0, that seems to indicate that the filters on pfSense aren't in play, unless the outbound ping response is getting filtered out somewhere and I'm just not finding it. I've got the exact same setup working on v1.0.1, so I'm really not sure why this isn't working on the new version. Has the handling of packets destined to IPSEC tunnels changed in 1.2 beyond the IPSEC interface filters? I'm really baffled by this one….

Thanks again for any insight you can offer on this one.

http://forum.m0n0.ch/ ?

search the forum
there is a solution around

my client has a static address on his end and i have one two on my side.  I have no issues.  It was a pain to get just right but I am finding everyvendor has slightly different terms for the same thing and it will drive you nuts.

In my case it was a typo.  I had the wrong IP set up.  changed it and up it came.  it's been working fine.
RC

Great work!  Can you submit this to freebsd-net@freebsd.org as well for comments / directions from the community on how we can get this commited to the official FreeBSD tree?

Thanks for all the work on this!

OK, sorry, yes, mobile clients are working  not in main mode…..

I've been trying to get a tunnel up between pfsense and ipcop and am also getting the same message in my ipsec logs. Any ideas?

IPSEC Log
Dec 7 16:32:44 racoon: INFO: unsupported PF_KEY message REGISTER
Dec 7 16:32:44 racoon: INFO: fe80::200:e8ff:fe12:ba22%dc0[500] used as isakmp port (fd=19)
Dec 7 16:32:44 racoon: [Self]: INFO: 85.189.247.234[500] used as isakmp port (fd=18)
Dec 7 16:32:44 racoon: [Self]: INFO: 172.31.15.8[500] used as isakmp port (fd=17)
Dec 7 16:32:44 racoon: INFO: fe80::202:a5ff:fecc:7d08%fxp0[500] used as isakmp port (fd=16)
Dec 7 16:32:44 racoon: [Self]: INFO: 127.0.0.1[500] used as isakmp port (fd=15)
Dec 7 16:32:44 racoon: INFO: ::1[500] used as isakmp port (fd=14)
Dec 7 16:32:44 racoon: INFO: fe80::1%lo0[500] used as isakmp port (fd=13)
Dec 7 16:32:44 racoon: INFO: @(#)This product linked OpenSSL 0.9.7e-p1 25 Oct 2004 (http://www.openssl.org/)
Dec 7 16:32:44 racoon: INFO: @(#)ipsec-tools 0.6.7 (http://ipsec-tools.sourceforge.net)

/var/etc/racoon.conf:
path pre_shared_key "/var/etc/psk.txt";

path certificate  "/var/etc";

remote 80.177.152.212 {
        exchange_mode main;
        my_identifier address "85.189.247.234";

peers_identifier address 80.177.152.212;
        initial_contact on;
        support_proxy on;
        proposal_check obey;

proposal {
                encryption_algorithm 3des;
                hash_algorithm sha1;
                authentication_method pre_shared_key;
                dh_group 2;
                lifetime time 3600 secs;
        }
        lifetime time 3600 secs;
}

sainfo address 172.31.15.0/24 any address 10.101.0.0/16 any {
        encryption_algorithm 3des,blowfish,cast128,rijndael,rijndael 256;
        authentication_algorithm hmac_sha1,hmac_md5;
        compression_algorithm deflate;
        lifetime time 28800 secs;
}

I think I posted on another one of your posts, I will get some additional help for you tomorrow with my working configurations posted on here.

Let's try to narrow down a few things.  What ASA Model and OS version are you running?  I would suggest limiting the protocol/encryption/hash to ESP-3DES-MD5 and disable or disallow all the others.  When phase 1 completes on the Cisco side and you try to ping through from the Cisco LAN to the pfSense LAN, does anything change (TTL?, RTT?)?

I will lab this up with one of my work ASA's to my home pfSense to offer some additional assistance.

Oh, well yeah that'd help.  :)  I was assuming you had the proper rules in place and thinking it possibly was a FTP proxy related issue (though VPN subnets are supposed to bypass that, obviously that's working correctly).