VPN is working but lots of errors in logs.

[TonyAR]

I have an IPSEC VPN between pfSense and VMWare Vcloud.

The VPN appears to be working fine, however I have a constant stream of error messages in the IPSEC logs.

racoon: [IPSec]: [ <remote ip="">] ERROR: failed to pre-process ph2 packet [Check Phase 2 settings, networks] (side: 1, status: 1).
racoon: ERROR: failed to get sainfo.</remote> 

These are occurring at roughly 10 second intervals.

I Googled and "failed to get sainfo" suggests a subnet mismatch - however I have checked and all subnets are correct.

Settings

Phase 1

Authentication method: MutualPSK
Negotiation mode: main
My identifier:  <my ip="">Peer identifier: <remote ip="">Pre-Shared Key: <blah>Policy Generation: Default
Proposal Checking: Default
Encryption algorithm: AES 256bits
Hash algorithm: SHA1
DH key group: 2(1024bit)
Lifetime: 28800
NAT Traversal: Disable
DPD: enabled</blah></remote></my> 

This is a list of the phase 2 entries.

tunnel 	192.168.0.0/24 	172.16.63.0/24 	ESP 	AES (256 bits) 	SHA1 	
tunnel 	192.168.0.0/24 	172.16.60.0/24 	ESP 	AES (256 bits) 	SHA1 	
tunnel 	192.168.0.0/24 	172.16.61.0/24 	ESP 	AES (256 bits) 	SHA1 	
tunnel 	192.168.0.0/24 	172.16.62.0/24 	ESP 	AES (256 bits) 	SHA1 	
tunnel 	192.168.3.0/24 	172.16.63.0/24 	ESP 	AES (256 bits) 	SHA1 	
tunnel 	192.168.3.0/24 	172.16.60.0/24 	ESP 	AES (256 bits) 	SHA1 	
tunnel 	192.168.3.0/24 	172.16.61.0/24 	ESP 	AES (256 bits) 	SHA1 	
tunnel 	192.168.3.0/24 	172.16.62.0/24 	ESP 	AES (256 bits) 	SHA1 	
tunnel 	192.168.0.0/24 	172.16.64.0/24 	ESP 	AES (256 bits) 	SHA1 	
tunnel 	192.168.3.0/24 	172.16.64.0/24 	ESP 	AES (256 bits) 	SHA1 	

Phase 2 settings for all entries:

Mode: Tunnel IPV4
Protocol: ESP
Encryption algorithms: AES256
Hash algorithms: SHA1
PFS key group: 2(1024bit)
Lifetime: 28800

Any help would be appreciated.

pfSense version:

2.1.1-RELEASE (amd64)
built on Tue Apr 1 15:22:21 EDT 2014
FreeBSD 8.3-RELEASE-p14

VMWare Vcloud Director version unknown.

[TonyAR]

Replying to own post as this may help someone else in the future.

I found the issue.

On the remote side, I had defined our three (local) networks:

192.168.0.0/24
192.168.3.0/24
10.1.1.0/24

Because we had no need for the 10.x subnet to use the VPN yet, I didn't define a phase 2 entry on pfSense.

This was causing the errors.

Defining a phase 2 entry for the 10.x network on pfSense resolved my issue.