I have seen this behavior with the first version that enabled padlock support (pfkey update failed). As padlock doesn't seem to work at the moment it was disabled until we can prove it's working. Is there a chance that you are on that old version and you're running a via cpu with padlocksupport?
 
However, I would suggest going to the latest version (.79.2 while I am writing this) and check again. This sounds like an old version to me.
 
Holger
-----Ursprüngliche Nachricht-----
Von: Heiko Weber [mailto:[EMAIL PROTECTED]
Gesendet: Sonntag, 21. August 2005 19:38
An: [EMAIL PROTECTED]
Betreff: [pfSense Support] ipsec VPN doesnt work

Hi,

 

I have some problems using VPN IPsec.

The tunnel wont work.

 

System logs:

 

 

Aug 20 23:09:16

racoon: INFO: IPsec-SA request for 123.234.123.234 queued due to no phase1 found.

Aug 20 23:09:16

racoon: INFO: initiate new phase 1 negotiation: 234.123.234.123[500]<=>123.234.123.234[500]

Aug 20 23:09:16

racoon: INFO: begin Aggressive mode.

Aug 20 23:09:16

racoon: NOTIFY: couldn't find the proper pskey, try to get one by the peer's address.

Aug 20 23:09:16

racoon: INFO: ISAKMP-SA established 234.123.234.123[500]<=>123.234.123.234[500] spi:7cf9d7a330877dcf:9fc0c939947c68f3

Aug 20 23:09:17

 racoon: INFO: initiate new phase 2 negotiation: 234.123.234.123[0]<=>123.234.123.234[0]

Aug 20 23:09:17 racoon: ERROR: pfkey UPDATE failed: Invalid argument

Aug 20 23:09:17 racoon: ERROR: pfkey ADD failed: Invalid argument

 

Any hints??

 

Cu

 

Heiko


____________
Virus checked by G DATA AntiVirusKit

Reply via email to